Serenity

It was actually down for the better part of 4 hours and didn't even respond to `kill -SIGKILL $pid` :/ But maybe you're right, might have responded after a good while.. I only tried connecting for hours but never gave it time after sending the SIGKILL. I'll try it next time (if it happens again) :)

I'm actually quite impressed by how little it does use for being in beta. It still begs the question tho why the server hang, which was why I reported the "bug", memory leakage was just a wild guess that I later realized was a bit to crazy.

I'm "stressing" the server right now, trying to weed out any hardware related issues (Since I'm aware that the server is a little bit on the cheap-skate-end of things). It might be that the server runs out of physical memory and there's no memory containment features yet? I mean, a memory leak would appear differently in my world. And as of now I'm at 3.1/3.9 gigs of ram being used up by Avorion, and I bet it will hang in a little while if i keep it running this "hot". I'll get back to you on this. Edit: The stress-test used up as much RAM as possible, but never hung up on me. Appears to be some mechanisms to prevent that from happening. Did skip a frame or two, that's rpobably what that is. Still not sure what caused the hangup.

Howdy, * Attached log Appears that after jumping around like crazy last night and then all players logging off, the server simply just hung up on all the sockets around this afternoon. The server still kept logging, but the server page/status was unreachable. Essentially I don't have much to go on here other than the fact that it was nonresponsive to SIGHUP/SIGINT/SIGKILL, and i had to forcefully shut it down. No data was lost and it's up and running again. * http://i.imgur.com/veAjKsT.png Would it be possible to increase the verbosity? Or get something more useful out of these logs?