Loads of warnings about invalid packets

[varac]

I'm using spotifyd which uses librespot, and my journal is full (>25k log entires a day) with these warnings:

Apr 25 20:26:59 ro… spotifyd[5020]: couldn't parse packet from V4(X.X.X.182:47258): type 10240 is invalid
Apr 25 20:26:59 ro… spotifyd[5020]: couldn't parse packet from V4(X.X.X.182:47258): type 10240 is invalid

See also https://github.com/Spotifyd/spotifyd/issues/578 for the regarding spotifyd issue.

The host the packets come from is not my laptop which runs spotifyd but a different device in the local network.

Please (add an option to) reduce the logging since it literally spams my journal in bulk.

[willstott101]

I think these messages are indicative of a real problem so I would consider them warnings, whether it's a problem and end-user binary actually wants to warn about... I agree with you it should be configurable.

We're posting these warnings with the log crate which as far as I understand it, should allow downstream crates to customize the backend or verbosity or filters etc. You can see how librespot (at least when used as a binary) does this.

As you can see when using env_logger there are even ways for end users to customise the verbosity. It looks like spotifyd is probably using the syslog crate to provide logging, I can't immediately see any such options but I've never really looked into it. If there's some other standard way to provide configurable logging besides the log crate that you know of I'd happily look into it.

As for the root problem, 10240 does indeed look like a totally non-existent message type so something funky might be going on there. If you're happy to try and capture those packets we might find a bug, or just a weird device on your network 🤷‍♂️

Sorry I'm not much more help with this.

[varac]

If there's some other standard way to provide configurable logging besides the log crate that you know of I'd happily look into it.

Unfortunatly I don't but that doesn't mean anything :smile:

If you're happy to try and capture those packets we might find a bug, or just a weird device on your network man_shrugging

Here you go, I used sudo tcpdump -w /tmp/spotify-packets.dump host 10.27.13.182 to capture a few packets, how they are useful:

weird-device.log

[philippgerard]

I have the same issue, but my messages read like this:

Aug 04 08:30:41 manjaro-cinnamon spotifyd[5183]: couldn't parse packet from V4(192.168.178.27:5353): LabelIsNotAscii

[rvendrame]

Same issue here: couldn't parse packet from V4(172.30.32.1:5353): query type 65 is invalid couldn't parse packet from V6([fe80::83e:4973:ee4f:1e8b]:5353): query type 65 is invalid.

[dstivanov]

I also have the same message reading:

Mar 06 09:37:35 couldn't parse packet from V4(192.168.1.90:51488): HeaderTooShort
Mar 06 09:38:40 couldn't parse packet from V4(192.168.1.90:58705): HeaderTooShort
Mar 06 09:38:41 Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }

Restarting the service helps.

[kekonn]

This problem is still there at the time of writing. Is this project even active? Seems like it's just a logging statement that should be turned down in verbosity.