Huge errorlog.txt file!!

[notesguru99]

Hi All,
Our errorlog.txt file blew up to 150GB in size. Not sure yet if we had hit the verbose logging option or whether it is spewing out a load of errors? Everything seems fine apart from this massive text file? Any ideas?

Thanks
Stuart

[Esben_D]

2GB in a week does seem like a lot. You could open the errorlog to check what kind of errors are being given back. It could be that something in your configuration is causing errors to be spammed in the errorlog.

[notesguru99]

Thanks for the response. It may be because we have been using LS for a long time. We have no additional debug options set and my log file has grown to over 2GB in a week so I will keep a closer eye on it!

Thanks

[Esben_D]

If you are not having any issues, then I would recommend stopping your Lansweeper service, deleting the errorlog.txt, and restarting your service. A new errorlog will be generated when the service starts.

The cause of your large errorlog might be because you have debug options still enabled, or just because you have been using Lansweeper for a long time. You can revert any additional logging options by opening Program Files (x86)\Lansweeper\Tools\ConfigEditor.exe and use the 'Reset to default' button. After resetting use the 'Save configs and restart service' button.