Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Failed: Query was empty - Every map change #189

Closed
sneak-it opened this issue Oct 8, 2016 · 6 comments
Closed

Query Failed: Query was empty - Every map change #189

sneak-it opened this issue Oct 8, 2016 · 6 comments

Comments

@sneak-it
Copy link
Contributor

sneak-it commented Oct 8, 2016

Hi guys, I'm upgrading from a slightly older 1.5.5 version (prior to sbpp_ prefix plugin file names), and now that I have, every map change I get this in sourcebans.log:

[sbpp_main.smx] Query Failed: Query was empty

It doesn't appear to be causing any functionality issues from what I can tell (tested banning & reconnecting on banned account, functions properly).

Edit: Now it is consistently
L 10/08/2016 - 01:41:00: [sbpp_main.smx] Query Failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '�' at line 1

@sneak-it
Copy link
Contributor Author

sneak-it commented Oct 10, 2016

Update: Hope this helps find the issue, this completely crippled my server and all sql connections today:

L 10/10/2016 - 07:21:53: Info (map "surf_mesa") (file "errors_20161010.log")
L 10/10/2016 - 07:21:53: [SM] Exception reported: Invalid database Handle 0 (error: 4)
L 10/10/2016 - 07:21:53: [SM] Blaming: sbpp_comms.smx
L 10/10/2016 - 07:21:53: [SM] Call stack trace:
L 10/10/2016 - 07:21:53: [SM] [0] SQL_TQuery
L 10/10/2016 - 07:21:53: [SM] [1] Line 264, G:\csgo\plugin zips\sourcemod 1.8\scripting\sbpp_comms.sp::OnMapEnd
L 10/10/2016 - 07:21:53: Error log file session closed.
L 10/10/2016 - 15:33:45: SourceMod error session started
L 10/10/2016 - 15:33:45: Info (map "surf_surprise") (file "errors_20161010.log")
L 10/10/2016 - 15:33:45: [SM] Exception reported: Stack leak detected: sp:-691662848 should be 2790396!
L 10/10/2016 - 15:33:45: [SM] Exception reported: Invalid plugin address
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the heap
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the stack
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the stack
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the stack
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the stack
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the stack
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the heap
L 10/10/2016 - 15:33:45: [SM] Exception reported: Not enough space on the stack

etc, spammed a 185mb error log file with over 230,000 lines of not enough space on stack/heap. I'll be reverting to the older version for now until this is fixed.

@rogeraabbccdd
Copy link

rogeraabbccdd commented Oct 19, 2016

Hello guys, I also have this problem in my server, and here's my error log.

L 10/19/2016 - 10:09:08: SourceMod error session started
L 10/19/2016 - 10:09:08: Info (map "de_dust2") (file "errors_20161019.log")
L 10/19/2016 - 10:09:08: [SM] Exception reported: Invalid database Handle 0 (error: 4)
L 10/19/2016 - 10:09:08: [SM] Blaming: sbpp_comms.smx
L 10/19/2016 - 10:09:08: [SM] Call stack trace:
L 10/19/2016 - 10:09:08: [SM] [0] SQL_TQuery
L 10/19/2016 - 10:09:08: [SM] [1] Line 264, D:\CSGODS\CSGO\csgo\addons\sourcemod\scripting\sbpp_comms.sp::OnMapEnd
L 10/19/2016 - 10:09:09: Error log file session closed.

Sourcemod version 1.8.0.5492
Sourcebans++ version 1.5.5-dev (Download from sb++ website)

@coolmans
Copy link

me too
[SM] [1] Line 264, ***\addons\sourcemod\scripting\sbpp_comms.sp::OnMapEnd
L 11/25/2016 - 09:10:23: [sbpp_main.smx] Query Failed: Query was empty

L 11/25/2016 - 09:50:56: [sbpp_main.smx] Query Failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'd REGEXP '^STEAM_[0-9]:_SERVER$'), '0.0.0.0', 1)' at line 1

@Fastmancz
Copy link

sarabveer added a commit that referenced this issue Jan 12, 2017
@koteq
Copy link
Contributor

koteq commented Jan 19, 2017

Is the change to SQL_SetCharset actually needed?
There was another issue related to it, check #179.

@rogeraabbccdd
Copy link

This issue should be closed because it has been fixed.

@Groruk Groruk closed this as completed Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants