[Spacewalk-list] Tomcat Issues while configuring spacewalk

[Coe, Colin C. (Unix Engineer)]

What is the output of 'ls -l /usr/share/tomcat5/logs/catalina.out'?
 
CC

________________________________

From: spacewalk-list-bounces at redhat.com on behalf of cheerla sreehari
Sent: Tue 7/29/2008 8:05 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Tomcat Issues while configuring spacewalk


Hi ,

While configuring the spacewalk , I got an error message 
"tomcat start failed " 
After that I did so much research to solve the problem .

But I couldn't solve the problem .I am getting the following error message while restarting tomcat manually  .
Starting tomcat5: lock file found but no process running for pid 6746, continuing

Using CATALINA_BASE:   /usr/share/tomcat5
Using CATALINA_HOME:   /usr/share/tomcat5
Using CATALINA_TMPDIR: /usr/share/tomcat5/temp
Using JRE_HOME:
touch: cannot touch `/usr/share/tomcat5/logs/catalina.out': Permission denied
/usr/bin/dtomcat5: line 310: /usr/share/tomcat5/logs/catalina.out: Permission denied

Regards,
SreeHari Ch


On Tue, Jul 29, 2008 at 4:32 PM, John Hodrien <johnh at comp.leeds.ac.uk> wrote:


	If I have a machine that needs updates, and I select Auto Errata Update in the
	GUI, and next time it checks in it applies the updates.  If I leave it on
	that, and a new errata applies to the machine, nothing happens, and it is not
	automatically updated.
	
	Where do I start to debug this?  Taskomatic is running, and I'm getting daily
	emails of activity, so I know it hooking up with the DB.
	
	jh
	
	-- 
	"All my life I wanted to be someone; I guess I should have been more
	 specific."                                          -- Jane Wagner
	
	_______________________________________________
	Spacewalk-list mailing list
	Spacewalk-list at redhat.com
	https://www.redhat.com/mailman/listinfo/spacewalk-list
	



NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.