- coconut 1m Partially inactive during summer.
- FancyPenguin 6m
- Ryuzaki4Days 50s Shoot your ace in the face.
- crashdown 21m
- Baron17 1m
- Ebos 11s
- BCingyou 1m
- Grey0 1m
- MrJDucky2 4m
- himble 12s youtu.be/og243Dom4Sw
- jsmith225 8h
a Cerberus 9h Head Builder & GM when I need to
- Dorn 13s https://www.youtube.com/watch?v=7OUqUiZQxs4
- Chrissl1983 14h working on my @history for too long...
- Azelle 20h
j Johnny 9h New Code Written Nightly. Not a GM.
And 17 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Server Panic?!?!
Somebody get the valium..

Server panicked about midnight PST.. Really not much more to say..

We should all get it a copy of the Hitchhiker's Guide to the Galaxy, methinks.

You know, somehow, despite it's advice, Arthur always managed to anyway.

Of course 98% of the advice offered in it was questionable, depending on your idea of fun, species, and ability to make anything infinately improbable.

-Kevlar

there are days when i quite enjoy this forum.

Only some days, B? Man...you're missin out...

i'm confused

Another server panic, exactly at midnight PDT (if that isn't a clue where to look *coughs*), dropped back to 11:45, so we lost 15 minutes.

And I have to scan 300 more photographs! :cursing:

Well I could always recreat Gridka on Chiba City MUD...

Ah sleep, who needs it?
:biggrin:

Prais Jesus, Kalli, and what ever Voodoo god watches over Servers.

Thanks Johny!
:cheesy:

now i'm all confused...


what makes a server panic anyway....

i didn't know servers had feelings... i hope we arent mistreating it... hehehe

STOP THE SERVER ABUSE! Eat a carrot!

+()()|_

In our case, a sig 11.

Signal 11, or officially know as "segmentation fault", means that the program accessed a memory location that was not assigned.

Mainly this happens (in stable production systems like ours) due to timing problems in the CPU <-> cache <-> memory path, but other explinations include stray alpha particles randomly flipping a bit, and of course, software bugs.

I'm pretty convinced it's not a LambdaMOO issue (if it were we should be able to reproduce it with the same hour old database before the panic), which leaves my custom compiled kernel, and the hardware as the possible culprits.

Take your pick.

One day I may upgrade the kernel to a newer version, but as this one has been solid save a few panics after 2+ months straight of uptime, It's not a priority. Why fix what's (mostly) not broken?

-Kevlar