Angelblue05 4130 Posted November 24, 2014 Share Posted November 24, 2014 (edited) I'm stumped. I have all my debug options disabled. My log seems to be stuck in debug mode. Needless to say my logs grow in size very fast. Am I missing something? I've tried to enable/disable debug. I've also restarted my MB server, but nothing works. Please help!Version: MBS 3.0.5441.2, XBMB3C beta 0.9.717Server log: This log was captured from a fresh install. Everything was set with the wizard config.https://www.dropbox.com/s/b24euaefq6kp34e/server-63552612856.txt?dl=0Locations where I've check to make sure debug is disabled: Playback > Transcoding DLNA > Play To Advanced > General XBMB3C debug is disabled XBMC debug is disabled (not that I think it would show on the MBS log) Edited November 26, 2014 by Angelblue05 Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted November 25, 2014 Author Share Posted November 25, 2014 (edited) Edit [11/25]: I updated to the latest MBS beta 3.0.5441.2. With the restart, it seems to have fixed the debug log problem. Yay! I may have spoken too soon... Edited November 25, 2014 by Angelblue05 Link to comment Share on other sites More sharing options...
saitoh183 137 Posted November 26, 2014 Share Posted November 26, 2014 Edit [11/25]: I updated to the latest MBS beta 3.0.5441.2. With the restart, it seems to have fixed the debug log problem. Yay! I may have spoken too soon... @@Luke @@ebr Would you have any ideas or suggestions? This is still happening with latest beta for me as well. I have tried a complete reinstall (removed everything first). Did only the wizard config, then opened log and their was debug lines. I also posted this issue here http://mediabrowser.tv/community/index.php?/topic/13569-log-issues/ but no one ever responded Link to comment Share on other sites More sharing options...
ebr 14905 Posted November 27, 2014 Share Posted November 27, 2014 We just haven't had a chance to look for it yet. Link to comment Share on other sites More sharing options...
saitoh183 137 Posted December 7, 2014 Share Posted December 7, 2014 (edited) @@ebr or @@Luke Did you guys get a chance to look into this...its a very annoying problem and i just dont know what to try anymore Edited December 7, 2014 by saitoh183 1 Link to comment Share on other sites More sharing options...
ebr 14905 Posted December 7, 2014 Share Posted December 7, 2014 I haven't had time to. Honestly, it isn't high on the list. Link to comment Share on other sites More sharing options...
saitoh183 137 Posted December 7, 2014 Share Posted December 7, 2014 I haven't had time to. Honestly, it isn't high on the list. Ok..well is there any registry keys that could cause this? Link to comment Share on other sites More sharing options...
saitoh183 137 Posted December 7, 2014 Share Posted December 7, 2014 I haven't had time to. Honestly, it isn't high on the list. @@ebr I know this issue might not be affecting you or many people but it is affecting me and my sister but even giving us some sort idea of where to look would have been appreciated instead of the answer you gave. Its not like i have been nagging for an answer 15mins after posting...Its those types of answers that make people turn away from posting. I know your all busy with more pressing issues but even if you cant troubleshoot, giving ideas would go a long way in showing that even if its a very minor issue, you still help. 1 Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted December 8, 2014 Author Share Posted December 8, 2014 (edited) If this helps narrow the issue down, it seems the automatic server restart (at midnight) solves the debug issue. Any forced restart, either via the restart button on the dashboard or the server restart plugin sets it to debug again... Is there a difference between the two types of restart? Like my brother said, if you can tell us where to look, we can probably sort of troubleshoot it ourselves. I've been helping this community to the best of my knowledge, it would just be nice to have a little support in return even if the problem is minor. Especially when you have a lot of users, the logs get as big as 1GB on some nights! It's ridiculous.... Edited December 8, 2014 by Angelblue05 Link to comment Share on other sites More sharing options...
Redshirt 1487 Posted December 8, 2014 Share Posted December 8, 2014 It has to be simply a code error and I don't think there's anything to be done until one of the devs can look at it. As ebr said, it's not a priority. That doesn't mean it's not important to you and your brother, it just means that there are things that are currently considered to be a higher priority and even urgent. The team has to prioritize where limited developer resources are spent. If the issue is purely just the size of the logs, you could create a scheduled task in windows (assuming your using windows) to delete the contents of the logs folder every 4 hours. Or whatever time frame suits. Speaking more directly towards saitoh183's comment. What you consider a bug, I and perhaps some of the other devs consider a feature. With debug level logging enabled it means the logs provide more information when an issue is reported. There's no going back to the user and saying this log didn't contain what I need, can you enable this and do that. Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted December 8, 2014 Author Share Posted December 8, 2014 (edited) I understand what you are saying, @@Redshirt. It's just we've been having this issue for well over 3 months (over multiple server builds). At first, we thought it was normal until someone else pointed out that they didn't have debug lines in their server log. Temporary Workaround: I've removed the server restart plugin for the time being since it's the reason why I constantly had debug enabled in my logs. I will also avoid forced restart and make sure to update only right before the midnight auto restart. For now, I suppose it will be good enough to work as a workaround until the matter is resolved. Edited December 8, 2014 by Angelblue05 Link to comment Share on other sites More sharing options...
ebr 14905 Posted December 8, 2014 Share Posted December 8, 2014 Sorry, I wasn't trying to be dismissive. I simply meant that, since this issue doesn't really affect the successful operation of the system, it isn't something we are setting aside other work items to try and find and solve. We will get to it eventually. BTW - your discovery that this appears to happen on restart is very helpful. Thx. Link to comment Share on other sites More sharing options...
ebr 14905 Posted December 8, 2014 Share Posted December 8, 2014 Can one of you guys help us troubleshoot this and set your logging level how you want and then re-start so that it gets re-set - then go look at your actual server config file in an editor. Is the EnableDebugLogging value true or false? Link to comment Share on other sites More sharing options...
saitoh183 137 Posted December 8, 2014 Share Posted December 8, 2014 (edited) Can one of you guys help us troubleshoot this and set your logging level how you want and then re-start so that it gets re-set - then go look at your actual server config file in an editor. Is the EnableDebugLogging value true or false? Its set to false Sorry, I wasn't trying to be dismissive. I simply meant that, since this issue doesn't really affect the successful operation of the system, it isn't something we are setting aside other work items to try and find and solve. We will get to it eventually. Yeah i know..I wish i could have noticed with which build this problem appeared.... Edited December 8, 2014 by saitoh183 Link to comment Share on other sites More sharing options...
saitoh183 137 Posted December 8, 2014 Share Posted December 8, 2014 (edited) I understand what you are saying, @@Redshirt. It's just we've been having this issue for well over 3 months (over multiple server builds). At first, we thought it was normal until someone else pointed out that they didn't have debug lines in their server log. Temporary Workaround: I've removed the server restart plugin for the time being since it's the reason why I constantly had debug enabled in my logs. I will also avoid forced restart and make sure to update only right before the midnight auto restart. For now, I suppose it will be good enough to work as a workaround until the matter is resolved. Yes i can confirm that the log that was created with the midnight restart had no debug lines but my log created after the plugins Restart did have the debug Also my log is now 40mb and cannot be opened via webclient Response Status Error Code OutOfMemoryException Message Exception of type 'System.OutOfMemoryException' was thrown. Stack Trace [GetLogFile: 08-Dec-2014 2:47:19 PM]: [REQUEST: {Name:server-63553603501.txt}] System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.Text.StringBuilder.ToString() at System.IO.StreamReader.<ReadToEndAsyncInternal>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at MediaBrowser.Server.Implementations.HttpServer.HttpResultFactory.<GetStaticResult>d__7.MoveNext() Errors Edited December 8, 2014 by saitoh183 Link to comment Share on other sites More sharing options...
xnappo 1593 Posted December 8, 2014 Share Posted December 8, 2014 i have had this issue for months too - and it is annoying. Link to comment Share on other sites More sharing options...
ebr 14905 Posted December 8, 2014 Share Posted December 8, 2014 Okay, so if you go to the configuration page where you turn debug logging on and off, is the checkbox in the proper state (meaning it is unchecked if you meant for it to be off) even though debug lines are being written? Link to comment Share on other sites More sharing options...
xnappo 1593 Posted December 8, 2014 Share Posted December 8, 2014 (edited) Yes it is correct (unchecked). And when you start the server (normally, not from a Windows service) the log window pops up. Edited December 8, 2014 by xnappo Link to comment Share on other sites More sharing options...
ebr 14905 Posted December 8, 2014 Share Posted December 8, 2014 Log window? That's gone from the current server... Link to comment Share on other sites More sharing options...
xnappo 1593 Posted December 8, 2014 Share Posted December 8, 2014 Okay, last few restarts I have not been watching the machine it is running on. Still though - the log is on. xnappo Link to comment Share on other sites More sharing options...
saitoh183 137 Posted December 8, 2014 Share Posted December 8, 2014 Okay, so if you go to the configuration page where you turn debug logging on and off, is the checkbox in the proper state (meaning it is unchecked if you meant for it to be off) even though debug lines are being written? correct and as stated it seems to be happening when a restart is done other than the built-in midnight restart Link to comment Share on other sites More sharing options...
ebr 14905 Posted December 8, 2014 Share Posted December 8, 2014 By "built-in midnight restart" do you just mean the new log file that is created? Or is your machine actually re-starting? Link to comment Share on other sites More sharing options...
saitoh183 137 Posted December 8, 2014 Share Posted December 8, 2014 By "built-in midnight restart" do you just mean the new log file that is created? Or is your machine actually re-starting? new log file created Link to comment Share on other sites More sharing options...
ebr 14905 Posted December 8, 2014 Share Posted December 8, 2014 Okay, so to "fix" this - at least until the server restarts again, you guys just go to that config page and save it again with the checkbox unchecked? Link to comment Share on other sites More sharing options...
xnappo 1593 Posted December 8, 2014 Share Posted December 8, 2014 I haven't bothered to try to get it to turn off, just living with the huge log files. Can't test right now. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now