2017-02-28 00:09 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002824MPDDefaultpublic2011-03-19 21:21
Assigned Tocirrus 
Product Version 
Target VersionFixed in Versiongit 
Summary0002824: mpd update doesn't give filename information for error messages
DescriptionMy /var/log/mpd.log contains numerous sequential lines like
> Feb 21 10:32 : ffmpeg: Open failed
These lines occur at all logging levels, and are not accompanied by any further information at any logging level, ie there may be many of them in a row, with unrelated update messages at either end.

These seem to be happening when an invalid audio file is scanned by the update routine -- after I deleted one such file, a subsequent update logged one less such line.

Additionally, messages of the type documented in "http://musicpd.org/mantis/view.php?id=2823" are not being associated with a filename.

Presumably the filename of the file for which these errors occurred should be logged at one or more of the verbosity levels.
TagsNo tags attached.
Attached Files




intuited (reporter)

This is happening with mpd 0.15.8, built from the git repo.


cirrus (administrator)

The file name is printed in verbose mode.


intuited (reporter)

Maybe it's not update that's doing it, then. There are some other messages mixed in with the ones I mentioned, I'll post a log sample.


intuited (reporter)

Just uploaded the log file: mpd-log-invalid_codec-clip.txt.gz [^] (2,726 bytes) 2010-02-21 12:55

I'm pretty sure no other clients were running when I compiled that log file. I just opened up the full log file in vim, then did `mpc update`, then copied the new text into a separate file. It's about 13000 lines, which boils down to 81 if you filter out the "Unsupported video codec" lines. Anyway the lines containing "Feb 21 13:48 : ffmpeg: Open failed" are the ones I'm referring to directly; the "Unsupported video codec" ones are mentioned in that other bug report I referenced.

By the way I guess I filed this under the wrong component, sorry about that; it should probably be in the mpd section. Is it possible to move it over there, or should I submit a different bug report? Thanks!


intuited (reporter)

Also just to confirm: that log was made by mpd running in verbose logging mode.


cirrus (administrator)

A log message was added to 0.16.

-Issue History
Date Modified Username Field Change
2010-02-21 18:30 intuited New Issue
2010-02-21 18:30 intuited Status new => assigned
2010-02-21 18:30 intuited Assigned To => cirrus
2010-02-21 18:32 intuited Note Added: 0005368
2010-02-21 18:33 cirrus Note Added: 0005369
2010-02-21 18:33 cirrus Status assigned => closed
2010-02-21 18:33 cirrus Resolution open => no change required
2010-02-21 18:42 intuited Note Added: 0005370
2010-02-21 18:42 intuited Status closed => feedback
2010-02-21 18:42 intuited Resolution no change required => reopened
2010-02-21 18:55 intuited File Added: mpd-log-invalid_codec-clip.txt.gz
2010-02-21 18:57 intuited Note Added: 0005371
2010-02-21 18:57 intuited Note Added: 0005372
2010-02-28 10:53 cirrus Project mpc => MPD
2010-03-22 04:52 Avuton Olrich Status feedback => assigned
2010-11-08 17:52 cirrus Note Added: 0006281
2010-11-08 17:52 cirrus Status assigned => resolved
2010-11-08 17:52 cirrus Fixed in Version => git
2010-11-08 17:52 cirrus Resolution reopened => fixed
2011-03-19 21:21 Avuton Olrich Status resolved => closed
+Issue History