The jabberd2 init script starts all services are listed in /etc/jabber/jabberd.cfg. The stop script stops all processes that create a .pid file in /var/run/jabber. But the mu-conference init script creates a .pid file in /var/run/jabber too. The jabberd2 init script should not kill all processes with .pid files in /var/run/jabber, but only processes are listed in /etc/jabber/jabberd.cfg. By the way: I don't understand why it is not possible to restart only one of components whit the init script. It should happen give one init script for each component and one script that depends on other scripts. Now it is possible to restart s2s component and no user are logged out. Only a idea. Reproducible: Always Steps to Reproduce: 1. start jabberd2 2. start mu-conference 3. restart jabberd2 Actual Results: mu-conference not running after restart jabberd2 Expected Results: jabberd2 init script don't touch the mu-conference process. # rc-config start jabberd Starting init script * Starting Jabber Server ... * Starting router (/etc/jabber/router.xml) ... [ ok ] * Starting sm (/etc/jabber/sm.xml) ... [ ok ] * Starting s2s (/etc/jabber/s2s.xml) ... [ ok ] * Starting c2s (/etc/jabber/c2s.xml) ... [ ok ] # rc-config start mu-conference Starting init script * Starting MUC Jabber Transport ... [ ok ] # rc-config restart jabberd Restarting init script * Stopping Jabber Server * Stopping c2s ... [ ok ] * Stopping mu-conference ... [ ok ] * Stopping router ... [ ok ] * Stopping s2s ... [ ok ] * Stopping sm ... [ ok ] * Starting Jabber Server ... * Starting router (/etc/jabber/router.xml) ... [ ok ] * Starting sm (/etc/jabber/sm.xml) ... [ ok ] * Starting s2s (/etc/jabber/s2s.xml) ... [ ok ] * Starting c2s (/etc/jabber/c2s.xml) ... [ ok ]
Seems to be the same issue like #241472.
*** This bug has been marked as a duplicate of bug 241472 ***
