Subject: Re: MOO on a Sun4

From: vaughaog <[email-masked]>
Date: Mon, 7 Jun 1993 11:21:16 -0700

I'm sure it said "SERVER PANIC" originally, but now I think it's to do with
open_network_connection(); as the last log entries but two said

Jun  7 15:59:28: ACCEPT: #-75 on 14 from open_network_connection()
Jun  7 15:59:29: DISCONNECTED: #-75 on 14 from open_network_connection()

and then the log ends.

stats:

dougal% /usr/etc/pstat -s
10520k allocated + 1172k reserved = 11692k used, 71104k available

dougal% ps -aux
USER       PID %CPU %MEM   SZ  RSS TT STAT START  TIME COMMAND
whiteve    955  0.0 24.1 7264 6812 ?  S    17:19   3:50 ./c c.db c.db.new

dougal% ls -l
total 8550
-rwxr-xr-x  1 whiteve    647168 Jun  7 17:18 c
-rw-r--r--  1 whiteve   4010019 Jun  7 15:43 c.db
-rw-r--r--  1 whiteve   4010543 Jun  7 19:02 c.db.new
-rw-r--r--  1 whiteve      6211 Jun  7 19:06 c.log
-rw-r--r--  1 whiteve     45818 Jun  7 17:19 c.log.old
-rwx------  1 whiteve      1793 Jun  3 20:18 restart

Everytime I come back to log in someone tells me 'the MOO is down again', it's
most infuriating...
Could it be a bug, or something to do with ONC, or what??? Or is the DB just
too big???

Help - MagicDragon@MagicMOO

---

From: Pavel Curtis <[email-masked]>
Date: Mon, 7 Jun 1993 11:48:47 -0700

> Date:	Mon, 7 Jun 1993 11:21:16 -0700
> From:	vaughaog <[email-masked]>
> 

It doesn't sound like a bug in ONC and it's certainly not that the DB is `just
too big' (since it's pretty tiny by comparison with LambdaMOO).  If you get a
`panic', then there should be a message in the log saying something more and
there should be a core file around.  If the server process is gone but the log
doesn't contain a PANIC entry, then either the server was killed by an
uncatchable signal (e.g., `kill -9' or a page fault to a deleted NFS-mounted
server binary file) or else the operating system crashed without giving the
server a chance to save its state.  In these situations, you've got to figure
out what that external killing force is and fix it.

If, on the other hand, you're getting a PANIC entry in the log, then I'd need
to know some more information to help you.  First, what's the PANIC reason
given in the log?  Second, start up a debugger on the executable and the core
file and let me know what a stack backtrace looks like.

	Pavel