Very obscure MPD error

anadyr · 2010-03-04 19:57:23

Hi,

I have been running mpd for a few months and it works (or at least, worked) excellently. But now seeking doesn't work anymore. When I want to seek inside a song, it crashes with error code 17. I cannot reconnect again (error code 13) until I manually restart the mpd daemon. This is the error from the logs:

mpd: src/decoder_api.c:93: decoder_command_finished: Assertion `dc.command != DECODE_COMMAND_SEEK || dc.seek_error || decoder->seeking' failed.

Does anybody know what had happened? I cannot find anything on the internet, except an mpd bugreport with status "closed (unable to reproduce)", which isnt very promising.

Last edited by anadyr (2010-03-04 19:58:49)

Rasi · 2010-03-04 22:46:45

might be a bug. Can you recompile mpd with this PKGBUILD: http://ix.io/Om and see if it still happens?

If yes do this:

install gdb with pacman.
run gdb /usr/bin/mpd
in gdb type "run --stdout --no-daemon --verbose"
let mpd crash
now type "thread apply all bt" and hit enter until all info is shown.

the resulting stuff submit to mpds bug tracker including some information like file type and such.

Last edited by Rasi (2010-03-04 22:47:09)

anadyr · 2010-03-05 16:47:10

I compiled mpd with this PKGBUILD and installed it, but it doesnt work:

/usr/bin/mpd /etc/mpd.conf
unrecognized parameter in config file at line 38: error_file

mpd --create-db
** ERROR **: option parsing failed: Unknown option --create-db
aborting...
Aborted

On the first error: I commented line 38 in mpd.conf (error_file), and now starting the mpd daemon does not give an error. However, it does not work: the music does not start playing, and I cannot connect to the daemon...
On the second error: no clue why that happens.

kgas · 2010-03-05 16:56:45

for database creation use mpd --create-db <path/to/configfile>. Most of the mpd trouble boils down to permission issues imho. The preferred method to start the mpd is either from the sessions auto start feature or .xinitrc instead of deamon.

bobdob · 2010-03-05 17:44:14

anadyr wrote:

mpd --create-db
** ERROR **: option parsing failed: Unknown option --create-db
aborting...
Aborted

This error is because in git, mpd has changed the way the database is created. You no longer needs to initially create a db with that command.

Rasi · 2010-03-05 18:34:28

anadyr wrote:

I compiled mpd with this PKGBUILD and installed it, but it doesnt work:
/usr/bin/mpd /etc/mpd.conf
unrecognized parameter in config file at line 38: error_file
mpd --create-db
** ERROR **: option parsing failed: Unknown option --create-db
aborting...
Aborted
On the first error: I commented line 38 in mpd.conf (error_file), and now starting the mpd daemon does not give an error. However, it does not work: the music does not start playing, and I cannot connect to the daemon...
On the second error: no clue why that happens.

when mpd does not give an error it is started.

Please put "mpd: ALL" in your /etc/hosts.allow file, then you will be able to connect

anadyr · 2010-03-05 20:34:18

That doesn't work.
I now have two different packages: mpd (from the Arch depository), and mpd-git (from the PKGBUILD above). When I use the first one, things work fine; at boot the music immediately starts playing. When I use the second git-one, mpd starts without any error, but the music does not start playing, and I cannot connect to the daemon.

I explicitly did not change any configs/permissions (apart from commenting line 38 in mpd.conf, which apparently has no effect on mpd behavior)

Rasi · 2010-03-05 22:19:06

anadyr wrote:

That doesn't work.
I now have two different packages: mpd (from the Arch depository), and mpd-git (from the PKGBUILD above). When I use the first one, things work fine; at boot the music immediately starts playing. When I use the second git-one, mpd starts without any error, but the music does not start playing, and I cannot connect to the daemon.
I explicitly did not change any configs/permissions (apart from commenting line 38 in mpd.conf, which apparently has no effect on mpd behavior)

this is EXACTLY what should be worked around by adding that line to /etc/hosts.allow (and works here just fine)

anyway, since the stable package works for you, i consider this as solved

Last edited by Rasi (2010-03-05 22:20:30)

anadyr · 2010-03-06 09:10:19

I added mpd: ALL to hosts.allow and it doesnt work. Plus the stable package works, except seeking, and that's why I started this thread...
In other words: no progress yet.

bobdob · 2010-03-06 10:56:13

What file type are you trying to play? And if possible could you upload a file that doesn't work, so others can test.

anadyr · 2010-03-06 16:39:32

It seems to occur with every file. I use have 192kbps mp3, made by grip/lame.

gazj · 2010-05-03 18:24:09

Damm, have the same problem with seeking, was hoping the forums were going to throw up the answer, oh well I will keep looking and report any findings.

Arch Linux

#1 2010-03-04 19:57:23

Very obscure MPD error

#2 2010-03-04 22:46:45

Re: Very obscure MPD error

#3 2010-03-05 16:47:10

Re: Very obscure MPD error

#4 2010-03-05 16:56:45

Re: Very obscure MPD error

#5 2010-03-05 17:44:14

Re: Very obscure MPD error

#6 2010-03-05 18:34:28

Re: Very obscure MPD error

#7 2010-03-05 20:34:18

Re: Very obscure MPD error

#8 2010-03-05 22:19:06

Re: Very obscure MPD error

#9 2010-03-06 09:10:19

Re: Very obscure MPD error

#10 2010-03-06 10:56:13

Re: Very obscure MPD error

#11 2010-03-06 16:39:32

Re: Very obscure MPD error

#12 2010-05-03 18:24:09

Re: Very obscure MPD error

Board footer