full server bug?

[Mizrim]

Its not a restart fix. Thatll just let everyone join til it fills again.

If possible, look at where you guys raised the cap on the server.ini or the mySQL database. It seems like whats happening is people are logging out but the server is keeping the mysql player data up instead of storing and dumping.

Whats the game code written in exactly? I could assist if possible in a simple solution. Just need to check the files where you guys edited the mysql player data. Its probably a simple / or > or ; line broken lol.

good thinking! this issue seems to have started after cap was raised last night..

[Kingofpol]

Its not a restart fix. Thatll just let everyone join til it fills again.

If possible, look at where you guys raised the cap on the server.ini or the mySQL database. It seems like whats happening is people are logging out but the server is keeping the mysql player data up instead of storing and dumping.

Whats the game code written in exactly? I could assist if possible in a simple solution. Just need to check the files where you guys edited the mysql player data. Its probably a simple / or > or ; line broken lol.

good thinking! this issue seems to have started after cap was raised last night..

This happens alot in coding lol. Im a modder for arma and garrysmod myself & and regisitered coder at scriptfodder.com

I PMed azureal if he needed any help or if i could apply for a temp helper

[Azarael]

It's nothing to do with SQL.

What happens is that the connection goes into a strange one-way state. Input from the client is recognised by the server, however, the server does not respond except to send a massive garbage packet at irregular intervals. When the client terminates the connection, it appears that the server end is left open, and so a ghost is created.

Example of such a packet: http://pastebin.com/D2PtMHru

Nothing within the code has been changed that might obviously cause this to happen... though I do see that experience messages now often bug and show that they've come from BOs or keeps.

[Kingofpol]

It's nothing to do with SQL.

What happens is that the connection goes into a strange one-way state. Input from the client is recognised by the server, however, the server does not respond except to send a massive garbage packet at irregular intervals. When the client terminates the connection, it appears that the server end is left open, and so a ghost is created.

Example of such a packet: http://pastebin.com/D2PtMHru

Nothing within the code has been changed that might obviously cause this to happen... though I do see that experience messages now often bug and show that they've come from BOs or keeps.

Ah so server had a spaz moment haha, my bad. Usually when this stuff happens on my servers im working on its literally the database half the time from a small broken line etc.

BO and keeps could be from the taking process maybe? Have you run test of taking a keep and seeing how the code completes it and dumps the action?