Any one can help me on the error what I'm getting while starting some service in Linux.

# /etc/init.d/observiced start
Starting Oracle Secure Backup services... 2011/08/02.23:03:01 child didn't lock rock file - child never locked rock file (FSP rock file manager)
[FAILED]


When I see the status it gives me as mentioned below.

# /etc/init.d/observiced status
observiced dead but subsys locked

Hi,

First check if you have any instances of that process running, maybe even in zombie status using:
Kill any instances. Remove the lock file and pid file of the service in question. Check your init file for the service if you don't know where the pid file is located and how it's named. Since you failed to mention what distro and version you are using I can only guess for the location of the subsys lock files. Check /var/lock/subsys if you have a lockfile for your service there. If there is, delete it.

After that try to restart the service the normal way.

Kind regards,

Eric

Hi Eric, I did that, but dint find any process running, infect I deleted the locked file from /var/lock/subsys also, but no luck.

Linux 2.6.18-194.11.4.el5 #1 SMP Tue Sep 21 05:04:09 EDT 2010 x86_64 x86 _64 x86_64 GNU/Linux, see the log for that service, where it says it started obhttpd service but I could not able to see that when I do ps.

[root@slci038 ~]# tail -f /usr/tmp/observiced.log
Copyright (c) 1992, 2010, Oracle. All rights reserved. on slci038 pid 440
2011/08/02.23:01:00 listening for requests on port 400, interfaces:
2011/08/02.23:01:00 eth0 (fe80::221:28ff:fe8e:1f68%2)
2011/08/02.23:01:00 eth0 (::ffff:10.242.0.147)
2011/08/02.23:01:00 note: this machine is an administrative server
2011/08/02.23:01:00 obhttpd started in pid 443
2011/08/02.23:01:00 note: obscheduled listening on port 48207, interfaces:
2011/08/02.23:01:00 eth0 (fe80::221:28ff:fe8e:1f68%2)
2011/08/02.23:01:00 eth0 (::ffff:10.242.0.147)
2011/08/02.23:03:01 child didn't lock rock file - child never locked rock file (FSP rock file manager)

Hi,

Did you also delete the pid file of the process in question? Make sure you check for running processes, stop or kill them, delete pid file(s) and then lock file(s). If you didn't check/delete pid file(s) then do so and try again.

Kind regards,

Eric

yes I did that, removed the pid, deleted the lock file, infect I restarted the server but still no luck, one thing which I understood is the ophttpd service was not stopped properly and that creating a problem, thought it should work after reboot, but no luck.