jabber family not reporting pids to /var/run/jabber

[kitchen]

I've got jabber 1.4.3.-3ubuntu1, jabber-jit 1.1.6-9build2, jabber-jud 0.5-3, jabber-muc 0.6.0-2, jabber-yahoo 2.3.2-1 all running, but they are not logging their pids into /var/run/jabber/$prog.pid as the assorted init scripts indicate they should

This makes it exceedingly difficult to restart them gracefully when the main jabberd segfaults (https://launchpad.net/distros/ubuntu/+source/jabber/+bug/35427 and https://launchpad.net/distros/ubuntu/+source/jabber/+bug/35953) because restart tries to kill on the pid files...which aren't there.

It's not a big deal for the main process that just seg'd but the others don't respond well to multiple servers attempting to run in the same space.

[Ronny Bangsund (ronnyb)]

This happens on jabberd2_2.0s8-0ubuntu5_i386 for me.
Shutting down the server is a case of "hunt the PID".

[Ronny Bangsund (ronnyb)]

Nevermind, found there was a fix released:
https://launchpad.net/distros/ubuntu/+source/jabberd2/+bug/43899

[Markus Bertheau (mbertheau)]

Correct solution is to change /etc/init.d/jabber:

--- /etc/init.d/jabber.orig 2007-04-30 16:10:23.000000000 +0700
+++ /etc/init.d/jabber 2007-04-30 16:16:38.000000000 +0700
@@ -15,6 +15,7 @@
 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
 DAEMON=/usr/sbin/jabberd
 NAME=jabberd
+DAEMONUSER=jabber
 DESC=jabberd
 CONF=/etc/jabber/jabber.xml
 PID=/var/run/jabber/jabber.pid
@@ -48,7 +49,11 @@
       check_pid

       echo -n "Starting $DESC: "
- [ ! -d `dirname $PID` ] && mkdir `dirname $PID`
+ if [ ! -d `dirname $PID` ]; then
+ mkdir `dirname $PID`
+ chown $DAEMONUSER `dirname $PID`
+ fi
+
       cd /usr/lib/jabber/
       start-stop-daemon -b -c jabber:adm --start --quiet \
          --pidfile $PID --exec $DAEMON $CMDLINE

[Daniel T Chen (crimsun)]

Note that the patch needs to be much more careful with the path of dirname.