Ban client of same identity as issuing ban = server crash

[squirrelof09]

Okay, so we were just fooling around on the server and had a client connect twice to the server with same identity. This person banned their other connection for exactly one second. The server crashes. This is bad bug.

2012-07-12 10:29:53.423900|CRITICAL|VirtualServer | 1| Assertion "client != 0" failed at server\serverlib\virtualserver.cpp:6581;

[dante696]

Edit, this will be found and fixed asap!

What server and client version is running?

How to?
I connect with a second client and 2 same identitys
Now client 1 right-clicks one of them and adds the ban and the server does crash?

Tab1:
<13:35:11> "Ultimate1" connected to channel "Default Channel"
<13:35:14> You were banned for 1 day from the server by ""Ӽ""
<13:35:14> Disconnected from server

Tab2:
<13:35:14> "Ultimate" was banned for 1 day from the server by ""Ӽ""
<13:35:14> You were banned for 1 day from the server by ""Ӽ""
<13:35:14> Disconnected from server

Do i understand right, the second identity has to connect in the same moment, when tab1 was banned?

[eckart]

confirmed at client 3.0.8 (WinXP) and server 3.0.6.1 (linux 64bit)

(2012-07-12 14:53:08.082497|CRITICAL|VirtualServer | 1| Assertion "client != __null" failed at server/serverlib/virtualserver.cpp:6581;

[squirrelof09]

I apologize for my short report due to being in a rush.

If it means anything, we banned the client for only one second, we won't be testing this further on our development server.

We were using -nosingleinstance, so no tabs. Both clients were connect the same server, same channel (and different channel first time we did this).

I removed "ignore bans" from my friends group and told him to ban his other identity. He bans himself for only one second. I do not see the action carryout on my TS clients end. The process ends immediately on the server. THe server crashes and the above entry appears in the log.

My friend is not online right now, but I suspect he's using either 3.0.7 or 3.0.8 client version. However, the server is 3.0.6.1 Windows 64bit.

Hope that helps. Couldn't tell if you have already figured this out.

[hunterpl]

Hello yeah that bug work only if you open in 2 tabs same UID, after that make ban for yourself for 1 s after few second, server make crash permamently, Epic Fail, tested on 3.0.5 and 3.0.6.1 , 3.0.7 version server.

[SilentStorm]

For the Record:
The Ban does get stored in the Database, and the Server crashes instantly before any more Clients get kicked/banned from the server because the server instantly crashes!
The Reason it looks like its taking a few seconds is just because the CLient will wait while assuming a bad connection to the server before timing out.

[dante696]

I was able to reproduce it on server 3.0.6.1 and MySql (not with sqlite).
Client logging has to be enabled for that.

Edit
The databae type did not matter, it happend, when client id 1 banned client id2 or 3 or 4 etc....
The invoker neededa lower clid as the target itsellf.

[dante696]

This will be fixed with our next server release.

[Dream]

Hello,
I am ATHP and I have a problem.

At my instance some virtual servers crash with the critical error

CRITICAL|VirtualServer |  1| Assertion "client != __null" failed at server/serverlib/virtualserver.cpp:6581;

When will be the next server release? Or how to fix the bug?

[dante696]

I can not say when server version 3.0.8 will be released.

[PotaBlava]

I can not say when server version 3.0.8 will be released.

But, this issue will be solved in server 3.0.7, isn't it?.

[dante696]

The issue issolved in Version 3.0.7 and a pre version can be found here
http://forum.teamspeak.com/showthrea...ase-Discussion