ULX Banid Problem

[GTKarnage]

Alright, our server has been acting up lately with ULX. 

When using "ulx ban" or "!ban", everything works out fine and dandy.  The user gets the ban message and is instantly kicked and banned from the server for the specified amount of time.

However, when using "ulx banid" or "!banid", the message shows up in chat and the console saying that the steamid was banned for the set amount of time and for whatever reason, yet the user is neither kicked nor banned from the server.  I can kick them from the server and they can instantly rejoin.

Example:
ulx banid "STEAM_0:0:XXXXXXX" 1 "Test"
(ADMIN) Soandso banned id STEAM_0:0:XXXXXXX for 1 minute(s) (Test)  - (At this point, I am banning myself and am still in the server after the "ban.")

Anyone else having this problem or know how to fix this?

[Megiddo]

Any errors in console? I'll double check that this is still working his afternoon, too.

[GTKarnage]

The only errors I get are when connecting to our server, not using ULX.

These are:
"ERROR! Module 'zlib_b64' not found!"

and

"RunConsoleCommand blocked - sent before player spawned (ZLib_Installed)"

[Stickly Man!]

I just tested this on my ded server, and it seems to be working fine

Code: [Select]

] ulx banid STEAM_0:1:5###### 1 "Foul language"
Player __fastcall left the game (Kicked and banned)
You banned steamid STEAM_0:1:5###### for 1 minute(s) (Foul language)
Player __fastcall has joined the game
Player __fastcall left the game (STEAM UserID STEAM_0:1:5###### is banned)


[GTKarnage]

The problem still exists.

[JamminR]

GTKarnage, is this ULX release or SVN?
Older release versions and some older SVN revisions had an issue where our bans.txt file that is used to store temporary bans between server sessions could/would get corrupted due to slashes... "////". What is the size of your server data/ULib/bans.txt file? If over 2mb in size, it very well may be due to the corruption issue.
Open it with a text editor that can handle large files and see if there is a section with several (8-20 or more) slashes.
If so, you'll need to delete the file and let ULX recreate it.
Though you will lose some temporary bans, your permanent bans will be fine. (We use bans.txt because Source doesn't hold temporary bans from server session to server session)