Hey,
I bought an Unmanaged 2-core VDS from NFOservers not too long ago and I've set it up using Sourcebans, SMAC, and ckSurf. Every once in a while it seems that SRCDS will spam with MySQL errors and cause a stack overflow. I'm not sure what causes it because it happens every once in a while.
CS:GO Crashing
- Aeternal
- Compulsive poster
- Posts: 60
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Sun Nov 24, 2013 7:41 am
- Contact:
- ThatGuyNex
- This is my homepage
- Posts: 239
- Joined: Tue May 28, 2013 12:23 pm
Re: CS:GO Crashing
What are the errors exactly? Have you checked the SQL server logs for any errors from the same time?
Re: CS:GO Crashing
Here is a log from today just after the map changed:ThatGuyNex wrote:What are the errors exactly? Have you checked the SQL server logs for any errors from the same time?
Code: Select all
L 03/02/2016 - 19:53:50: Info (map "surf_forbidden_ways_ksf") (file "errors_20160302.log")
L 03/02/2016 - 19:53:50: [SM] Unable to load plugin "custom-chatcolors-toggle.smx": Could not find required plugin "ccc"
L 03/02/2016 - 19:53:50: [SM] Plugin encountered error 25: Call was aborted
L 03/02/2016 - 19:53:50: [SM] Native "SetFailState" reported: Failed to connect to SourceBans DB, Could not find database conf "sourcebans"
L 03/02/2016 - 19:53:50: [SM] Displaying call stack trace for plugin "sbchecker.smx":
L 03/02/2016 - 19:53:50: [SM] [0] Line 75, sbchecker.sp::OnDatabaseConnected()
L 03/02/2016 - 19:53:50: [SM] Plugin encountered error 25: Call was aborted
L 03/02/2016 - 19:53:50: [SM] Native "SetFailState" reported: Database failure: Could not find Database conf "sourcebans"
L 03/02/2016 - 19:53:50: [SM] Displaying call stack trace for plugin "sourcebans.smx":
L 03/02/2016 - 19:53:50: [SM] [0] Line 209, sourcebans.sp::OnPluginStart()
L 03/02/2016 - 19:53:50: [SM] Plugin encountered error 25: Call was aborted
L 03/02/2016 - 19:53:50: [SM] Native "SetFailState" reported: Database failure: could not find database conf sourcebans
L 03/02/2016 - 19:53:50: [SM] Displaying call stack trace for plugin "sourcecomms.smx":
L 03/02/2016 - 19:53:50: [SM] [0] Line 221, sourcecomms.sp::OnPluginStart()
L 03/02/2016 - 19:53:54: [SM] Native "SQL_TQuery" reported: Invalid database Handle 0 (error: 4)
L 03/02/2016 - 19:53:54: [SM] Displaying call stack trace for plugin "SourceSleuth.smx":
L 03/02/2016 - 19:53:54: [SM] [0] Line 166, SourceSleuth.sp::OnClientPostAdminCheck()
L 03/02/2016 - 19:53:55: [SM] Native "SQL_TQuery" reported: Invalid database Handle 0 (error: 4)
L 03/02/2016 - 19:53:55: [SM] Displaying call stack trace for plugin "SourceSleuth.smx":
L 03/02/2016 - 19:53:55: [SM] [0] Line 166, SourceSleuth.sp::OnClientPostAdminCheck()
L 03/02/2016 - 19:53:55: [SM] Native "SQL_TQuery" reported: Invalid database Handle 0 (error: 4)
L 03/02/2016 - 19:53:55: [SM] Displaying call stack trace for plugin "SourceSleuth.smx":
L 03/02/2016 - 19:53:55: [SM] [0] Line 166, SourceSleuth.sp::OnClientPostAdminCheck()
L 03/02/2016 - 19:53:55: [SM] Native "SQL_TQuery" reported: Invalid database Handle 0 (error: 4)
L 03/02/2016 - 19:53:55: [SM] Displaying call stack trace for plugin "SourceSleuth.smx":
L 03/02/2016 - 19:53:55: [SM] [0] Line 166, SourceSleuth.sp::OnClientPostAdminCheck()
L 03/02/2016 - 19:58:48: [SM] Native "SQL_TQuery" reported: Invalid database Handle 0 (error: 4)
L 03/02/2016 - 19:58:48: [SM] Displaying call stack trace for plugin "SourceSleuth.smx":
L 03/02/2016 - 19:58:48: [SM] [0] Line 166, SourceSleuth.sp::OnClientPostAdminCheck()
L 03/02/2016 - 20:06:51: Error log file session closed.
