Ulysses
Ulysses Stuff => General Chat & Help and Support => Topic started by: Storm on December 06, 2013, 09:20:47 AM
-
Oddest thing. My bans have all disappeared from the bans tab on my 7 TTT servers. My bans.txt and banned_user.cfg are intact but under the bans tab there is nothing. This has not occurred on my servers running other gmod gamemodes. Just on TTT. Have you heard of any issue with this and can you suggest something I might check to get it back? Thank you!
-
Check data/ulib/bans.txt
If the bans are still in there please tell us, and maybe we can fix this for you.
-
Yes bans.txt is intact.
-
How large is your bans file?
-
How large is your bans file?
You guys should maybe consider changing users/groups/bans into mysql lite. It would be much more reliable in my opinion.
-
You guys should maybe consider changing users/groups/bans into mysql lite. It would be much more reliable in my opinion.
It's the very next thing we're going to do, actually. We just need time to do it.
-
bans.txt is 367,445
-
bans.txt is 367,445
That might be your issue. That's quite a large file, it's around 350 megabytes. Must be hundred to thousands of bans, like you must of been banning people using ulx before xgui was here..
(http://puu.sh/5Fhax/d0d3082a85.png)
-
It is over 1600 bans. I have that many bans on each of 10 gmod servers because I ban some people across all servers. It is really a problem because at some point I am afraid something will break! Moreover, I have to enter each ban separately to each of 10 servers on HLSW. It is very time consuming. This is why I wish sourcebans would work properly on gmod.
-
That's 358.8 KB, chaos (first number was bytes). That's large but not huge. I'm really not sure what your problem is, Storm, sorry. We will be moving the bans system over to SQL in the near future though, hopefully that will resolve your issue.
-
Thanks at least the bans are still in the banned_user.cfg and they cant get on the servers.
-
That's 358.8 KB, chaos (first number was bytes). That's large but not huge. I'm really not sure what your problem is, Storm, sorry. We will be moving the bans system over to SQL in the near future though, hopefully that will resolve your issue.
Will you guys be making some other addon that will convert the ulib bans to mysql bans, or will all bans just be reset?
-
Not decided yet.
-
Reset?? You mean I may lose the bans?
-
Reset?? You mean I may lose the bans?
The current system uses file.write(or something like that) which creates a basic text file in DATA folder called bans.txt. In that file contains all the bans and stuff, though they have been discussing switching to MySQL lite so that bans can be read faster and easier by the server, which could result in fixing the issues with delay and lag.
(I wrote this one my phone, so there may be small mistakes and such.)
-
I would never just ignore existing bans, they will be migrated to the new system.
-
It sounds like it would be great to switch but would I lose the bans in my banned_user.cfg or could I transfer them? Or is it just too early to tell?
-
*sigh* No Storm.
Though it's possible I'm incorrect in saying this, I'm 99% sure I'm not.
We will never over take/stop using Source's normal ban system, which, sometimes unfortunately, is a straight text file called banned_user.cfg
The main reasons we use an additional file now, and it's the bans.txt one are;
1) "Temporary" across multi-session - Source bans don't keep "temporary bans" across server sessions. If you temporary ban someone using Source, no ULib loaded, for 5 days and your server restarts for any reason before that 5 days is up, that ban is gone. With our file, it will stay until expired.
2) Reason tracking
3) Who tracking (both name banned, and who did it)
4) Others I now forget.
If/when we start storing OUR ban information in a new format, be it SQLite or whatever, as Megiddo stated, he plans on converting whatever is in OUR bans.txt file.
The Source bans file would still be loaded as normal, and perhaps, given our industrious nature, also as an addition be stored in a separate sqlite db file.
-
The Source bans file would still be loaded as normal, and perhaps, given our industrious nature, also as an addition be stored in a separate sqlite db file.
Did not know you could create your own sv.db file, thought everyone just had to share and make a new table in the thing... Mmmmh :/
-
You do have to share, unfortunately... :(
-
Indeed Chaos.
I only meant as a back up to the original Source text file.