server filling syslog with messages

[dborn]

I'm also getting my syslog flooded by messages like this, several times per second:
"squeezeboxserver[932]: #011file:///var/lib/squeezeboxserver/prefs/clientplaylist_000000000000.m3u doesn't exist on disk - skipping!"
16145 lines out of 98886 are from squeezeboxserver.
(some of?) the same messages also appear in the /var/log/squeezeboxserver/server.log file

All my debug settings are the default values.

[Millwood]

Still putting what look like scanner messages in syslog. Examples:

Sep 25 04:00:25 aptiva squeezeboxserver[634]: [22-09-24 04:00:25.2507] Slim::Plugin::xPL::Plugin::xplExecuteCallback (619) Warning: Called without a client: rescan
...
Sep 25 04:00:25 aptiva squeezeboxserver[634]: [22-09-24 17:00:43.3916] Slim::Utils::Scanner::Local::__ANON__ (288) Get changed tracks count

This is triggered by a scheduled rescan.

[Millwood]

thanks but I was concerned about where the log was going. I expected it to be in the squeezebox logs, not in syslog.
i will try your advice anyway.

[mherger]

server filling syslog with messages

> Suddenly, I'm seeing messages like:
> Sep 23 01:34:40 aptiva squeezeboxserver[634]: [22-09-22 18:28:08.7245]
> Slim::Web::Graphics::artworkRequest (339) Looking for:
> html/images/Players/receiver.jpg in skin Default
> in /var/log/syslog.

Check your settings in Settings/Advanced/Logging. You can select the
Default settings at the top, and make sure you check the "keep during
reboot" or similar box.

[Millwood]

server filling syslog with messages

Suddenly, I'm seeing messages like:
Sep 23 01:34:40 aptiva squeezeboxserver[634]: [22-09-22 18:28:08.7245] Slim::Web::Graphics::artworkRequest (339) Looking for: html/images/Players/receiver.jpg in skin Default
in /var/log/syslog.
I'm on Logitech Media Server Version: 8.2.1 - 1652959290 @ Thu 19 May 2022 01:30:57 PM CEST
Debian 10 (buster)
Is there a setting I'm missing?

[Millwood]

> Has the OP tried putting the line -SLIMOPTIONS="--quiet"- in the file
> -/etc/default/logitechmediaserver- ?
When the log file is filling up the filesystem then you should first of
all figure out why it is logging that much! In normal use there should
be very little output. Either reset the logging options, or fix whatever
is causing the log statements (and that's what the thread initially was
about).