Response line too large

[diekshouse]

Hi,
I am using moOde/MPD 0.21.16 together with ashuffle.
If the NAS (NFS) is mounted to the library, ashuffle stops running, giving the error message:
"Response line too large".
Any suggestions to solve this problem?
Thanks,
Regards, Herman

[joshkunz]

This issue does not reproduce with MPD 0.21.16 in ashuffle's integration tests. From looking at other instances of this (in other projects), it looks like MPD is sending a line that libmpdclient is choking on. Can you telnet to your MPD instance, and run listall manually?

[diekshouse]

It runs:

[diekshouse]

Although the telnet window tells me this is MPD 0.21.11

[diekshouse]

It looks like it only lists one album from the NAS. The library contained around 400 albums from the NAS at that moment.

[diekshouse]

No, that is not the case. The screen cannot be scrolled back any further.

[joshkunz]

ashuffle depends on a library, libmpdclient to interact with MPD. This error is being thrown by libmpdclient.

libmpdclient has a 4KiB fixed-size buffer for storing MPD responses. If a single line of the response is larger than that buffer, it will return a response line too large error. From your first comment, it looks like ashuffle is able to load your library successfully, but then when it tries to play a song (or manipulate the queue in some other way) MPD is sending back a response with more than 4KiB on a single line.

Since I don't know exactly where this error is coming from, I'll need to add some more logging into the error reporting to track it down. I'll update this bug when there is an ashuffle release with additional error logging.

Until then, one more question: Does this happen immediately when you start ashuffle, or only eventually once ashuffle has been running for a while?

[martinetd]

FWIW they probably could just set log_level "verbose" in their mpd conf file and see where it chokes?
I just tried running mpd with that and you see all commands issued by clients in there.

[diekshouse]

When ashuffle has been started manually, it looks like it is collecting songs till the pool is 3614 (the real number of songs is 31004). This takes a few seconds, after that it returns the messages. So it is not able to run for a while.

[joshkunz]

@diekshouse It looks like you may not be using the latest version of ashuffle. ashuffle now logs out MPD error: when an error is thrown by libmpdclient.

If this still reproduces with the latest ashuffle (v2.1.0 at the time of writing), can you add log_level "verbose" to your mpd.conf as suggested by @martinetd above, and attach the log here?

[joshkunz]

Alright, this hasn't been updated in ~6mo, and it seems to be related to an old version of ashuffle. Since we have a better error message for this failure mode now, and there's not much else ashuffle can do, I'm going to close this out.

@diekshouse if this is still occurring with the latest version of ashuffle (you can easily download the latest version on the releases page), please add log_level "verbose" to your MPD config, and attach the MPD log when re-opening.