Bugzilla – Bug 15563
Logging is no longer persistent in SB Server7.5.0 r29960
Last modified: 2010-04-08 17:24:56 UTC
"Save logging settings for use at next application restart " doesn't work. All logging levels reset to a default level define for each category following a server reboot. Also the tick box in the UI is unticked, which means the setting is either not being stored in the prefs at all, or not being read back and used within the UI.
The "save logging settings" checkbox has never been sticking. But the logging prefs are working fine for me: if I tick above box, then set some log to debug, it will still be set to debug after server restart.
BTW: this has nothing to do with SP logging. You're talking about the web UI, aren't you?
Not sure what SP logging is. I was trying to capture logs for the bug 15562 that I logged over the weekend. As such I tried upping the Jive logging level, shutdown the server, deleted the server.log file and restarted the server. During testing I discovered that the Jive log level had reset itself back to Warn, so I wasn't capturing anything useful. I must go back and retry with Debug set.
jive indeed seems not to stick. Can you reproduce this for all/other log settings?
== Auto-comment from SVN commit #29966 to the slim repo by michael == == https://svn.slimdevices.com/slim?view=revision&revision=29966 == Bug: 15563 Description: add jive debugging to the list of default log categories
Michael, is that a fix for this bug? Or just a related checkin? Thanks!
== Auto-comment from SVN commit #30067 to the repo by mherger == == https://svn.slimdevices.com/?view=revision&revision=30067 == Bug: 15563 Description: still not the fix, but some more cleanup of log labels and classes
== Auto-comment from SVN commit #30124 to the repo by mherger == == https://svn.slimdevices.com/?view=revision&revision=30124 == Fixed Bug: 15563 Description: partially backport change 30121 which fixes this issue
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!