Bug 8801 - log filling with 401 errors when password-protected SC instance on subnet
: log filling with 401 errors when password-protected SC instance on subnet
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Misc
: 7.1
: PC Other
: P5 normal (vote)
: 7.x
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-18 18:11 UTC by Peter Watkins
Modified: 2009-07-31 10:25 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Watkins 2008-07-18 18:11:58 UTC
Running 7.2ns on the same subnet as a 7.0 instance that has password protection enabled with default log settings (haven't touched the logging prefs since running through the web setup wizard), every minute I get two log entries like this:

[08-07-18 21:05:15.0247] Slim::Networking::Async::HTTP::_http_error (264) Error: [401 Unauthorized]
[08-07-18 21:05:15.0260] Slim::Networking::Discovery::Players::_players_error (134) Unable to get players: 401 Unauthorized

These messages shouldn't show up -- not at this frequency! -- at the default log levels. Maybe at the INFO level, certainly at DEBUG, but not at WARN/ERROR/FATAL
Comment 1 Michael Herger 2008-07-20 13:31:25 UTC
Andy - maybe we should only report the error when there's no error handler and leave the logging to the handler? Or add an additional parameter to set logging level on a per query level, allowing callers to suppress these messages?

But then it's an information support might be interested in, as it will tell them why a user doesn't see other players. If we left the error logging to the local handler, this could do some more intelligent handling like not checking every other minute, or only logging once per hour.
Comment 2 Andy Grundman 2008-08-01 08:20:34 UTC
Fixed in 7.2 change 22297.  Async will now only report errors if the caller doesn't provide an onError callback.
Comment 3 Ross Levine 2008-10-10 15:53:40 UTC
Verified in 7.2.1 - 23496
Comment 4 James Richardson 2008-12-15 12:34:19 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 5 Chris Owens 2009-07-31 10:25:01 UTC
Reduce number of active targets for SC