[Spacewalk-list] Spacewalk 1.7 / RHEL 5.8 / Taskomatic issue

Mon Jul 9 08:56:18 UTC 2012

Good morning,

Should I understand that I'm the only one with such a problem? :)

Would it be possible to get any advice? at least some directions?

Regards,
Jacek Rudowski
jrudowski at sapphire.gi<mailto:jrudowski at sapphire.gi>
DDI: +350 20049785
Sapphire Networks
Suite 3.0.3, Eurotowers, P O Box 797, Gibraltar
Customer Services
* Tel: +350 20047200
F Fax: +350 20047272
* E-Mail: info at sapphire.gi<mailto:info at sapphire.gi>
* Web: http://www.sapphire.gi<http://www.sapphire.gi/>

Technical Support
* Tel: +350 20047201
F Fax: +350 20047271
* E-Mail: support at sapphire.gi<mailto:support at sapphire.gi>

________________________________
From: Jacek Rudowski
Sent: 05 July 2012 18:07
To: 'spacewalk-list at redhat.com'
Subject: Spacewalk 1.7 / RHEL 5.8 / Taskomatic issue

Hello everybody,

I hope someone will be able to help me with my problems with taskomatic.

To be as descriptive as possible and give as much information as possible - a bit of background...

First installation of Spacewalk 1.7 has been done on RHEL 5.5 and I have to say it started to work almost instantly (with exception for cobbler, which had to be downgraded due to some apparently known issues - but that's not the case here)

I connected it with mrepo generated repositories, with packages synced nightly to spacewalk, and also with taskomatic running fine - so I had also repo files prepared daily for spacewalk and rhnplugin.

Later I have upgraded RHEL to 5.8 and... taskomatic stopped working, and to be honest I have no idea why, which change in the system it might be related to.

repomd.xml is not generated anymore for spacewalk/rhnplugin and taskomatic dying a while after (re)start attempt.

With some debug logging turned on I find those:

ERROR  | wrapper  | 2012/07/04 10:24:45 | Startup failed: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2012/07/04 10:24:45 | JVM did not exit on request, terminated
DEBUG  | wrapper  | 2012/07/04 10:24:45 | Signal trapped.  Details:
DEBUG  | wrapper  | 2012/07/04 10:24:45 |   signal number=17 (SIGCHLD), source="unknown"
DEBUG  | wrapper  | 2012/07/04 10:24:45 | Received SIGCHLD, checking JVM process status.
DEBUG  | wrapperp | 2012/07/04 10:24:45 | socket read no code (closed?).
DEBUG  | wrapperp | 2012/07/04 10:24:45 | Closing backend socket.

I was googling for information on this - it looks to be quite a common issue with earlier versions of spacewalk, but also expected to be sorted(?)

Anyway - some further investigation, with even more logging gave me this:

INFO   | jvm 1    | 2012/07/04 16:41:07 | 2012-07-04 16:41:07,180 [WrapperListener_start_runner] INFO  com.redhat.rhn.taskomatic.core.TaskomaticDaemon - Tomcat is not up yet, sleeping 4 seconds
INFO   | jvm 1    | 2012/07/04 16:41:11 | 2012-07-04 16:41:11,187 [WrapperListener_start_runner] INFO  com.redhat.rhn.taskomatic.core.TaskomaticDaemon - Tomcat is not up yet, sleeping 4 seconds
INFO   | jvm 1    | 2012/07/04 16:41:15 | 2012-07-04 16:41:15,193 [WrapperListener_start_runner] INFO  com.redhat.rhn.taskomatic.core.TaskomaticDaemon - Tomcat is not up yet, sleeping 4 seconds
INFO   | jvm 1    | 2012/07/04 16:41:19 | 2012-07-04 16:41:19,199 [WrapperListener_start_runner] INFO  com.redhat.rhn.taskomatic.core.TaskomaticDaemon - Tomcat is not up yet, sleeping 4 seconds
INFO   | jvm 1    | 2012/07/04 16:41:23 | 2012-07-04 16:41:23,205 [WrapperListener_start_runner] INFO  com.redhat.rhn.taskomatic.core.TaskomaticDaemon - Tomcat is not up yet, sleeping 4 seconds
INFO   | jvm 1    | 2012/07/04 16:41:27 | 2012-07-04 16:41:27,212 [WrapperListener_start_runner] INFO  com.redhat.rhn.taskomatic.core.TaskomaticDaemon - Tomcat is not up yet, sleeping 4 seconds

But... tomcat is running and listening on port 8009 for ajp proxied connections (which I think is default in spacewalk installation)

I don't really know now where too look at - maybe someone experienced similar sort of issue already?

One more thing maybe - from catalina.out:

Jul 5, 2012 5:11:27 PM org.apache.coyote.ajp.AjpMessage processHeader
SEVERE: Invalid message recieved with signature 18245

But it doesn't really help me much - maybe because of lack of some skills in Java (couple of more weeks with those issues, and it will probably change... ha ha!)

Just yet couple of word about environment:
as mentioned earlier RHEL 5.8
Spacewalk 1.7
TanukiWrapper 3.2.1
Java 1.6.0  (tried OpenJDK, Sun, IBM - no luck - now it's Sun)

Any suggestions would be welcome - any questions for additional information either, of course...

Regards

Regards,
Jacek Rudowski
jrudowski at sapphire.gi<mailto:jrudowski at sapphire.gi>
DDI: +350 20049785
Sapphire Networks
Suite 3.0.3, Eurotowers, P O Box 797, Gibraltar
Customer Services
* Tel: +350 20047200
F Fax: +350 20047272
* E-Mail: info at sapphire.gi<mailto:info at sapphire.gi>
* Web: http://www.sapphire.gi<http://www.sapphire.gi/>

Technical Support
* Tel: +350 20047201
F Fax: +350 20047271
* E-Mail: support at sapphire.gi<mailto:support at sapphire.gi>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120709/96b3a14c/attachment.htm>