Reset Password
Existing players used to logging in with their character name and moo password must signup for a website account.
- FancyPenguin 5m
- Baron17 1m
- Caetanosandy 1s
- Cainite313 12m
- Jericho 41s
- Grizzly666 2s BEAT THEIR FACE IN.
- RealHumanBean 7s
- MrWolfSpawn 26s
- Mory 8s Jikook ftw. Army for lyf.
- hello_marmalade 22m
- Strummer 0s
- desearcher 4s
- BCingyou 36s
w Dreamer 12m
- Megabossrex 3m
- Kiwi 3m I guess there's always something killing me.
- Mercury 13s
- Revex 54s
- Manywaters 3m
- deaddragon 3s
c Butako 35s Butakooooo the builder. Can she fix it? Eh.
- PriceCheck 28m
- Selly 18s
- HolyChrome 1m
- Jonquille 4m
- Baguette 7h thanks, i hate it
- Skylis 16m
- Beepboop 12m
j Johnny 4h New Code Written Nightly. Not a GM.
And 22 more hiding and/or disguised
Connect to Sindome @ 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.


there are days when i quite enjoy this forum.

Only some days, B?'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?

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

Thanks Johny!

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



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?