[SOLVED] MPD running locally leaves PID behind on shutdown

saturn_knight · 2014-04-12 02:08:15

I've been having this issue for a while and I'm not sure what's wrong.

My MPD is configured as per the wiki to run as the local user, and I have the following line in .profile

# MPD daemon start (if no other user instance exists)
[ ! -s ~/.config/mpd/pid ] && mpd

When I restart, or shutdown and do a clean start of my system MPD doesn't start because the PID file is left behind from the previous process.

I've tried to simplify the process for testing

1) boot to console
2) start MPD manually
3) execute systemctl reboot

When the system comes back up the old PID file is still there, preventing MPD from autostarting.
Does anyone have any ideas on what might be keeping my system from shutting down the process cleanly?

Last edited by saturn_knight (2014-04-12 07:44:48)

jasonwryan · 2014-04-12 02:22:19

Why don't you just start it with a service file and let systemd manage the process?

cris9288 · 2014-04-12 02:35:40

I agree. Systemd service is the way to go. Once you have a user instance of sytsemd up and running, the service file is quite trivial.

Rasi · 2014-04-12 07:11:21

jasonwryan wrote:

Why don't you just start it with a service file and let systemd manage the process?

Maybe because of this: https://bbs.archlinux.org/viewtopic.php?id=178793 (thread also includes the solution for a proper mpd service file)

Last edited by Rasi (2014-04-12 07:12:00)

cju · 2014-04-12 07:31:00

Just forget about the pid-thing and write

mpd

instead of

[ ! -s ~/.config/mpd/pid ] && mpd

in your $autostartfile. Sure, that's not the ideal way, but it just works, so I why should I care any further.

saturn_knight · 2014-04-12 07:41:36

Thanks for the recommendations. I was tempted to just run MPD without checking for the PID first, but it was bothering me that it used to work and I don't know what changed. Also, the fact that if MPD isn't being shut down cleanly on shutdown what else might be getting shut down in an unclean state?

The thread Rasi pointed to shows the same problem I was experiencing, not sure why it didn't come up in my searches. Apparently there is an issue with MPD not responding to the shutdown signal properly in some situations. Ultimately, I went ahead and switched to the systemd user startup and it's now remembering my playlists and current state between reboots. I guess I was initially hesitant to use it because the wiki states that it's still unsupported upstream, plus I was afraid there might be a more serious underlying problem that might affect other things on my system.

Thanks again!

jasonwryan · 2014-04-12 07:42:45

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

Arch Linux

#1 2014-04-12 02:08:15

[SOLVED] MPD running locally leaves PID behind on shutdown

#2 2014-04-12 02:22:19

Re: [SOLVED] MPD running locally leaves PID behind on shutdown

#3 2014-04-12 02:35:40

Re: [SOLVED] MPD running locally leaves PID behind on shutdown

#4 2014-04-12 07:11:21

Re: [SOLVED] MPD running locally leaves PID behind on shutdown

#5 2014-04-12 07:31:00

Re: [SOLVED] MPD running locally leaves PID behind on shutdown

#6 2014-04-12 07:41:36

Re: [SOLVED] MPD running locally leaves PID behind on shutdown

#7 2014-04-12 07:42:45

Re: [SOLVED] MPD running locally leaves PID behind on shutdown

Board footer