You are not logged in.
After months of stability, mpd recently started exiting while playing. I started it with the verbose logging option and experienced the following.
It started playing at 17:29 and crashed at 17:31. I'd love to figure out why it shutdown by itself:
$ tail -f ~/.mpd/mpd.log
Jul 11 17:29 : avahi: Initializing interface
Jul 11 17:29 : avahi: Client changed to state 101
Jul 11 17:29 : avahi: Client is CONNECTING
Jul 11 17:29 : state_file: Loading state file /home/facade/.mpd/mpdstate
Jul 11 17:29 : decoder_thread: clearing mixramp tags
Jul 11 17:29 : decoder_control: mixramp_start = NULL
Jul 11 17:29 : decoder_control: mixramp_prev_end = NULL
Jul 11 17:29 : decoder_thread: probing plugin mad
Jul 11 17:29 : playlist: queue song 1:"jacquie-albums/track.mp3"
Jul 11 17:29 : mad: detected LAME version 3.92 ("LAME3.92 ")
Jul 11 17:29 : mad: LAME peak found: 0.000000
Jul 11 17:29 : mad: encoder delay is 576, encoder padding is 1728
Jul 11 17:29 : decoder: audio_format=44100:24:2, seekable=true
Jul 11 17:29 : output: opened plugin=pulse name="pulse audio" audio_format=44100:16:2
Jul 11 17:29 : output: converting from 44100:24:2
Jul 11 17:31 : state_file: Saving state file /home/facade/.mpd/mpdstate
Jul 11 17:31 : output: closed plugin=pulse name="pulse audio"
Jul 11 17:31 : avahi: Shutting down interface
Jul 11 17:31 : listen: listen_global_finish called
Jul 11 17:31 : db_finish took 0.000000 secondsOffline
Hmm, that is odd. Try running
mpd --no-daemon --stderr --verbosefrom the command line and see if that sheds any light on the issue.
Offline
Isn't that going to repeat the experiment I ran above?
Offline