http://bugzilla.novell.com/show_bug.cgi?id=520038
User marc@marcchamberlin.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=520038#c4
--- Comment #4 from Marc Chamberlin 2009-07-08 14:11:32 MDT ---
Ok Michal, the patch did restore the ability to stop and restart the tomcat6
server, but stopping seems to be taking an extraordinary long time. So thanks
for fixing it.
In trying to get things back to a working state (and again the only thing that
has happened, which affected the tomcat6 server, was this security update I
got, so I do not know if it is the cause of these problems, or just exposed
them) I discovered a couple other problems...
1. I deleted all the log files under /var/log/tomcat6 in order to get fresh
copies of them. Subsequently I restarted the tomcat6 server using "rctomcat6
restart" and it failed. I noted that it had attempted to create the log file -
catalina.out with an owner of root and permissions of rw-r-r and then it
subsequently tried to write to this file with a user id of tomcat which causes
the failure. So something in the scripts is setting up the catalina.out file
with the wrong user and permissions. I manually changed the permissions to
rw-rw-r and that worked (on my system I also made the tomcat user a member of
the root group) Once up and running, I noted that the owner of catalina.out had
changed to the tomcat user.. Interesting!
2. A more serious error also took place in my webapps/ROOT directory. My own
index.html file that was located there, was replaced by the default index.html
file that comes with the base tomcat6 installation. In other words, the
index.html that the Jakarta-Apache folks supply showing documentation on the
tomcat server itself. THIS HAD TO HAVE RESULTED SOMEHOW FROM THIS SECURITY
UPDATE!!! I have NOT changed anything else in these directories for some time
now. (Good thing I have everything in the webapps directory backed up so I was
able to restore it easily enough)
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.