Hi. I have a pure systemd install (no rc.conf).
I installed murmur form "community" and started it with
systemctl start murmur
The service starts but restarts every two minutes or so with these lines in journalctl:
PID file /run/murmur/murmur.pid not readable (yet?) after start. murmur.service operation timed out. Terminating. Unit murmur.service entered failed state. murmur.service holdoff time over, scheduling restart.
Last edited by SoleSoul (2012-08-18 22:42:41)
This is from the output of 'ls -l' on /var:
lrwxrwxrwx 1 root root 6 Jul 21 02:46 run -> ../run/
I think it is ok.
I know nothing about murmur. Did you change your config to write the pid somewhere else? is the pidfile being written at all (i assume it isn't)?
You could probably jsut avoid the pidfile all together and run the service in non-forking mode.
[Unit] Description=Mumble Daemon After=network.target [Service] ExecStart=/usr/sbin/murmurd -fg -ini /etc/murmur.ini [Install] WantedBy=multi-user.target
Your friendly murmur packager here. This is likely a packaging issue as I have no clue about systemd. Please report a bug and if you are awesome, find a fix as well.
There was an inconsistency in the behavior of murmur today. I tried to run it again after a reboot and after complaining once
systemd: PID file /run/murmur/murmur.pid not readable (yet?) after start.
the daemon stayed alive and working.
If the problem comes again I'll report it as a bug but for now I'm not sure what's happening.
Thanks for your help.
Bumping as I've got exactly the same issue. Looks like no pidfile is created in the first place as falconindy guessed.
I would like to report that I since switched to systemd on my server and murmur works just fine. If you guys find a bug, fix it and report the fix on the bug tracker.
Same deal. It's periodically killing my server though it seems to run fine. No time to debug yet, but sucks.
I couldn't solve it but to work around the problem and see what's going on I run it like that as root:
murmurd -fg -ini /etc/murmur.ini
Tell me what systemctl status murmur gives you. Guys, I can't reproduce the problem with my setup. You need to give me logs at least to figure out what is going on.
I now use murmur-ice from the AUR, but my problem was resolved after manually creating /run/murmur/murmur.pid, setting permissions, and restarting the systemd service. Never had a problem after that. Not sure why this wasn't getting created automatically; my /var/run and /run symlinks are correct and no problems with other services.
Sorry I can't be of more help, but it seems to have something to do with a conflict between the service and the desired pid file.
in my case the solution was to comment
Murmur installer just missing to create the directory, just
# mkdir /var/run/murmur
# chown murmur:murmur /var/run/murmur
# chmod 777 /var/run/murmur
/var/run is a symlink to /run and /run is a tmpfs, so I guess those commands should be added as
in the unit file