Some jabberd services won't start and their status is 'dead but subsys locked'
Issue
- The jabberd services appear to start ok:
Initializing jabberd processes ...
Starting router: [ OK ]
Starting sm: [ OK ]
Starting c2s: [ OK ]
Starting s2s: [ OK ]
- But checking their status shows the c2s and sm jabber services are dead but subsys locked:
# service jabberd status
router (pid 4853) is running...
sm dead but subsys locked
c2s dead but subsys locked
s2s (pid 4925) is running...
- On another occasion the sm process wouldn't start:
# service jabberd status
router (pid 18672) is running...
sm dead but subsys locked
c2s (pid 18686) is running...
s2s (pid 18693) is running...
Environment
- Red Hat Satellite and Proxy 5.x
- Monitoring
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.