Subject: Nasty MOO Hang

From: [email-masked] (Joshua R. Poulson)
Date: Tue, 22 Jun 1993 05:02:20 -0700

Last night our Moo, which had been running nicely since June 10th, hung up
with the following messages in the logs:

Jun 22 00:03:26: CHECKPOINTING on DF.db.new.#32# ...
Jun 22 00:03:43: *** PANIC (in child): Caught signal 10
Jun 22 00:03:43: *** Child shutting down parent via USR1 signal
Jun 22 00:03:43: SHUTDOWN: shutdown signal received
Jun 22 00:03:43: DUMPING on DF.db.new.#33# ...
Jun 22 00:03:56: *** PANIC: Caught signal 10

The "checkpointed" db seems to be intact by the #33# one was hung halfway 
through the dump and immediately sucked up all available CPU until I stopped
the beastie 8 hours later.

Anyone know where the "USR1" signal is coming from and what could cause such
a thing?

Thanks! --JRP [Shirgall@LambdaMOO, DFMOO, MOOns, and others]

---

From: Pavel Curtis <[email-masked]>
Date: Mon, 28 Jun 1993 15:17:31 -0700

> Date:	Tue, 22 Jun 1993 05:02:20 -0700
> From:	[email-masked] (Joshua R. Poulson)
> 

The USR1 signal is sent by the checkpointing (child) process to the main
(parent) process and is normal.  The nasty thing is the signal 10, indicating
some kind of stray pointer in the server.  If you can use a debugger to send me
a backtrace from the core file, that would help me find and maybe fix the
problem...

	Pavel/Lambda/Haakon