Red Hat Bugzilla – Bug 1315761
Fresh install Taskomatic does not start automatically
Last modified: 2016-03-08 09:30:32 EST
Description of problem:
When i reboot my server, the taskomatic service refuse to start.
In log i've this message :
INFO | jvm 5 | 2016/02/24 07:53:18 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO | jvm 5 | 2016/02/24 07:53:18 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
INFO | jvm 5 | 2016/02/24 07:53:18 |
ERROR | wrapper | 2016/02/24 07:53:48 | Startup failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2016/02/24 07:53:48 | JVM did not exit on request, terminated
INFO | wrapper | 2016/02/24 07:53:48 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper | 2016/02/24 07:53:48 | JVM exited in response to signal SIGKILL (9).
FATAL | wrapper | 2016/02/24 07:53:48 | There were 5 failed launches in a row, each lasting less than 300 seconds.
But if i log in server (ssh or tty) and launch manually the service (/etc/init.d/taskomatic start) it's work perfectly.
I tried to "delayed the service" by inserting a sleep before it start but does not do anything.
Version-Release number of selected component (if applicable):
I've a fresh install of spacewalk 2.4 on centos 7.2.1511.
Steps to Reproduce:
1. Fresh install of spacewalk on clean centos 7.2
2. Reboot server
3. check status of taskomatic service
Taskomatic service dead