Startup error mpd connection not working #64
Comments
|
I went back to myMPD 4.3.0 (6f2edb3)and it worked. It looks that version updated how systemd loads myMPD and I had to fix a couple things in /etc/mympd/options before it would start. I will try and work through versions to see what changed that broke things (or what brought out something not right in my system). |
|
hi john, /etc/mympd/options are not used anymore. All configuration is done through /etc/mympd/mympd.conf. The error "Error opening /var/lib/mympd/tmp/playlist.tmp" seems the problem. Exists the directory /var/lib/mympd/tmp/ and myMPD has the rights to write to it? |
|
Thanks. myMPD did not have permissions so I changed it to this: drwxrwxr-x 2 nobody mympd 4096 Oct 7 16:26 /var/lib/mympd/tmp Previously it was owned by mympd and group was r-w. This got things to go farther. See below for full log which shows a retry of some sort that ends in a seg fault. However, I am not sure what user/permissions should be in general. My /etc/mympd/mympd.conf has this: #myMPD user The log below shows this being used when accessing some files. However from how some files files are installed they are owned by "mympd". For example, /var/lib/mympd/tmp was owned by mympd until I changed it. Before I start changing things further it probably makes sense that I get that understanding first. sudo ./mympd /etc/mympd/mympd.conf |
|
All directories and files under /var/lib/mympd must be writeable by your mympd user. It seems that myMPD can't get the last-modified value from songs in your database. |
|
git log Installing this version seemed to change my perms...so: sudo chown -R nobody /var/lib/mympd Results are different with this version (emphasis added on first error occurrence): sudo ./mympd /etc/mympd/mympd.conf [snip a bunch of repeated attempts; leave some in] MPD Connecting to 127.0.0.1:6600 |
|
Can you run mpd with verbose logging enabled and post the messages of mpd.log? |
|
Attached is from the first (and only time) I attempted to start myMPD after starting mpd: |
|
The error in the log file is: myMPD is iterating through all songs to find the last-modified songs. It seems this doesn't work on very large databases. myMPD 4.3.1 will use a better approach to find the newest songs in database. In the meanwhile you can delete Hopefully myMPD 4.3.1 will be released in this week. |
|
The last commit should fixes your issue. Please reopen this issue, if not. |
|
That fixed it...thanks! Here is the startup: sudo ./mympd /etc/mympd/mympd.conf |
Describe the bug
I just now undated to most recent version in git and when I access the myMPD user interface I can't browse my music and no information is shown for my running mpd.
When I start at the command line I see this:
sudo ./mympd /etc/mympd/mympd.conf
Parsing config file: /etc/mympd/mympd.conf
Starting myMPD 4.3.0
Document root: /usr/share/mympd/htdocs
Error opening /var/lib/mympd/state/notificationWebError opening /var/lib/mympd/state/notificationPageError opening /var/lib/mympd/state/jukeboxModeError opening /var/lib/mympd/state/jukeboxPlaylistError opening /var/lib/mympd/state/jukeboxQueueLengthDroping privileges to nobody
Listening on http port 8081
MPD Connecting to 127.0.0.1:6600
MPD connected.
MPD protocoll version: 0.20.0
MPD supported tags: Artist ArtistSort Album AlbumSort AlbumArtist AlbumArtistSort Title Track Name Genre Date Composer Performer Disc MUSICBRAINZ_ARTISTID MUSICBRAINZ_ALBUMID MUSICBRAINZ_ALBUMARTISTID MUSICBRAINZ_TRACKID MUSICBRAINZ_RELEASETRACKID
myMPD enabled tags: Artist Album AlbumArtist Title Track Genre Date Composer Performer
Error opening /var/lib/mympd/tmp/playlist.tmpMPD X: Cannot send a new command while receiving another response
MPD X: Cannot send a new command while receiving another response
There is nothing further even when I navigate through myMPD screens.
To Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: