[jpwanabe]

Does anyone else have any problems with source sleuth not working correctly? We are on Windows Server 2008 and I've had the ban multiple accounts that are coming from the same IP address that is permanently banned. Can someone who has a working set up post their config?

[Sw33T3R]

Hello
I have a big problem with SourceBans

[Server Specs]
Apache/2.4.12 (Ubuntu)
Database client version: libmysql - 5.6.27
PHP extension: mysqli Documentation
PHP version: 5.6.11-1ubuntu3.1
OS Ubuntu 15.10

I dont know why i have AJAX error when i want ban,kick someone from web panel
BTW SourceBans web rcon console doesnt work (Can't connect to the server)

I tried SourceBans 1.5.3 and 1.5.4 same problem

PHP Code:

Error: the XML response that was returned from the server is invalid. Received: 
Warning: stream_set_timeout() expects parameter 1 to be resource, boolean given in /var/www/html/sourcebans/includes/CServerRcon.php on line 50

Warning: fwrite() expects parameter 1 to be resource, boolean given in /var/www/html/sourcebans/includes/CServerRcon.php on line 71

Warning: fwrite() expects parameter 1 to be resource, boolean given in /var/www/html/sourcebans/includes/CServerRcon.php on line 71
$('dialog-control').setStyle('display', 'block'); 


PS (Before switching to new ubuntu (from 14.10 lts to 15.10) everything was okay, I dont remember previous php version)

[Blah91]

SourceBans++ is a modified version of SourceBans 1.4.11 by GameConnect. It includes many community made customizations and modifications to make the SourceBans experience better.

What Sourcebans++ actually modifies / changes? In addition to that it does not work (does not work support mariadb, gg).

[mazdarx8]

Hi,

I have following problem that when I mute a player, and a mapchange he is unmuted again. I use the !mute command.
The same, if he joins to another server.

I dont know when the problem was happen, some times ago it worked without problems.

[DarkDeviL]

Originally Posted by Blah91 What Sourcebans++ actually modifies / changes? In addition to that it does not work (does not work support mariadb, gg).

Well, if you are so retarded to say something doesn't work just because MariaDB doesn't work perfectly together with it, then I really feel sorry for you.

No offense, but as I read your post, you said SourceBans++ wasn't working? MariaDB is the problem, not SourceBans++:

MariaDB claims to be a drop-in replacement for MySQL. If it really was a drop-in replacement, how would you explain that MariaDB breaks functionality of other things, which works perfectly with MySQL? That's not what I would call a "drop-in" replacement.

Anyway, SourceBans++ is totally open sourced, ... so if you want it MariaDB to work together with SourceBans++, feel free to make it the required adjustments and submit a pull request.

If I misunderstood you, and that you would really like to help constructively rather than running around with that selfish attitude you were showing above, then offer your assistance for the future development.

[Sarabveer]

Originally Posted by Blah91 What Sourcebans++ actually modifies / changes? In addition to that it does not work (does not work support mariadb, gg).

I never said it supported MariaDB.

* Webserver o PHP 5.4 or higher * ini setting: memory_limit greater than or equal to 64M o MySQL 5.0 or higher * Source Dedicated Server o MetaMod: Source o SourceMod: Greater Than or Equal

[asherkin]

Originally Posted by arne1288 Anyway, SourceBans++ is totally open sourced, ... so if you want it MariaDB to work together with SourceBans++, feel free to make it the required adjustments and submit a pull request.

Might want to check your facts first - the author has rejected without comment previous contributions to fix the incompatibility.

Originally Posted by arne1288 MariaDB claims to be a drop-in replacement for MySQL. If it really was a drop-in replacement, how would you explain that MariaDB breaks functionality of other things, which works perfectly with MySQL? That's not what I would call a "drop-in" replacement.

SourceBans++ would work fine with MariaDB if SourceBans++ didn't have a broken hard-coded check for specific MySQL versions (which is only there to work around other issues SourceBans++ has with the MySQL query optimiser due to highly inefficient SQL queries in SourceBans++).

SourceBans++ claims to support MySQL 5.0+, which includes all versions of MariaDB as a fork of MySQL 5.6 without any compatibility-breaking changes, so that statement is clearly incorrect.

[DarkDeviL]

Originally Posted by asherkin Might want to check your facts first - the author has rejected without comment previous contributions to fix the incompatibility.

I have seen that the author refused to work on changes related to MariaDB compatibility, not that the author refused to take any contributions from third parties that would make peace between them.

Refusing to work on and refusing to accept contributions are two different things to me, I have only seen the first one.

Originally Posted by asherkin SourceBans++ would work fine with MariaDB if SourceBans++ didn't have a broken hard-coded check for specific MySQL versions (which is only there to work around other issues SourceBans++ has with the MySQL query optimiser due to highly inefficient SQL queries in SourceBans++). SourceBans++ claims to support MySQL 5.0+, which includes all versions of MariaDB as a fork of MySQL 5.6 without any compatibility-breaking changes, so that statement is clearly incorrect.

I believe we might agree with most things, and SourceBans is indeed known to have a lot of inefficient SQL queries.

However, if you can send one command to MySQL, and that works fine, but you can't send it to some fork of the MySQL; I wouldn't ever call that a drop-in replacement.

If it was a drop-in replacement to me, it would either silently have discarded or eventually produced a warning with the hard-coded check.

[asherkin]

I'm on my phone so can't look it up again, but the closed PRs are in the repo for anyone to see.

That's it, you CAN send the same "command" - but SourceBans++ DOESN'T send it at all due to the buggy version check.

There is absolutely nothing that could be changed in MariaDB (other than pretending to be MySQL, and a specific version at that), the problem is squarely in SourceBans++ – if it just sent the query it would work fine – and the query in question is just working around other bugs in SourceBans++ and is required by BOTH MySQL and MariaDB 5.6+, but SourceBans++ doesn't consider 10 greater than 5 so doesn't work with current versions of MariaDB, it'll probably break MySQL on the next major version bump as well.

[Sarabveer]

https://github.com/Sarabveer/SourceB...d07bcad1ce7e93

Going back to sleep. Zzzzzzz........

EDIT:

Originally Posted by asherkin There is absolutely nothing that could be changed in MariaDB (other than pretending to be MySQL, and a specific version at that), the problem is squarely in SourceBans++ – if it just sent the query it would work fine – and the query in question is just working around other bugs in SourceBans++ and is required by BOTH MySQL and MariaDB 5.6+, but SourceBans++ doesn't consider 10 greater than 5 so doesn't work with current versions of MariaDB, it'll probably break MySQL on the next major version bump as well.

Asherkin, what are you taking about here?