Vanilla Netrek Server Development Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[VANILLA-L:733] Re: daemonII core dumps

For this problem, ERRORS shows ...

forceShutdown for ftww@staff.cs.su.OZ.AU: 15
forceShutdown for cameron@riogrande.digital.com.au: 15
forceShutdown for netrek@annex8-57.dial.umd.edu: 15
forceShutdown for Bozo@syd2-ppp-040.tpgi.com.au: 15
forceShutdown for cameron@riogrande.digital.com.au: 15
forceShutdown for s834572@pc10-175.rcondw.rug.nl: 15
forceShutdown for menglaro@slsyd8p29.ozemail.com.au: 15
forceShutdown for Render_2@bundy.alcohol.tne.net.au: 15
forceShutdown for cameron@riogrande.digital.com.au: 15
forceShutdown for Kathleen Ward@force.ampsc.com: 15
forceShutdown for Objekt@rrenfrow.campus.vt.edu: 15
forceShutdown for Bozo@sollis.syd.att.net.au: 15
exitDaemon: got signal 4
exitDaemon: going down on signal 4

Now, the first set of forceShutdown calls are presumably due to the
SIGTERM that the daemon sends to the ntserv processes. Signal number 15.

The last two lines tell me I've had a SIGILL in the daemon.

I suppose the next diagnosis step is to run the daemon with a debug
flag, e.g. by starting the daemon manually with any argument ...

    if (argc > 1)
        debug = 1;

Other information from the server, that may not help ...

The crashes ...

apollo.syd.att.net.au> ls -l core*
-rw-------   1 ollis    users     499712 Dec 10 17:27 core.1
-rw-------   1 ollis    users     499712 Dec 10 17:58 core.2
-rw-------   1 ollis    users     499712 Dec 10 18:16 core.3
-rw-------   1 ollis    users     499712 Dec 10 18:27 core.4
-rw-------   1 ollis    users     499712 Dec 10 18:39 core.5


>From logfile; last join before server restart in each case;

Joining: NetThug, (c) Wed Dec 10 17:26:28 1997
        <NetThug@max2p5.albany.albany.net>

Joining: vid, (c) Wed Dec 10 17:57:40 1997
        <root@xmv-as1s32.erols.com>

Joining: Objekt, (d) Wed Dec 10 18:16:00 1997
        <Objekt@rrenfrow.campus.vt.edu>

Joining: guest, (c) Wed Dec 10 18:26:44 1997
        <raymolam@lynx1157.lynx.bc.ca>

Joining: whizkid, (b) Wed Dec 10 18:39:14 1997
        <s834572@pc10-175.rcondw.rug.nl>

>From log; corresponding connections;

       max2p5.albany.albany.net         Wed Dec 10 17:26:21 1997
       max2p5.albany.albany.net         Wed Dec 10 17:26:21 1997
       max2p5.albany.albany.net         Wed Dec 10 17:27:55 1997
       max2p5.albany.albany.net         Wed Dec 10 17:27:55 1997

       xmv-as1s32.erols.com             Wed Dec 10 17:57:13 1997
       xmv-as1s32.erols.com             Wed Dec 10 17:57:19 1997

       rrenfrow.campus.vt.edu           Wed Dec 10 18:15:55 1997
       rrenfrow.campus.vt.edu           Wed Dec 10 18:15:55 1997

       lynx1157.lynx.bc.ca              Wed Dec 10 18:25:18 1997
       lynx1157.lynx.bc.ca              Wed Dec 10 18:25:19 1997
       lynx1157.lynx.bc.ca              Wed Dec 10 18:26:37 1997
       lynx1157.lynx.bc.ca              Wed Dec 10 18:26:38 1997

       pc10-175.rcondw.rug.nl           Wed Dec 10 18:39:06 1997
       pc10-175.rcondw.rug.nl           Wed Dec 10 18:39:06 1997

Strange that some clients cause four connections to the newstartd
ports before logging in.  Any ideas why?

--
James Cameron                                    (cameron@stl.dec.com)
Digital Equipment Corporation (Australia) Pty. Ltd. A.C.N. 000 446 800
+
++ Vanilla-l Mailing List ++
To unsubscribe: send "unsubscribe vanilla-l" to majordomo@real-time.com
For more information: http://archives.real-time.com
References: