Bugzilla – Bug 5607
Debugging settings not shown after restart
Last modified: 2008-12-18 11:12:53 UTC
If I in "Server Settings/Debugging" choose to "Save debugging settings for use at next application restart" this works correctly and the logging is enabled after the restart. However, if I after the restart goto "Server Settings/Debugging" that dialog doesn't show the values actually used, it always seems to show the default values after a restart of SqueezeCenter.
I use this regularly and haven't run into this since the "save settings" option was introduced. Try adding the following line before the FOREACH line in HTML/EN/settings/server/debugging.html: [% USE Dumper; Dumper.dump_html(categories) %] The page will now be loaded with the debug hash, so we can see if the form is somehow mot matching up for the current states, or if the server is providing invalid info. If you are seeing the debug output expected, then the debug state should be correct.
The HASH shows a lot of entries, but the particular one I'm interested in shows: ======================== { 'current' => 'WARN', 'name' => 'plugin.customscan', 'label' => 'Custom Scan' }, ======================== The log.conf file contains the following row: log4perl.logger.plugin.customscan = DEBUG The page shows WARN So, as you see the information visible in the page is not the one available in the log.conf file. I'm not sure if this matters, but the log files is stored in a custom directory since I start SlimServer with: --logdir /var/lib/slimserver/Logs70 The log.conf file is also stored in this directory. After I change the logging level in the user interface it is shown correctly until I restart SlimServer, after the restart the visible information in the Debugging page reverts back to the defaults. I know the logging level stored in the log.conf file is used, because I see the DEBUG loggging entries from plugin.customscan in the generated server.log file.
the logdir param might be the key. it IS what makes things different from my system. Just to eliminate plugin issues, are you seeing the same WARN default for the core server debug options as well? I'll need one that I can verify on my setup (or anyong at SD too for that matter.) Try an easy one, prefs.
(In reply to comment #3) > the logdir param might be the key. it IS what makes things different from my > system. Just to eliminate plugin issues, are you seeing the same WARN default > for the core server debug options as well? I'll need one that I can verify on > my setup (or anyong at SD too for that matter.) Try an easy one, prefs. > It seems to work for the server properties, so plugin properties might be handled differently. network.http -> This works, it shows the same level as in log.conf database.info -> This works, it shows the same level as in log.conf plugin.randomplay -> This doesn't work, it shows the default value independent on which value is in log.conf You should be able to verify any corrections with plugin.random play as it has the same problem.
*** Bug 6132 has been marked as a duplicate of this bug. ***
Try change 14884
(In reply to comment #6) > Try change 14884 > This seems to have fixed it, so I'll mark this as fixed.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.