Horrid Site Response

[Scott Greczkowski]

I'm glad damaged knows what he's talking about, 'cause he's way past my wiki... Glad to see everything seems to be back to normal. I hope this isn't a hardware issue, Scott.

No this was more a case of a process got stuck which caused the server load to shoot up, and Scott decided to fix it by rebooting the machine, however when the reboot happened a file was beaing written in the OS which got corrupted and prevented the server from booting back up.

The bad file was restored via the console and then we were back online. Thanks to Ler for his help getting us back online.

 

[damaged]

I'm glad damaged knows what he's talking about, 'cause he's way past my wiki... Glad to see everything seems to be back to normal. I hope this isn't a hardware issue, Scott.

What wiki would that be?

 

[damaged]

No this was more a case of a process got stuck which caused the server load to shoot up, and Scott decided to fix it by rebooting the machine,

Exactly what nice can help prevent, the runaway process would have been low priority, and the other system processes would have had higher priorities, allowing him to issue a killall, or sync/reboot without paralyzing cpu lag.

 

[Foxbat]

No this was more a case of a process got stuck which caused the server load to shoot up, and Scott decided to fix it by rebooting the machine, however when the reboot happened a file was beaing written in the OS which got corrupted and prevented the server from booting back up.

I hate it when that happens... Especially that, "aw, sh!t" you feel when the server hasn't come back in the expected amount of time.

 

[Foxbat]

What wiki would that be?

Whatever you said here:

Saw some extended (10-15 mins) routing issue again tonite with inaps pnap, perhaps you could ask your provider (and maybe to ask their provider) to stop announcing your routes/ip space to inaps pnaps, then you would not have to worry about inap suckage, all routes to you would be handled by the rest of the peers, excluding inap.

It's too late to get Googling inap/inaps and pnap/pnaps (UNIX and Internet, I'm guessing). All I know is I need to nap!

 

[Scott Greczkowski]

Nap sounds good, I am off to bed too... Got to be up for work in 5 hours.

 

[damaged]

Whatever you said here:It's too late to get Googling inap/inaps and pnap/pnaps (UNIX and Internet, I'm guessing). All I know is I need to nap!

Well, you said 'past my wiki', so I thought you had your own wiki setup, and was interested in checking it out.

BTW:
inap = internap, a provider/carrier (sort of).
pnap = private network access point, it's a packet switched network where two customers connected to the same pnap exchange traffic through the pnap without transmitting over the internet 'backbones'.