Subj : Zombie Node?
To   : Paul Quinn
From : Robert Wolfe
Date : Sat Aug 05 2017 07:07 am

* In a message originally to Robert Wolfe, Paul Quinn said:

> 220/60
> 267/155
> 396/45
> Hi! Robert,

> On 08/04/2017 10:40 PM, you wrote:

>  RW> Up until Monday I was not having any issues with FE.  However, I have
>  RW> noticed that packets are being scanned out to a "zombie node" that I
>  RW> do not have configured in my FE setup and was wondering how to go
>  RW> about tracking down where that node might be set up if it is not set
>  RW> up in the node book in FE at all?

> Two possibilities that come immediately to mind: a now-erroneous entry in
> your 'pack' route file, or, a bad second entry for a node (just under
> their main address) in the node manager?

> Since FE doesn't use the nodelist that may have changed a node's status,
> then that can't be the source of the error.  What you have there is an
> operator-induced error.  ;-)

> Cheers,
> Paul.

> --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101
> Thunderbird/31.4.0
>  * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Thanks for the info.  The ony way I knew about it was because of an
ARChiverr (the archiver that was being called was literally SEA's
ARC).  Once I put that in place it looks like the errors stopped and
operation has returned to normal.

--- EleBBS/OS2 v20120208.d
* Origin: Neptune's Lair/2 * Olive Branch, MS USA * os2bbs.org (1:116/18)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.