Why is daemon service not starting during boot time ?

**sicarie** · Mar 7 '11, 05:37 AM

I will merge these threads as soon as the issue is resolved so there's no confusion.

What is your script called and where is it located? Is it in /etc/init.d? What are the specific symlinks you created in the /etc/rc2.d and /etc/rc3.d folders?

**rameshjumgam** · Mar 7 '11, 12:25 PM

Hi sicarie,

1)Through my daemon script it starts some process, it is located in /etc/init.d/
2)Symbolic links i have created is
in
[root@cv-codc-embu ~]# file /etc/rc.d/rc0.d/K90dmgtd
/etc/rc.d/rc0.d/K90dmgtd: symbolic link to `../init.d/dmgtd'

[root@cv-codc-embu ~]# file /etc/rc.d/rc1.d/K90dmgtd
/etc/rc.d/rc1.d/K90dmgtd: symbolic link to `../init.d/dmgtd'

[root@cv-codc-embu ~]# file /etc/rc.d/rc2.d/S10dmgtd
/etc/rc.d/rc2.d/S10dmgtd: symbolic link to `../init.d/dmgtd'

[root@cv-codc-embu ~]# file /etc/rc.d/rc3.d/S10dmgtd
/etc/rc.d/rc3.d/S10dmgtd: symbolic link to `../init.d/dmgtd'

[root@cv-codc-embu ~]# file /etc/rc.d/rc4.d/S10dmgtd
/etc/rc.d/rc4.d/S10dmgtd: symbolic link to `../init.d/dmgtd'

[root@cv-codc-embu ~]# file /etc/rc.d/rc5.d/S10dmgtd
/etc/rc.d/rc5.d/S10dmgtd: symbolic link to `../init.d/dmgtd'

[root@cv-codc-embu ~]# file /etc/rc.d/rc6.d/K90dmgtd
/etc/rc.d/rc6.d/K90dmgtd: symbolic link to `../init.d/dmgtd'

and after rebooting the system i have checked like

[root@cv-codc-embu ~]# /sbin/service dmgtd status
/opt/CSCOpx/etc/commonscript.sh : line 82: /tmp/cscotmp/LOG_NAME.txt: No such file or directory
Usage: /etc/init.d/dmgtd { start | stop | kill}

Means my service is calling while boot time but start argument is not getting passed where i should take care plz help Thanks in advance....

**sicarie** · Mar 9 '11, 06:40 PM

The two things that jump out at me are errors and that you have a script in each level of the /etc/rc.d folders when you probably shouldn't. Those levels are init levels - they start different processes.

For instance, the kernel doesn't automatically boot with the capacity to be networked. It has to load that ability once it's able to be supported. That's why there are several init scripts with the same name throughout those folders - they load different parts of those programs when the resources are available (you can research 'linux run levels' through Google if you're curious about this). Also, the scripts starting with K are "kill" scripts for when the computer is shutting down. You should definitely remove yours unless there is a certain way your script should be stopped.

I would recommend calling your script one time in the /etc/rc3.d folder, and removing the others.

The other thing I notice is the error - line 82. It looks like your script calls another script that needs to log to a specific file. That log file does not exist, and therefore I believe your script is erring out.

Try running ./dmgtd from the folder that the dmgtd script is in.

You should see that error. You can fix this by running

mkdir /tmp/cscotmp
touch LOG_NAME.txt

That will ensure the directory is there, and the file is there for writing.

After that is done, re-run your script (./dmgtd) and make sure no other errors occur. It's possible that script is expecting a variable called $LOG_NAME, so you might want to check that if you keep getting an error with that other script.

Why is daemon service not starting during boot time ?

Why is daemon service not starting during boot time ?

Comment

Comment

Comment