quote:Originally posted by AWH_ReApErIt happened 3 times last night, but I found out someone was hacking my server. Or at least that's the idea I got when someone joined the server, tried logging into admin with a bad password, and the server crashed. After that, the same guy would join the server, and *poof*, server's dead. So I banned his IP and it hasn't happened since.
OK - sadly I don't think I can prevent from this happening if there's someone else involved.
quote:Also, is it possible to run this from a webserver so my computer doesn't have to constantly be on and logged into SARJ for its WONDERFUL features to be available?
Not for this release, I'm afraid. However, since I'm releasing the source code, perhaps someone could make something like this?
quote:[EDIT]
Okay, the server crashed again (This time, it's apparently because of a bad map change). So, leaving SARJ open, I restarted the server through SSH. I try to reconnect with SARJ, and it says "Connecting..." and never actually connects. I have to restart SARJ to connect again.
[/EDIT]
Bad map change? Hmm...I don't think SARJ has anything to do with changing maps.
quote:[EDIT2]
It crashed again, this time for no apparent reason. How do I run a packet logger? =S
[/EDIT2]
If you're on linux you can use tcpdump. Ethereal is also popular and works in Windows.
quote:[EDIT3]
Very small, nit-picky thing. ;)
The pings are displayed differently in SARJ than they are in the server. I had a clan member join the server, and tell me the ping of someone in there. He said it was between 500 and 750. In SARJ, it said he had about 210.
[/EDIT3]
This might just be the result of getting a different 'snapshot' of the ping. SARJ just extracts it from refresh packet - I'm not sure how it's done when in-game. I'll test out what SARJ says against the Soldat Admin tool later and see if they're different.
quote:[EDIT4]
The right click menu is gone. Not sure if you inteded to take it out, but it's gone. =(
[/EDIT4]
Yeah, I noticed that myself yesterday. That's fixed now, so don't worry about it :)
Thanks for the detailed reports - they're helping a lot.
[EDIT]
I've managed to fix a few things and have updated the file. Please download the new one and use that one now (same address). Also, could you run SARJ from the command prompt instead of the jar file? That way you will see useful information spat out from the JVM when things go wrong :) If SARJ is 'crashing', it is likely that an exception has ocurred and it's halted - you just can't see the message unless you run from a console. Remember, the command is:
java -jar sarj.jar
[/EDIT]