starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1223] log files eat my HDD!!! #952

New issue

Closed

opened 2026-02-27 02:54:30 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 02:54:30 +03:00

Owner

Originally created by @hitmany on GitHub (Jan 3, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1223

Its under /log/script
Every day file bigger and bigger

Originally created by @hitmany on GitHub (Jan 3, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1223 ![image](https://cloud.githubusercontent.com/assets/8200058/21604917/ea6484e8-d1b6-11e6-876c-e2b4196f31e2.png) Its under /log/script Every day file bigger and bigger

kerem closed this issue

2026-02-27 02:54:30 +03:00

kerem commented

2026-02-27 02:54:30 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 3, 2017):

At first i was gonna say:
"Your probably got addons writing a whole bunch of crap to your logs.
You can lower the logdays variable into csgoserver script to cleanup logs more often or try to find a way so that your addons don't write that much crap into the console."

But in your case, it's not console logs, but script logs.
I suspect those logs are filled up with an abusive badly set cronjob action. So watch your cronjobs carefully.
And most of all, see what's filling up those LGSM logs.
Since those files are huge, try to run the following command on any of them:
tail -c 10000 -f YOUR-LOG.log

@UltimateByte commented on GitHub (Jan 3, 2017): At first i was gonna say: "Your probably got addons writing a whole bunch of crap to your logs. You can lower the logdays variable into csgoserver script to cleanup logs more often or try to find a way so that your addons don't write that much crap into the console." But in your case, it's not console logs, but script logs. I suspect those logs are filled up with an abusive badly set cronjob action. So watch your cronjobs carefully. And most of all, see what's filling up those LGSM logs. Since those files are huge, try to run the following command on any of them: `tail -c 10000 -f YOUR-LOG.log`

kerem commented

2026-02-27 02:54:30 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 3, 2017):

Ultimately, github is for development, so we'll come back here only if you find a bug into LGSM.
https://github.com/GameServerManagers/LinuxGSM/wiki/Support

@UltimateByte commented on GitHub (Jan 3, 2017): Ultimately, github is for development, so we'll come back here only if you find a bug into LGSM. https://github.com/GameServerManagers/LinuxGSM/wiki/Support

kerem commented

2026-02-27 02:54:30 +03:00

Author

Owner

@hitmany commented on GitHub (Jan 3, 2017):

Okay, I have a lot of logs, its not problem
But files goes more and more every day
Look: 1 day 607 mb
second day 659 mb
3 day 693 mb
So looks like old day logs stored in new day. That is issue!

@hitmany commented on GitHub (Jan 3, 2017): Okay, I have a lot of logs, its not problem But files goes more and more every day Look: 1 day 607 mb second day 659 mb 3 day 693 mb So looks like old day logs stored in new day. That is issue!

kerem commented

2026-02-27 02:54:30 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jan 3, 2017):

can i see a sample of the log please

@dgibbs64 commented on GitHub (Jan 3, 2017): can i see a sample of the log please

kerem commented

2026-02-27 02:54:30 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 4, 2017):

Without log content, this issue is irrelevant.

@UltimateByte commented on GitHub (Jan 4, 2017): Without log content, this issue is irrelevant.

kerem commented

2026-02-27 02:54:30 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 12, 2017):

I bet on a poorly made cronjob. Closing since no feedback.

@UltimateByte commented on GitHub (Jan 12, 2017): I bet on a poorly made cronjob. Closing since no feedback.

kerem commented

2026-02-27 02:54:30 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.