[DarkDeviL]

Originally Posted by Sarabveer Thats the dev version, but ok.

He asked for the change log, and he got it... He didn't say for which..

Also, in his deleted post, he said:

why arent we seeing any updated on this project. Is this dead too like original?

The GitHub history should show him that it is not completely dead..

[MyWarthog]

"Oh, this volunteer project hasn't been officially updated in 2 months. It must be dead."

Riiiiiight. I guess by that logic, then SourceMod must be dead too, right?

[Phaiz]

Originally Posted by MyWarthog "Oh, this volunteer project hasn't been officially updated in 2 months. It must be dead." Riiiiiight. I guess by that logic, then SourceMod must be dead too, right?

[Sarabveer]

Originally Posted by Phaiz

Lol

[utaker]

Originally Posted by Sarabveer U want us to release a buggy version every month, or a stable one every few months. The project is not dead, ever since the last week, I've been really busy. Thats why I'm looking for coders. I already have 3 guys forking my repo and making their own changes. I'm just waiting for the Pull Requests. Thats the dev version, but ok.

ok i'll shift to this one from sourcebans

[scso1502]

Any idea why these error messages are showing up in the error logs of all my TF2 servers? Were there any changes to SourceSleuth recently that corrected these? I'm using the SourceSleuth version I downloaded with the forked 1.5.2.F Version of SourceBans here from this thread:

L 08/13/2015 - 02:18:25: [SM] Native "SQL_TQuery" reported: Invalid database Handle 0 (error: 4)
L 08/13/2015 - 02:18:25: [SM] Displaying call stack trace for plugin "SourceSleuth.smx":
L 08/13/2015 - 02:18:25: [SM] [0] Line 168, SourceSleuth.sp::OnClientPostAdminCheck()

Partial plugins list showing versions running:

(48 "SourceBans" (1.5.2F) by SourceBans Development Team, Sarabveer(VEER™)
(50 "SourceSleuth" (SB-1.5.2F) by ecca, Sarabveer(VEER™)

Thanks in advance.

[King Cnut]

I'm still getting this error:

L 08/10/2015 - 15:22:09: SourceMod error session started
L 08/10/2015 - 15:22:21: [SDKTOOLS] Could not locate FireOutput - Disabling detour
L 08/10/2015 - 15:22:22: [SM] Failed to load plugin "player_analytics.smx": [2003]: Can't connect to MySQL server on '104.XXX.XXX.XXX' (10061).
L 08/10/2015 - 15:22:22: [SDKTOOLS] Failed to find PlayerRunCmd offset - OnPlayerRunCmd forward disabled.
L 08/10/2015 - 15:22:39: [SM] Plugin encountered error 25: Call was aborted
L 08/10/2015 - 15:22:39: [SM] Native "SetFailState" reported: Failed to connect to SourceBans DB, [2003]: Can't connect to MySQL server on '104.XXX.XXX.XXX' (10061)
L 08/10/2015 - 15:22:39: [SM] Displaying call stack trace for plugin "sbchecker.smx":
L 08/10/2015 - 15:22:39: [SM]   [0]  Line 69, sbchecker.sp::OnDatabaseConnected()
L 08/10/2015 - 15:22:39: [sourcecomms.smx] Connecting to database failed: [2003]: Can't connect to MySQL server on '104.XXX.XXX.XXX' (10061)
L 08/10/2015 - 15:22:39: [SourceSleuth.smx] SourceSleuth: Database connection error: [2003]: Can't connect to MySQL server on '104.XXX.XXX.XXX' (10061)

I've granted permissions for my gameserver to connect to my webserver like I've done at least 2 trillion times before for other applications in the past but it still can't connect due to the error. The webserver ip isn't banned as my 'listip' shows no records. Please help.

[scso1502]

@ King Cnut:

Error (10061) indicates that the network connection to the MySQL server is refused. Here's some things I would check it I was having this trouble. This would indicate a permissions issue that is not allowing the gameserver to connect to the database. I only post the below info because even the most experience people sometime miss the obvious because we're human and simply over look things some times. Lord knows I have, not that I'm anything special.

1. If this is an existing install and it worked before, I'd ask myself "What did I change recently that could have created this problem?" Some of those things could be:

- Did you recently update SourceMod and overwrite or change the Sourcebans section of \addons\sourcemod\config\databases.cfg?
- Have you recently enabled new firewall settings on the game server that were not enabled before?
- Have you changed your game server's IP address? Does it match what you have your Remote MySQL settings configured on the Webserver?
- Have you recently updated the MySQL database username and/or password on the webserver and do they match what you have in your databases.cfg on the game server?

2. If this is a new install have you double-confirmed the following:

- Confirmed the MySQL database server address, username & password match databases.cfg on the game server
- Confirmed the MySQL port is correct in the databases.cfg
- Confirmed the Remote MySQL settings on the webserver allow the game server's IP address to connect to the MySQL database?
- Have you given all the permissions necessary to the MySQL user to allow to access the database?

I can't see any other reason for the database server and the game server to be unable to communicate unless there's a webserver problem the hosting company needs to fix.

All the best on getting back up and running. Let us know what you find. It will help others I'm sure.

[Creampuffyness]

Originally Posted by scso1502 Any idea why these error messages are showing up in the error logs of all my TF2 servers? Were there any changes to SourceSleuth recently that corrected these? I'm using the SourceSleuth version I downloaded with the forked 1.5.2.F Version of SourceBans here from this thread: L 08/13/2015 - 02:18:25: [SM] Native "SQL_TQuery" reported: Invalid database Handle 0 (error: 4) L 08/13/2015 - 02:18:25: [SM] Displaying call stack trace for plugin "SourceSleuth.smx": L 08/13/2015 - 02:18:25: [SM] [0] Line 168, SourceSleuth.sp::OnClientPostAdminCheck() Partial plugins list showing versions running: (48 "SourceBans" (1.5.2F) by SourceBans Development Team, Sarabveer(VEER™) (50 "SourceSleuth" (SB-1.5.2F) by ecca, Sarabveer(VEER™) Thanks in advance.

I have this too. I actually removed Sourcesleuth because I am not sure if it was working or not. I recently (like 3 days ago) readded it, and on day 1 had no errors. Since then I still get SourceSleuth errors. I cannot verify if it is working on not.

[Creampuffyness]

As a follow up to my last post Sourcesleuth is still working from this package. While I still see errors, it is banning alt accounts as it should.