Solved Huge Logfiles

[Boddelneck]

Hey,

TL;DR had 95GB logfiles in the TS3Client /log directory because of newsticker

Story:
Tuesday my TS3Server kept on crashing - when I wanted to restart it i just got an I/O Error from the server.
Didn't want to troubleshoot so I just installed a backup.
Today it happened again. I was furious and blamed my Hoster - so I thought i'd just backup Sinusbot and my TS3Server and just reinstall my server.
Booted my Fallback system...
When I downloaded the Sinusbot I noticed that one log file kept on downloading - about 9GB into the transfer.

One of my logfiles was 93GB big.

Some files were 15 GB, 14GB aswell - all of them in December with the then current patchlevel.

Important Data:

Started with Sinusbot 0.9.8
Updated through every patch to the "lastest" version: 0.9.9-8f70ff3

The Problem:

The Problem lies in the logs...

2016-01-30 01:53:08.301069|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.301585|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.302127|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.302583|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.303120|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.303591|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.304155|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.304613|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.305252|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.305727|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.306385|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.306941|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.307403|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.307947|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.308400|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.308978|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.309426|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.309959|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-01-30 01:53:08.310530|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
^C
root@h2448673:/opt/ts3soundboard/data/ts3/84d08941-0d15-42cc-8aab-826fb7dce81d/94f35d96-178a-4c0c-8da1-008e88ac76f6/logs#

The Logfiles in /{botdir}/data/ts3/{botid}/{instanceid}/logs seem to be spamming!
This was captured with a "tail -f <logfile>" within the directory and while this seems little - textfiles can grow A LOT. I mean look at the polling rate!

Is there any way to turn this off?

My Config file:

ListenPort = 8087
ListenHost = "0.0.0.0"
TS3Path = "/opt/ts3soundboard/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64"
YoutubeDLPath = "/usr/local/bin/youtube-dl"
EnableAloneMode = true

If anybody has this problem: Delete your logs in the described folders.
And - until official response - maybe setup a cronjob to delete your files

Greetings
Wippinho

 

[CrAazZyMaN21]

I have this Problem too ^^

 

[Crank]

The Newsticker Check will fixed in the next Version, says @flyth

 

[Boddelneck]

Sorry for necro - just updated and this is fixed in 0.9.10!

Thank you!

 

[flyth]

Thanks for the confirmation!

 

[Boddelneck]

Just restarted my bot and it started again on Version 0.9.10-e1fdee3

I am certain it was gone when I've checked it last month, but now my new logfile of today keeps spamming it up again.

2016-03-12 14:01:02.610683|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.611130|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.611789|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.612227|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.707919|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.709650|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.711914|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.718457|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.718980|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017
2016-03-12 14:01:02.785803|INFO    |Newsticker    |   |Newsticker next check: So. Jan. 1 00:00:01 2017

Greetings