starred/LinuxGSM

Fork 0

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

[GH-ISSUE #190] TF2 Server took too long to process Error #152

New issue

Closed

opened 2026-02-27 01:59:49 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 01:59:49 +03:00

Owner

Originally created by @medic917 on GitHub (Oct 4, 2014).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/190

This is the error I get in my server logs:
WatchDog! Server took too long to process (probably infinite loop).
Host_Error: WatchdogHandler called - server exiting.

L 10/03/2014 - 17:22:57: Engine error: Host_Error: WatchdogHandler called - server exiting.

Segmentation fault

This happened twice already, so it seems like it is a routine thing.
I did edit the tf2server script file to take out the lock file, and I have monitor running in my crontab.
Perhaps this was the reason?

I'm running the server without the ./tf2server monitor in the crontab and will let you guys know if I still get the crash due to the same error.

For now, any ideas?

Originally created by @medic917 on GitHub (Oct 4, 2014). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/190 This is the error I get in my server logs: WatchDog! Server took too long to process (probably infinite loop). Host_Error: WatchdogHandler called - server exiting. L 10/03/2014 - 17:22:57: Engine error: Host_Error: WatchdogHandler called - server exiting. Segmentation fault This happened twice already, so it seems like it is a routine thing. I did edit the tf2server script file to take out the lock file, and I have monitor running in my crontab. Perhaps this was the reason? I'm running the server without the ./tf2server monitor in the crontab and will let you guys know if I still get the crash due to the same error. For now, any ideas?

kerem closed this issue

2026-02-27 01:59:49 +03:00

kerem commented

2026-02-27 01:59:49 +03:00

Author

Owner

@Scarsz commented on GitHub (Oct 4, 2014):

For modified versions we can't really help you as you've made changes that we don't release, the server works fresh from the repository which is what we strive to get.

As for then seg fault, try verifying the server files manually through SteamCMD and starting the server from the actual command instead of through the script.

@Scarsz commented on GitHub (Oct 4, 2014): For modified versions we can't really help you as you've made changes that we don't release, the server works fresh from the repository which is what we strive to get. As for then seg fault, try verifying the server files manually through SteamCMD and starting the server from the actual command instead of through the script.

kerem commented

2026-02-27 01:59:49 +03:00

Author

Owner

@medic917 commented on GitHub (Oct 4, 2014):

tnx scarsz.

I was just curious if you guys could see a connection between me taking out the lockfile and this error.

I also contacted my server host and they said they had some issues on their hand that "could" have been the cause. But it happened twice already on a regular basis so I will keep looking.

@medic917 commented on GitHub (Oct 4, 2014): tnx scarsz. I was just curious if you guys could see a connection between me taking out the lockfile and this error. I also contacted my server host and they said they had some issues on their hand that "could" have been the cause. But it happened twice already on a regular basis so I will keep looking.

kerem commented

2026-02-27 01:59:50 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Oct 4, 2014):

I can confirm that taking the lock file out will have no bearing on fixing your error. This is an issue with the server itself and not the script. Monitor will re-enable the server on crash and log /email you the details. I recommend having monitor in if you want your server to stay online. You will also be notified about crashes by email.

Seg faults are normally caused by a dependency issue of some sort or a broken install of your distro.

@dgibbs64 commented on GitHub (Oct 4, 2014): I can confirm that taking the lock file out will have no bearing on fixing your error. This is an issue with the server itself and not the script. Monitor will re-enable the server on crash and log /email you the details. I recommend having monitor in if you want your server to stay online. You will also be notified about crashes by email. Seg faults are normally caused by a dependency issue of some sort or a broken install of your distro.

kerem commented

2026-02-27 01:59:50 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Oct 6, 2014):

Closing issue as no more response. Please reopen if required

@dgibbs64 commented on GitHub (Oct 6, 2014): Closing issue as no more response. Please reopen if required

kerem commented

2026-02-27 01:59:50 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 20, 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 20, 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.