Page 1 of 1

NOTIFY ADMINS WHEN SERVER IS DOWN

Posted: Wed Jan 12, 2011 10:41 am
by BullDogg
Please let one of the uber admins know if you notice the server down. Yesterday it was down for 6 hours until someone finally told me and I got it going again. So, pm one of us and let us know. PM Mongo, Strider, Tommy, Punisher or me but make sure an upper admin knows. Thanks!

Re: NOTIFY ADMINS WHEN SERVER IS DOWN

Posted: Wed Jan 12, 2011 3:04 pm
by BkW // ZtluhcS =HH=
ya dont notify me i dont have a computer and i may be back soon getting tired of not playing drinking and talking shit to all you whores

Re: NOTIFY ADMINS WHEN SERVER IS DOWN

Posted: Thu Jan 13, 2011 12:56 am
by DeUltimaPunisher
BkW // ZtluhcS =HH= wrote:ya dont notify me i dont have a computer and i may be back soon getting tired of not playing drinking and talking shit to all you whores
NO COMPUTER!? Well no wonder you've been missing!

I'm sure me and a few other members could come up with enough spare parts to build you one! I know I got a spare AM2+ motherboard and DDR2 RAM.

Fuck let us know if you need help in that department!

Re: NOTIFY ADMINS WHEN SERVER IS DOWN

Posted: Thu Jan 13, 2011 1:03 am
by DeUltimaPunisher
BullDogg wrote:Please let one of the uber admins know if you notice the server down. Yesterday it was down for 6 hours until someone finally told me and I got it going again. So, pm one of us and let us know. PM Mongo, Strider, Tommy, Punisher or me but make sure an upper admin knows. Thanks!

Lots of people did let us know, so I don't see the point of this post...

Tommy and Strider were both aware of the situation and were trying to reboot the server too. I believe the problem was the machine, for example if the HD get's full this happens. Once NFO notices the problem they respond buy cleaning up some space, they have also expressed interest in replacing the HD array connected to our server. Not a simple task for those who don't know how enterprise servers work, it's not like a normal computer where you just swap out a HD or add one.

The only reason your reboot fixed things was it was most likely after NFO had fixed the problem with the machine its self, thus it didn't repeat.