[Spacewalk-list] Taskomatic crashes during repodata generation

guirimand, michael michael.guirimand at cgg.com
Mon Nov 3 08:21:45 UTC 2014


Hi Jeremy,

We're expecting an issue closed to this one.
It was related to JVM configuration.

You need to change -Xms -Xmx.

https://access.redhat.com/solutions/43122

Regards,
______ ______ ______


Michael Guirimand
System Administrator



From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jeremy Maes
Sent: Monday 3 November 2014 09:10
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Taskomatic crashes during repodata generation

Hey

Recently I've started syncing a couple of bigger repositories (RHEL, CentOS, ...) and since then my taskomatic will almost systematically crash every time it gets to the "Generating new repository metadata for channel" stage. When it does, it usually seems to crash very fast after starting this task for one of the bigger channels.

I've already enabled debug logging, but the only errors I'm getting are:
/var/log/rhn/rhn_taskomatic_daemon.log

ERROR  | wrapper  | 2014/10/31 21:46:46 | JVM appears hung: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2014/10/31 21:46:46 | JVM did not exit on request, terminated
STATUS | wrapper  | 2014/10/31 21:46:47 | JVM exited in response to signal SIGKILL (9).
ERROR  | wrapper  | 2014/10/31 21:46:47 | Unable to start a JVM
STATUS | wrapper  | 2014/10/31 21:46:48 | <-- Wrapper Stopped

/var/log/messages

Oct 31 21:46:46 spacewalk wrapper[22867]: JVM appears hung: Timed out waiting for signal from JVM.
Oct 31 21:46:46 spacewalk wrapper[22867]: JVM did not exit on request, terminated
Oct 31 21:46:47 spacewalk wrapper[22867]: JVM exited in response to signal SIGKILL (9).
Oct 31 21:46:47 spacewalk wrapper[22867]: Unable to start a JVM
Oct 31 21:46:48 spacewalk wrapper[22867]: <-- Wrapper Stopped
Apart from those I can't seem to find any other error messages (not in the taskomatic log, not in syslog, not in tomcat logs, ...) at the same time that could indicate what is going wrong.

Anyone have any pointers as to where I could look next to hopefully solve this problem? We're starting to use spacewalk more and more and taskomatic always crashing is getting to be an issue. Of course I could use a cronjob to check its status periodically and restart it if necessary, but that's only a bandaid solution...
--
Jeremy Maes
Team Technische Support
Groep Schaubroeck | BU IT
Steenweg Deinze 154 | 9810 Nazareth
T +32 (0)9 389 05 29
jma at schaubroeck.be<mailto:jma at schaubroeck.be> | www.schaubroeck.be<http://www.schaubroeck.be/>
Volg Groep Schaubroeck op [LinkedIn] <https://www.linkedin.com/company/schaubroeck-nv>

**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm
This email and any accompanying attachments are confidential. If you received this email by mistake, please delete
it from your system. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141103/1e898abd/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 537 bytes
Desc: image001.png
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141103/1e898abd/attachment.png>


More information about the Spacewalk-list mailing list