Jump to content

MBS - Log size option


saitoh183

Recommended Posts

saitoh183

Would it be possible to add a configurable option to limit the maximum size a log can be. This would be to insure that we can always open the log via the webclient (which currently isnt the case). When we need to debug or something causes the log to grow really quickly, The webclient will fail to open it because of its size and all you get when you try is

 

546e31e3868d8_logerror.jpg

 

Then your forced to navigate to the logs location and try to open it (because if its to big , its usuless). Yes i know MBS creates a new file at 12:00am and yes it also creates a new log when you restart it, but that is not a solution when your MBS is used by alot of people and you cant always just restart.

Edited by saitoh183
Link to comment
Share on other sites

I think we just need to do a better job of handling that situation in the dashboard.  Limiting the size of the log file would mean we'd have to check the size of it after each write (or very frequently) which doesn't seem worth it for this reason.

Link to comment
Share on other sites

saitoh183

I think we just need to do a better job of handling that situation in the dashboard.  Limiting the size of the log file would mean we'd have to check the size of it after each write (or very frequently) which doesn't seem worth it for this reason.

 

Adding a setting (with pre-determined sizes) on the dashboard...say under Advanced wouldnt be a option? Sonarr has a similar system (no settings it just creates a new log when it hits the limit they defined) and it works quite well.

Link to comment
Share on other sites

Ultimately, it will be up to Luke but the setting isn't the issue.  It would be the performance hit of having to check the size of the log file after every single write (or on some other frequent basis).  Maybe that's not a big deal but I don't like adding things like that where they could have a high impact just due to the frequency of the operation.

 

In any case, it seems handling the large log files in the dashboard would be solving the real problem.

Link to comment
Share on other sites

saitoh183

Ultimately, it will be up to Luke but the setting isn't the issue.  It would be the performance hit of having to check the size of the log file after every single write (or on some other frequent basis).  Maybe that's not a big deal but I don't like adding things like that where they could have a high impact just due to the frequency of the operation.

 

In any case, it seems handling the large log files in the dashboard would be solving the real problem.

 

Yes it would...well food for thought :) as long as the solution allows us to always be able to view logs via the webclient :)

Link to comment
Share on other sites

Redshirt

I suspect this request is directly related to logging changes I made to one of the schedules tasks in the trakt plugin. So I'll throw my hat into the ring too.

 

The log entries that are most likely to be made are set at the debug level. Turning off debug logging would remove those entries. Unless your troubleshooting an issue for the devs, there's no reason for the average user to have debug logging enabled. The other log entries that I added, are only shown if a local show couldn't be matched to a remote show. Those log entries are actually curable by the user simply by making sure the show is actually in your collection on the trakt website and by making sure that there is a valid imdb/tvdb/tmdb id for each show.

Link to comment
Share on other sites

saitoh183

I suspect this request is directly related to logging changes I made to one of the schedules tasks in the trakt plugin. So I'll throw my hat into the ring too.

 

The log entries that are most likely to be made are set at the debug level. Turning off debug logging would remove those entries. Unless your troubleshooting an issue for the devs, there's no reason for the average user to have debug logging enabled. The other log entries that I added, are only shown if a local show couldn't be matched to a remote show. Those log entries are actually curable by the user simply by making sure the show is actually in your collection on the trakt website and by making sure that there is a valid imdb/tvdb/tmdb id for each show.

 

 

Have a look here http://mediabrowser.tv/community/index.php?/topic/9255-titan-mediabrowser-skin-for-xbmc/page-25&do=findComment&comment=150225

 

When debug is disabled is it normal to still see lines that start with Debug?

 

This is a snippet from a fresh install of latest beta...no configurations done

 

there are lines like this

2014-11-20 15:14:15.0978 Debug - HttpServer: HTTP Response 200 to ::1. Response time: 23.0023 ms.
	Url: http://localhost:8096/mediabrowser/System/Logs
2014-11-20 15:14:15.9289 Debug - HttpServer: HTTP GET http://localhost:8096/mediabrowser/System/Logs/Log?name=server-63552093197.txt
	Ip: [::1]:51868. Headers: Connection=keep-alive,Accept=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8,Accept-Encoding=gzip,deflate,sdch,Accept-Language=en-US,en;q=0.8,fr-CA;q=0.6,fr;q=0.4,Host=localhost:8096,User-Agent=Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.122 Safari/537.36
Edited by saitoh183
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...