Forums » General
Server down?
I'm stuck on the 'Select your character' screen, is the server down or is this a client issue? It doesn't appear to change no matter what I have tried in the last fifteen minutes.
New to the game, and loving it so far!
New to the game, and loving it so far!
The server lagged out again and it's down for the moment. And I suspect it won't be available until someone walks into the Guild offices to reset it. I think a1k0n said something about raybondo coming in tonight, but I'm not sure. But just a heads up for those who had planned on playing today.
=(
/me wishes the server would have an auto-reset feature
EDIT: Cross that. Incarnate has remote access to the server. He's on IRC now trying to fix it.
=(
/me wishes the server would have an auto-reset feature
EDIT: Cross that. Incarnate has remote access to the server. He's on IRC now trying to fix it.
fixed.
It was autoreset or something :D
cheers
It was autoreset or something :D
cheers
It does have an auto-reset feature. It leaked memory again, and took a long time to core-dump 280 megs of crap, which I can't cancel. I fixed more memory leaks, but I'm not certain that they're all taken care of. Server memory usage is still rising slowly, but much more slowly than before.
another garbage truck or??
hmm, i was just about to post a question on the status of the server myself.
Devs?
Edit NM it finally let me in after waiting on the connecting screen for 5 minutes.
Devs?
Edit NM it finally let me in after waiting on the connecting screen for 5 minutes.
From what I hear, Incarnate ripped the wires out taking off from the back parking lot in his Vulture last night. Damned long wings those things have.
I want a vulture, Those gauss cannons would make the morning commute much more enjoyable :)
s404 was not backed up noooooooooooooooooooooooooooo
sc404 and sc405 were temp and so that the next time the server gets restarted those sectors went away.
The server is getting worse. Recently, I had to go to the connecting screen, hit cancel and repeat OVER 200 TIMES before I got a good connection.
Wow, the server process ran out of memory. Cool! Now I have a coredump showing where it's leaking. Good thing we rewrote that heap of crap.
The new one still has that connecting bug though (but you shouldn't have to retry more than once). Haven't tracked it down yet.
404 and 405 will be missed. But hey, since I didn't give you a station, nobody got stuck (/explode if you think you're stuck).
The new one still has that connecting bug though (but you shouldn't have to retry more than once). Haven't tracked it down yet.
404 and 405 will be missed. But hey, since I didn't give you a station, nobody got stuck (/explode if you think you're stuck).
>> you shouldn't have to retry more than once
So is there a 200 time exception to that rule?
So is there a 200 time exception to that rule?
It's only applies to people that go by the name "roguelazer".
"Wow, the server process ran out of memory. Cool!"
A1k0n, Dunno if you can do this or not but I hear that valgrind is really good for tracking down memory leaks in programs. Of course, it requires you to run the server inside of valgrind which means it runs dog slow as it is "emulated" but it does work.
A1k0n, Dunno if you can do this or not but I hear that valgrind is really good for tracking down memory leaks in programs. Of course, it requires you to run the server inside of valgrind which means it runs dog slow as it is "emulated" but it does work.
Naturally, I use valgrind all the time. The memory leak in question isn't "leaked" in the sense that it's no longer accessible, though, so valgrind doesn't catch it. It's just junk data that's still held onto in some data structure somewhere. I've been planning to rewrite at a minimum the portion which I'm certain is leaking the memory for a long time though so I've been relatively apathetic. Now the whole server has been rewritten.
Unfortunately I can't easily valgrind the client because the nvidia drivers drive it nuts, but I've done it in the past using Mesa (talk about slow.. takes 5 minutes to enter a sector..)
Unfortunately I can't easily valgrind the client because the nvidia drivers drive it nuts, but I've done it in the past using Mesa (talk about slow.. takes 5 minutes to enter a sector..)
LOL. Want slow, run KDE under valgrind. :)
MMmmm, yes...I'll bet GNOME runs MUCH better..:]
Yea, I bet GNOME does run better - Fenix and I gots to stick together
/gnome forever.
/gnome forever.