"Service" dead but subsys locked

[jonislost]

Can anyone shed any light on the above error?

My problem is with the 3ware RAID controller software, but I actually want a bit more info on how to solve the issue (not specifically related to the 3dm2 service just services that lock in general...)

So first I check the service status:

sudo /etc/init.d/tdm2 status

I get the message:

3dm2 dead but subsys locked

So I thought I'd stop the service:

sudo /etc/init.d/tdm2 stop

It reports that it failed to stop the 3ware diskswitch deamon

So next I try removing the 3dm2 file from the subsys lock:

rm -f /var/lock/subsys/3dm2

then I check the service status and now its:

3dm2 is stopped

GREAT! I think... so I try starting it:

sudo /etc/init.d/tdm2 start

Starts the daemon OK. Awesome! Check the status:

3dm2 dead but subsys locked

Wahhhh

Due to the nature of the machine I cannot reboot it today (will need to wait for tomorrow). Until then though can anyone offer any knowledge on what's happening to this service and why it keeps locking?

Cheers.

 

[SMN]

Anything in /var/log/messages? What OS is it?

 

[tntcoder]

A lock file is purely there to prevent the process/deamon running more than once.

It looks like your tdm2 service is successfully creating the lock when it starts up but is never deleting it, probably due to it crashing shortly after it begins.

I would suggest looking in the script /etc/init.d/tdm2 and find exactly what command it's executing to start up the service and then run that manually. You will probably find it segfaults shortly after startup and leaving a lock file behind which messes with the status.