Hi everyone, After a fresh install of Suse 7.0 ( due to a hardisk faillure where I had everything working almost perfectly with Suse 6.4), I have encountered the following problems. 1) Suse Help system does not work I receive error 403 FORBIDDEN You don't have permission to access / on this server. At the Suse Site http://sdb.suse.de/sdb/en/html/adrian_6.3_apache.html describes the problem for 6.3. Therefore I checked my /etc/httpd/httpd.conf file and realized that it is as described in the article. So made the corrections. (If it is a known issue in 6.3 why Suse does not correct it after two versions ) 2) OK got the new apache.rpm installed and here we go problems do start FORBIDDEN You don't have permission to access / on D168.suse.de. Who the hell is D168.suse.de this is what is defined for server name in the apache config I believe this is a FEATURE not a bug So far I have changed names for the linux box thru yast and let yast handle all the updates thru suseconfig but this does not come to solution So where do I begin to dig for corections to get the local help system including Support database working and getting the Thanks -- Togan Muftuoglu toganm@turk.net 100% MS FREE Absolutely no component of Microsoft was used in the generation or posting of this e-mail. So it is virus free -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Togan Muftuoglu wrote:
Hi everyone,
After a fresh install of Suse 7.0 ( due to a hardisk faillure where I had everything working almost perfectly with Suse 6.4), I have encountered the following problems.
1) Suse Help system does not work I receive error 403
FORBIDDEN You don't have permission to access / on this server.
At the Suse Site http://sdb.suse.de/sdb/en/html/adrian_6.3_apache.html describes the problem for 6.3. Therefore I checked my /etc/httpd/httpd.conf file and realized that it is as described in the article. So made the corrections.
(If it is a known issue in 6.3 why Suse does not correct it after two versions )
2) OK got the new apache.rpm installed and here we go problems do start
FORBIDDEN You don't have permission to access / on D168.suse.de.
Who the hell is D168.suse.de this is what is defined for server name in the apache config
I believe this is a FEATURE not a bug
So far I have changed names for the linux box thru yast and let yast handle all the updates thru suseconfig but this does not come to solution
So where do I begin to dig for corections to get the local help system including Support database working and getting the
Thanks
Hi Togan, also check the unix file permissions in the "dokumentation" tree. they should be 755 for directories and 544 for files. This includes directories in the path *to* the server root. I think I came across a similar problem, in fact, I've seen this sort of problem so frequently (most with ~/public_html) that I forgot where and how. Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
juergen.braukmann@ruhr-west.de wrote:
Hi Togan,
also check the unix file permissions in the "dokumentation" tree. they should be 755 for directories and 544 for files. This includes directories in the path *to* the server root. I think I came across a similar problem, in fact, I've seen this sort of problem so frequently (most with ~/public_html) that I forgot where and how.
Juergen
Hi Juergen , thanks for the quick prompt. Since I am really upset with the hardware and the software problems I am getting at the moment (including the bad CD # 3 which most people have the same) is there way (probably there is) may be defining at /etc/permissions file which directory has what permissions and files have what permissions. If there is could you give me a KISS approach as it has been an awful day so far Probably you are right with the permission as I am unable to get permissions for /usr/local/man as normal user but root can access it. How come a fresh installation can break so many things is something I do not understand Thanks -- Togan Muftuoglu toganm@turk.net 100% MS FREE Absolutely no component of Microsoft was used in the generation or posting of this e-mail. So it is virus free -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Togan Muftuoglu wrote:
juergen.braukmann@ruhr-west.de wrote:
Hi Togan,
also check the unix file permissions in the "dokumentation" tree. they should be 755 for directories and 544 for files. This includes directories in the path *to* the server root. I think I came across a similar problem, in fact, I've seen this sort of problem so frequently (most with ~/public_html) that I forgot where and how.
Juergen
Hi Juergen ,
thanks for the quick prompt. Since I am really upset with the hardware and the software problems I am getting at the moment (including the bad CD # 3 which most people have the same) is there way (probably there is) may be defining at /etc/permissions file which directory has what permissions and files have what permissions. If there is could you give me a KISS approach as it has been an awful day so far
better use /etc/permissions.local for that, since it will all be gone with the next update. You realy get me searching now. ;-) I got problems finding my way through the system in terms of "where is what" ServerRoot "/usr/local/httpd/htdocs" all dirs up to that 755 there is a symlink "doc". it's a relative link to /usr/doc (that too 755) I'd say all dirs below that to 755, all files to 644. Sadly there are a few symlinks again, I did no clean install but an update. Digging through my system I vague remember that the location of documents changed from /usr/doc to /usr/share/doc. Under that, I find the susehelp system, but I do not find the link to it. The links are displayed in the browsers status line. In your situation, I'd try to find the first breaking link and compare it with the real position and permits. It could also be a symlink that points nowhere. As you see, I am as confused as I sound above, but I am left with a working system.
Probably you are right with the permission as I am unable to get permissions for /usr/local/man as normal user but root can access it.
Is it in your manpath???
How come a fresh installation can break so many things is something I do not understand
I had some other faults. Did a fresh install on my laptop and was impressed how good it went. No serious or remembereable problems there. The help system looks working. I might be wrong with my idea of permissions... Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
juergen.braukmann@ruhr-west.de wrote:
better use /etc/permissions.local for that, since it will all be gone with the next update. You realy get me searching now. ;-)
Found that portion also and compared wity my backups they are exactly the same.Since I had a crashed harddisk and scratched 7.0 CD #3 and 4i I ended up buying a new HD and a DVD (OK I was looking forward to it but not that urgent)
Probably you are right with the permission as I am unable to get permissions for /usr/local/man as normal user but root can access it.
After a fresh install now I have the help system and the Support database working apache is running no problem .After the new mod_php4.rpm upgrade from suse. apache complained with a wrong systax in the httpd.conf but it ended up that apache wants the mysqlclientlib.so, after installing it no problem it works cwith a charm (tuh tuh knock the wood) Well after the fresh install that still was the case. Now what I figured out was /usr/local has permission off 700, contrary to what you mentioned as 755 so I changed /usr/local to 0755 and now I can access the man pages and the executables under /usr/local/bin. The only thing I do not understand is why the installation made it to 0700 . Yet anyway now its functional. Thanks for the information. Togan Muftuoglu toganm@turk.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (2)
-
juergen.braukmann@ruhr-west.de
-
toganm@turk.net