[opensuse] services does not start automatically after a reboot on SLES 10
Hi, I have services of my product not starting after a reboot on SLES 10 mainframe box (but the services can be started manually using the scripts from /etc/init.d folder). I have all the configurations in place which are working on Suse 8 and Suse 9. I have the service start scripts (S77aclogrd) in /etc/init.d/rc5.d which are linked to scripts in /etc/init.d folder. Let me know what more I need to do get the services up and running after a reboot on SLES 10. Also let me know if you need more information. Thanks in advance, Murali. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Kamal, Murali (Murali.Kamal@ca.com) [20080610 12:07]:
I have services of my product not starting after a reboot on SLES 10 mainframe box (but the services can be started manually using the scripts from /etc/init.d folder).
I have all the configurations in place which are working on Suse 8 and Suse 9.
I have the service start scripts (S77aclogrd) in /etc/init.d/rc5.d which are linked to scripts in /etc/init.d folder.
Let me know what more I need to do get the services up and running after a reboot on SLES 10. Also let me know if you need more information.
Do the startup scripts have LSB conforming headers (see /etc/init.d/skeleton for reference)? What does 'chkconfig -l name_of_service' print? Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-06-10 at 06:07 -0400, Kamal, Murali wrote:
I have the service start scripts (S77aclogrd) in /etc/init.d/rc5.d which are linked to scripts in /etc/init.d folder.
Did you install them using insserv or chkconfig, or did you symlink them manually? It may not work that way. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFITmEntTMYHG2NR9URAhuQAJ9nNa2O3u71lxj1VGO3AN6si3MQ1gCdEVVj +zqMkhDKZojFrpNGoEt57cQ= =j3vk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, I have the symboliclinks in place done through my install script. I am not using the LSB confirming headers. The chkconfig command for my services returns the following: linux089:/etc/init.d # chkconfig -l acrecorde acrecorde 0:off 1:off 2:on 3:on 4:off 5:on 6:off linux089:/etc/init.d # chkconfig -l aclogrd aclogrd 0:off 1:off 2:on 3:on 4:off 5:on 6:off linux089:/etc/init.d # chkconfig -l acdistagn acdistagn 0:off 1:off 2:on 3:on 4:off 5:on 6:off linux089:/etc/init.d # chkconfig -l acactmgr acactmgr 0:off 1:off 2:on 3:on 4:off 5:on 6:off But, when I have the "RUN_PARALLEL" turned to "no" inside /etc/sysconfig/boot, I see all the services starting after a reboot. But I cannot suggest the customer to do the same, as it will effect a huge number of systems. Let me know what Should I include to have the services start. When I searched google, I found IBM Tivoli having similar problem(http://www-1.ibm.com/support/docview.wss?uid=swg21298166), but I don't know how they resolved the problem ! Thanks, Murali. Here is the script I am using #! /bin/sh # # Copyright 2007 CA. All rights reserved. # # # VeRsIoN: 8.0 (200.125) Compiled On:Jun 14 2007 09:58:36 i86PC # # start/stop eTrust Audit daemon if [ -r /opt/CA/eTrustAudit/bin//ac_set_env.sh ]; then . /opt/CA/eTrustAudit/bin//ac_set_env.sh else echo "eTrust Audit product not installed properly." exit fi case "$1" in 'start') if [ -f /opt/CA/eTrustAudit/bin/aclogrd ] ; then /opt/CA/eTrustAudit/bin/aclogrd -start fi ;; 'stop') if [ -f /opt/CA/eTrustAudit/bin/aclogrd ] ; then /opt/CA/eTrustAudit/bin/aclogrd -stop fi ;; *) echo "Usage: { start | stop }" ;; esac -----Original Message----- From: Carlos E. R. [mailto:robin.listas@telefonica.net] Sent: Tuesday, June 10, 2008 4:40 PM To: OS-en Subject: Re: [opensuse] services does not start automatically after a reboot on SLES 10 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-06-10 at 06:07 -0400, Kamal, Murali wrote:
I have the service start scripts (S77aclogrd) in /etc/init.d/rc5.d which are linked to scripts in /etc/init.d folder.
Did you install them using insserv or chkconfig, or did you symlink them manually? It may not work that way. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFITmEntTMYHG2NR9URAhuQAJ9nNa2O3u71lxj1VGO3AN6si3MQ1gCdEVVj +zqMkhDKZojFrpNGoEt57cQ= =j3vk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-06-10 at 07:24 -0400, Kamal, Murali wrote:
I have the symboliclinks in place done through my install script.
I am not using the LSB confirming headers.
You need to use those headers, and install using chkconfig or insserv. Do it, or do it, no alternative. Why? Because you are not maintaining the .depend.* files. If you insist on not doing things "the SuSE way", you might get it running for some time using "RUN_PARALLEL=no", or perhaps "USE_MAKE=no". This is not guaranteed to work, nor to be permanent. Disclaimer: I know little about the SLES, I speak comparing with the oss version, on which it is based. The documentation for this is in "man init.d", and there is a chapter in the suse html/pdf manual. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFITmybtTMYHG2NR9URAgphAKCB3F0XICT3sd3Px7sCqiPZM1JvxACfUCEt 3uWKF5S/XJ7+cfIgNcX4dyA= =brAJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Kamal, Murali (Murali.Kamal@ca.com) [20080610 13:24]:
I am not using the LSB confirming headers.
You *need* them, there is no other working way. Otherwise the runtime links get hosed as soon as insserv is called (for instance when a SuSE package with init scripts is installed). Just take /etc/init.d/skeleton as a template and 'man init.d' for documentation, it isn't that hard. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
Carlos E. R. -
Kamal, Murali -
Philipp Thomas