It's out of memory, so when it loads up with users (sometimes a few hundred at a time), it just dies because it's using the hard drive for virtual memory, and that'll kill even the best server.
The guy who built the server is in Vegas at the moment (rather than near the datacenter in Boston). He's the one who can install the memory that it needs, but I can't even recall through our conversation logs what type of RAM it needs, so it'll have to wait until he can get back home to even find out what it is so he can buy it.
The server's only at 2 gigs right now, it needs to be roughly doubled. Seems to be doing OK at the moment since the reboot, but who knows...*knocks on wood* Not a good thing in the first place when you have to reboot Linux. >.<
I'm at work, won't be back home for another few hours. If it goes down again, I won't have a way to fix it til then. The proxy here is even more restrictive than it was when I worked here before, so I can't use any of my nifty administrative tools.
The guy who built the server is in Vegas at the moment (rather than near the datacenter in Boston). He's the one who can install the memory that it needs, but I can't even recall through our conversation logs what type of RAM it needs, so it'll have to wait until he can get back home to even find out what it is so he can buy it.
The server's only at 2 gigs right now, it needs to be roughly doubled. Seems to be doing OK at the moment since the reboot, but who knows...*knocks on wood* Not a good thing in the first place when you have to reboot Linux. >.<
I'm at work, won't be back home for another few hours. If it goes down again, I won't have a way to fix it til then. The proxy here is even more restrictive than it was when I worked here before, so I can't use any of my nifty administrative tools.
