[Dravu]

For the past two days, two of our servers have been issues with the Sourcemod logs. At seemingly random times, Sourcemod just up and stops logging both to the regular log file as well as the error log file. The only way to fix the problem is to restart the server. Nothing else is accessing or locking the files and the servers' main logs (/orangebox/tf/logs/) aren't affected. Is there any way to debug the problem or restart the logging? Reloading Sourcemod obviously isn't an option.

[KyleS]

I have this as well. I should also note I haven't tried to solve it, either.

[Dravu]

There's nothing in common where the log files stop and nothing in the main logs that would indicate any issues. At the times Sourcemod stopped logging, nobody was logged into our server (physical, not gameserver) through any method (FTP, RDP, etc) either. I don't know what else to investigate, but at least I'm not alone.

[Dravu]

I recoded one of my plugins to write to its own log file instead of the main one and even though it'd create the file for it, it refused to write to it.

[Dravu]

I tried changing the RCON pass just to be sure, but nothing. I also upgraded the servers to Sourcemod v1.4.1 and ran them with administrator privileges and still nothing. The past two days, both servers stopped logging after after a map change (which map change is random), but it might've just been a coincidence.

Anybody have any ideas I can try?

[Dravu]

This appears to have been because of a plugin being too SQL intensive oddly enough. I'm going to work on rewriting parts of it to keep Sourcemod content. Not sure why the MySQL interface likes to keep giving me trouble.

[Fyren]

Can you write a simple plugin that intentionally causes this and post it in a bug report?

[Dravu]

Originally Posted by Fyren Can you write a simple plugin that intentionally causes this and post it in a bug report?

I can attempt to. I've also had problems in the past where plugins losing connection to the SQL server multiple times would eventually go unstable and stop working entirely. Reloading them would crash the server. I'll see if I can manually cause that as well.

[Dravu]

To update this, I found out that it actually wasn't the SQL interface. My plugin had a memory leak that I didn't notice. Whenever I'd execute a query, I'd shove it in a DataPack so that whenever a SQL query would produce an error, I could put the exact query in the error logs. Unfortunately, I only closed the handle whenever an error actually happened, so after a couple thousand queries, Sourcemod would unload the plugin. Little did Sourcemod know that when you unload my plugin, it sends a few queries to the SQL server. Apparently that little tid bit made Sourcemod shit itself and stop logging altogether.