-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server fills the entire disk with logs #1183
Comments
LMS or the operating system should rotate the log files automatically. What log file is this? It doesn't look like one generated by LMS itself. |
This is daemon.log, managed by syslog (which also rotates logs automatically). It collects messages from LMS. It started with thread 'main' panicked at 'Spotify servers returned an error. Restart librespot.', core/src/mercury/mod.rs:205:13 Another part of the messages (although it's still the same for the whole 10GB of logs): Oct 16 21:01:58 LMS squeezeboxserver[421]: : 6156976 0x : 0x0x524810 51c8105ec810 - - - 0x |
I also found this issue here: https://forums.slimdevices.com/forum/user-forums/3rd-party-software/112342-spotty-4-7-0#post1514107 |
I also use your Spotty plugin (which is great btw ;), don't know whether it's related somehow. |
I'd need more of that log file to understand where those numbers are coming from. They might be a stack trace or something. But if the spotty was failing all the time, you'd noticed that spotty wouldn't work. Maybe you can send me a compressed copy of the most recent few hundred lines? |
here is the link to the compressed log containing only messages from LMS: maybe line 567 could be some lead: 567 Oct 15 07:00:40 LMS squeezeboxserver[421]: 564: thread ' 0xmain5ac810' panicked at ' - Spotify servers returned an error. Restart librespot.', I've been using Spotty for many years on a few devices at home almost every day. I haven't noticed any hiccups or crashes until this occasional incident. |
That file is massive (135M lines). But it looks more like a Spotty issue than LMS. If you have Spotty Connect mode enabled, please disable it. Did that even work? It looks as if the connect helper was constantly crashing. Did you build the Spotty helper yourself? Or is this a regular installation? |
I've used Spotty Connect only occasionally, but it worked just fine. I can disable it as I don't use it often. I didn't build anything myself, I use only regular installation from packages. As I mentioned before, this issue happened to me already once, maybe twice, in the last, let's say, 6-8 years using LMC on my RaspberryPi. It can be some coincidence because normally everything goes smoothly. But apparently, there is some hidden glitch somewhere. |
I am running Raspberry Pi 4 Model B Rev 1.1
logitechmediaserver 8.5.2 deb package
In the last 6 years of running LMS, this happened to me for the second time:
thread 'main' panicked at 'Spotify servers returned an error. Restart librespot.', core/src/mercury/mod.rs:205:13
in syslog:
and then:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x712514810: -
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x1325ac810: -
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x713514810: -
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x1335ac810: -
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x514810 - 714:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x1345ac810: -
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x 514810715 - :
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x1355ac810: -
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x 514810716 - :
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x5ac810 - 136:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7170x514810: -
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x 5ac810137 - :
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7180x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 138:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7190x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 139 - :
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7200x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 140:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7210x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 141:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7220x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 142:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7230x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 143:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x724514810: - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 144:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7250x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 145:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x726514810: - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 146:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 7270x: 514810 - 0x
Oct 15 07:00:40 LMS squeezeboxserver[421]: 5ac810 - 147:
Oct 15 07:00:40 LMS squeezeboxserver[421]: 0x728514810: - 0x
10GB of logs like this until the HDD was full on the server
The text was updated successfully, but these errors were encountered: