Short tip: osa-dispatcher dead but subsys locked

Recently I had a issue when trying to use the OSA dispatcher integrated in Spacewalk, Red Hat Satellite and SUSE Manager. The software was unable to push actions to registered client systems - it seems that there was a problem with the appropriate service:

1# service jabberd status
2router dead but subsys locked
3sm (pid 5294) is running...
4c2s (pid 5301) is running...
5s2s (pid 5308) is running...
6
7# service osa-dispatcher status
8osa-dispatcher dead but subsys locked

After my previous troubleshooting ideas were unsuccessful I had to use Google for researching. I found the solution for the issue in the following mailing list: [click me!]

It seems like a recent crash of my VM also destroyed the Berkely database of the jabber service. Deleting the appopriate files results (according to the mailing list entry) in automatically re-creating the needed files.

After deleting those files the OSA dispatcher was able to work again:

1# rm -rf /var/lib/jabberd/db/* ; service jabberd restart
2# service jabberd restart
3# service osa-dispatcher restart