Connection to MPD failed

[christopherr]

Problem: After a power outage, Moode Fails to load library with error Connection to MPD failed.  Moode version 5.1

I thought this might be an issue because I was using MPD 0.21, however I reverted to 0.20 and the issue still occurs consistently after power outages.  I think it might be related to the fact that my NAS is still booting when Moode starts. I cannot access the library config pages either.  Rebooting the pi over ssh does not help either. This was not an issue with Moode 4.X.  Any help for debugging?

Update:

Code:

# service mpd status
● mpd.service - Music Player Daemon
  Loaded: loaded (/lib/systemd/system/mpd.service; disabled; vendor preset: enabled)
  Active: inactive (dead)

May 08 09:49:02 moode systemd[1]: [/lib/systemd/system/mpd.service:32] CPU scheduling priority is out of range, ignoring: 43

[Tim Curtis]

What does log output show?

cat /var/log/moode.log
cat /var/log/mpd/log

[TheOldPresbyope]

@christopherr

How long did you wait after rebooting?

When I tried to repro your problem by turning off a NAS which was mounted in moOde r5.1 running on an RPi3B+ and rebooting moOde, I first saw what you report: unresponsive UI and identical service report but after some time more than 1 second and less than a minute (I wasn't watching the clock), the UI came alive and the service report showed mpd was active.

Regards,
Kent

[christopherr]

What does log output show?

cat /var/log/moode.log
cat /var/log/mpd/log

cat /var/log/moode.log

Code:

20190508 091222 worker: - Start
20190508 091222 worker: Successfully daemonized
20190508 091223 worker: Integrity check (failed)
20190508 091223 worker: Exited
20190508 091418 command/moode: Connection to MPD failed
20190508 091421 command/moode: Connection to MPD failed
20190508 091436 lib-config: Connection to MPD failed
20190508 091447 command/moode: Connection to MPD failed
20190508 091450 command/moode: Connection to MPD failed
20190508 091458 audioinfo: Connection to MPD failed
20190508 091538 command/moode: Connection to MPD failed
20190508 091541 command/moode: Connection to MPD failed
20190508 091558 command/moode: Connection to MPD failed
20190508 091601 command/moode: Connection to MPD failed
20190508 091618 command/moode: Connection to MPD failed
20190508 091621 command/moode: Connection to MPD failed
20190508 091638 command/moode: Connection to MPD failed
20190508 091642 command/moode: Connection to MPD failed
20190508 091723 command/moode: Connection to MPD failed
20190508 091726 command/moode: Connection to MPD failed
20190508 091736 command/moode: Connection to MPD failed
20190508 091739 command/moode: Connection to MPD failed
20190508 091924 lib-config: Connection to MPD failed

cat /var/log/mpd/log => empty

[Tim Curtis]

You got bit by the Integrity check :-0 Send me a PM and I'll explain how to deal with it.

[Tenbagger]

I have a similar problem after installing 5.2 (used 5.0). 

UI is sluggish. The Library tab gives error message "lib-config: Connection to MPD failed".

Status on MPD is inactive (dead), with the message "CPU scheduling priority is out of range, ignoring: 43". 

This is the output from cat /var/log/moode.log:
20190512 171136 worker: - Start
20190512 171136 worker: Successfully daemonized
20190512 171324 lib-config: Connection to MPD failed
20190512 171954 command/moode: Connection to MPD failed
20190512 171957 command/moode: Connection to MPD failed
20190512 172003 command/moode: Connection to MPD failed
20190512 172006 command/moode: Connection to MPD failed
20190512 172011 command/moode: Connection to MPD failed
20190512 172014 command/moode: Connection to MPD failed
20190512 172136 command/moode: Connection to MPD failed
20190512 172139 command/moode: Connection to MPD failed

[Tim Curtis]

Log shows a 2 minute gap between the two records below. There is nothing in the code that would account for that so I'd suggest starting with a fresh SDCard and then boot up and examine the log before making any configuration changes.

20190512 171136 worker: Successfully daemonized
20190512 171324 lib-config: Connection to MPD failed

[Paulnd]

Hi,

I have a similar problem after updating to 5.2

this error repeats every few seconds in the daemon log and syslog
May 12 18:26:12 moode systemd[1]: Started Music Player Daemon.
May 12 18:26:12 moode mpd[10931]: exception: unrecognized parameter in config file at line 27: replay_gain_handler
May 12 18:26:12 moode systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
May 12 18:26:12 moode systemd[1]: mpd.service: Unit entered failed state.
May 12 18:26:12 moode systemd[1]: mpd.service: Failed with result 'exit-code'.

[Tenbagger]

Log shows a 2 minute gap between the two records below. There is nothing in the code that would account for that so I'd suggest starting with a fresh SDCard and then boot up and examine the log before making any configuration changes.

20190512 171136 worker: Successfully daemonized
20190512 171324 lib-config: Connection to MPD failed

Thanks! Right away.

[Tim Curtis]

Hi,

I have a similar problem after updating to 5.2

this error repeats every few seconds in the daemon log and syslog
May 12 18:26:12 moode systemd[1]: Started Music Player Daemon.
May 12 18:26:12 moode mpd[10931]: exception: unrecognized parameter in config file at line 27: replay_gain_handler
May 12 18:26:12 moode systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE
May 12 18:26:12 moode systemd[1]: mpd.service: Unit entered failed state.
May 12 18:26:12 moode systemd[1]: mpd.service: Failed with result 'exit-code'.

Post contents pf moode.log

cat /var/log/moode.log