[Dxspider-support] Node won't restart properly

[David Ward]

Dirk and Charlie thanks for the hints. I did the stat/user va3pec-5 as Dirk
suggested. Here is what I got

VE3BIP de VE3BIP-7  9-Jul-2003 1104Z >
stat/user va3pec-5
   Access Group: local
          Build: 57.189
       Callsign: VA3PEC-5
      Home Node: VA3PEC-5
       Language: en
      Last Node: VE3BIP-7
   Last Time in:  9-Jul-2003 0116Z
    Locked out?: No
Privilege Level: 1
     Route PC19: Yes
   Type of User: S
        Version: 54.51
VE3BIP de VE3BIP-7  9-Jul-2003 1105Z

I'm not sure quite how to interpret all the output but I presume everything
is OK.

When I did the show/node VA3PEC-5 as Charlie suggested I got
VA3PEC-5  spider

I have also done a bit more investigating using the listen facility.
Here is a trace of what I see. The same pattern repeats over and over. It
starts with
the SABM+ message which I think is a "connect". The AX25 layer answers but
it seems the cluster application doesn't respond. PEC then sends a few ping
commands which the cluster never responds to. Eventually PEC disconnects
with the DISC+ message. Then the pattern
repeats.

2m: fm VE3BIP-7 to VA3PEC-5 ctl RR3- 20:33:39
2m: fm VA3PEC-5 to VE3BIP-7 ctl DISC+ 20:34:11
2m: fm VE3BIP-7 to VA3PEC-5 ctl UA- 20:34:11

2m: fm VA3PEC-5 to VE3BIP-7 ctl SABM+ 20:39:09
2m: fm VE3BIP-7 to VA3PEC-5 ctl UA- 20:39:09
2m: fm VA3PEC-5 to VE3BIP-7 ctl I00+ pid=F0(Text) len 21 20:41:02
0000  PC50^VA3PEC-5^0^H99^M
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR1- 20:41:02
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:43:29
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR1- 20:43:29
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:44:23
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR1- 20:44:23
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:44:37
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR1- 20:44:37
2m: fm VA3PEC-5 to VE3BIP-7 ctl I01+ pid=F0(Text) len 26 20:44:38
0000  PC51^VE3BIP-7^VA3PEC-5^1^M
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR2- 20:44:39
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:44:51
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR2- 20:44:51
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:47:06
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR2- 20:47:06
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:49:07
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR2- 20:49:07
2m: fm VA3PEC-5 to VE3BIP-7 ctl I02+ pid=F0(Text) len 26 20:49:10
0000  PC51^VE3BIP-7^VA3PEC-5^1^M
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR3- 20:49:10
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:51:11
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR3- 20:51:11
2m: fm VA3PEC-5 to VE3BIP-7 ctl RR0+ 20:53:38
2m: fm VE3BIP-7 to VA3PEC-5 ctl RR3- 20:53:38
2m: fm VA3PEC-5 to VE3BIP-7 ctl DISC+ 20:54:10
2m: fm VE3BIP-7 to VA3PEC-5 ctl UA- 20:54:10


============================================


> To see how a callsign is set (and other useful information held about
> it) do:
>
> stat/user va3pec-5
>
> This will tell whether it is a node, locked out, what sort of thing it
> is and other useful stuff.
>
> Dirk
>
> On Wed, 2003-07-09 at 03:10, charlie carroll wrote:
> > Dave:
> > Was va3pec-5 connected at the time you did the sh/node command?  A node
> > needs to be connected for it to show when using the sh/node command.
> >
> > Try sh/node va3pec-5.
> >
> > 73 charlie, k1xx
> >

>