[GH-ISSUE #4081] [BUG] Team Fortress 2 fails to start after automated update #2611

New issue

Closed

opened 2026-02-27 03:04:06 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 03:04:06 +03:00

Owner

Originally created by @kintarowonders on GitHub (Jan 14, 2023).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4081

User Story

My Team Fortress 2 server now segfaults on startup, and has not been working for an unknown amount of time. The server updates itself at 4am every morning and at some point this update has stopped working on my system.

Basic info

Distro: [Debian bullseye 11.6]
Game: [Team Fortress 2]
Command: [Start]
LinuxGSM version: [v22.2.1]

Further Information

I need help getting more information because running with debugging, and adding the '-debug' parameter to _default.cfg is not producing any kind of debug log or more information in the logs directory, or anywhere else that I can find.

This is how the server is being launched...

./srcds_run -game tf -strictportbind -ip 0.0.0.0 -port 27016 +clientport 27005 +tv_port 27020 +map ctf_2fort +sv_setsteamaccount +servercfgfile tf2server.cfg -maxplayers 32 -debug

Below is how it fails...

Network: IP 0.0.0.0, mode MP, dedicated Yes, ports 27016 SV / 27005 CL
Initializing Steam libraries for secure Internet server
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 10 milliseconds to initialize
Setting breakpad minidump AppID = 440
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
[S_API FAIL] Tried to access Steam interface SteamUtils010 before SteamAPI_Init succeeded.
Setting breakpad minidump AppID = 232250
No account token specified; logging into anonymous game server account.  (Use sv_setsteamaccount to login to a persistent account.)
Connectivity test: result=Connected, in progress=0
Segmentation fault (core dumped)
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem
Sat Jan 14 19:50:09 AEDT 2023: Server restart in 10 seconds
Sat Jan 14 19:50:10 AEDT 2023: Server Quit

To Reproduce

Steps to reproduce the behaviour:

Just start the server and you get the segmentation fault error.

Expected behaviour

Server actually starts.

Originally created by @kintarowonders on GitHub (Jan 14, 2023). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4081 ## User Story My Team Fortress 2 server now segfaults on startup, and has not been working for an unknown amount of time. The server updates itself at 4am every morning and at some point this update has stopped working on my system. ## Basic info - **Distro:** [Debian bullseye 11.6] - **Game:** [Team Fortress 2] - **Command:** [Start] - **LinuxGSM version:** [v22.2.1] ## Further Information I need help getting more information because running with debugging, and adding the '-debug' parameter to _default.cfg is not producing any kind of debug log or more information in the logs directory, or anywhere else that I can find. This is how the server is being launched... `./srcds_run -game tf -strictportbind -ip 0.0.0.0 -port 27016 +clientport 27005 +tv_port 27020 +map ctf_2fort +sv_setsteamaccount +servercfgfile tf2server.cfg -maxplayers 32 -debug` Below is how it fails... ``` Network: IP 0.0.0.0, mode MP, dedicated Yes, ports 27016 SV / 27005 CL Initializing Steam libraries for secure Internet server [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK. CAppInfoCacheReadFromDiskThread took 10 milliseconds to initialize Setting breakpad minidump AppID = 440 Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit [S_API FAIL] Tried to access Steam interface SteamUtils010 before SteamAPI_Init succeeded. Setting breakpad minidump AppID = 232250 No account token specified; logging into anonymous game server account. (Use sv_setsteamaccount to login to a persistent account.) Connectivity test: result=Connected, in progress=0 Segmentation fault (core dumped) Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem Sat Jan 14 19:50:09 AEDT 2023: Server restart in 10 seconds Sat Jan 14 19:50:10 AEDT 2023: Server Quit ``` ## To Reproduce Steps to reproduce the behaviour: Just start the server and you get the segmentation fault error. ## Expected behaviour Server actually starts.

kerem

2026-02-27 03:04:06 +03:00

closed this issue
added the
type: bug

distro: Debian

command: stop

command: update

command: start

command: debug

command: restart
labels

kerem commented

2026-02-27 03:04:07 +03:00

Author

Owner

@kintarowonders commented on GitHub (Jan 14, 2023):

Nevermind!

I just had to do mods-update!

@kintarowonders commented on GitHub (Jan 14, 2023): Nevermind! I just had to do mods-update!

kerem commented

2026-02-27 03:04:07 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 15, 2024):

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

@github-actions[bot] commented on GitHub (Jan 15, 2024): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:55:35 +03:00

[PR #2611] [MERGED] feat(monitor): migrate monitor settings to _default.cfg #3724