Hello, thank you for your response. I already tried the "sleep 60" soluce, but does not work. I don't understand why, but the taskomatic service seems to run only when i'm in interactive session and i launch it manually.
Ok for the bug, but where can i find the bugtracker? -- Lionel. ----- Mail original ----- De: "Jan Hutař" <[email protected]> À: "spacewalk-list" <[email protected]> Envoyé: Lundi 7 Mars 2016 11:01:32 Objet: Re: [Spacewalk-list] Fresh install Taskomatic does not start automatically Hello, please file a bug for this issue. As a workaround, you can add "sleep 60" into "/etc/init.d/taskomatic" into top of function "start()". Note that I have checked RHEL7 installation and looks like we do not have systemd service file for that yet. Hope this helps, Jan On 2016-02-25 17:53 +0100, Lionel Caignec wrote: >Hi, > >nobody for helping me? > >Please ;). > >-- >Lionel > >----- Mail original ----- >De: "Lionel Caignec" <[email protected]> >À: "spacewalk-list" <[email protected]> >Envoyé: Mercredi 24 Février 2016 10:14:34 >Objet: [Spacewalk-list] Fresh install Taskomatic does not start >automatically > >Hello, > >i'm new with spacewalk and i have a little problem. >I've a fresh install of spacewalk 2.4 on centos 7.2.1511. > >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. > Giving up. > > > > 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. > > Someone can help me? > > Thank you. > > > -- > Lionel > >_______________________________________________ >Spacewalk-list mailing list >[email protected] >https://www.redhat.com/mailman/listinfo/spacewalk-list > >_______________________________________________ >Spacewalk-list mailing list >[email protected] >https://www.redhat.com/mailman/listinfo/spacewalk-list -- Jan Hutar Systems Management QA [email protected] Red Hat, Inc. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
