• FidoPoll scattering BSY files everwhere

    From bl00d@21:1/162 to All on Wednesday, September 21, 2016 20:27:00
    There, I got your attention :)

    Recently FidoPoll seems to be leaving BSY files laying around, I think I
    might have tracked it down, but not sure. It seems to happen when it has
    a problem connecting to another system. In the last day it attempted to
    connect 3 times and 2 of those 3 times.

    This morning after a fresh start (fidopoll killbusy), fidopoll ran on
    it's own at 7:27, it got one poll in, and then it timed out on the next
    node and then the rest are all busy. BSY files are created and then
    fidopoll won't run again until I clear them.

    Here is a snipped from the log file

    Sep 21 07:27:21 FIDOPOLL Version 1.12 A31
    Sep 21 07:27:21 Scanning 42:1/1
    Sep 21 07:27:21 Queued 0 files (0 bytes) to 42:1/1
    Sep 21 07:27:21 Polling BINKP node 42:1/1
    Sep 21 07:27:21 Connecting to loybbs.net
    Sep 21 07:27:21 Connected
    Sep 21 07:27:21 Authorization State: 1 HH:0 NH:1
    Sep 21 07:27:21 Sent: NUL SYS Razor's Domain 3.141592...
    Sep 21 07:27:21 Sent: NUL ZYZ bl00d
    Sep 21 07:27:21 Sent: NUL VER Mystic/1.12A31 binkp/1.0
    Sep 21 07:27:21 Sent: ADR 1:19/50@fidonet 21:1/162@fsxnet
    80:210/2@retronet 21:2/162@usenet 618:200/36@micronet
    101:1100/14@sinnet 42:43/1@sfnet
    Sep 21 07:27:21 Recv: NUL OPT ENC-DES-CBC
    Sep 21 07:27:21 Authorization State: 2 HH:1 NH:0
    Sep 21 07:27:21 OPT ENC-DES-CBC
    Sep 21 07:27:21 Recv: NUL SYS Legends of Yesteryear BBS
    Sep 21 07:27:21 SYS Legends of Yesteryear BBS
    Sep 21 07:27:21 Recv: NUL ZYZ Dallas Vinson
    Sep 21 07:27:21 ZYZ Dallas Vinson
    Sep 21 07:27:21 Recv: NUL LOC Huntsville, AL
    Sep 21 07:27:21 LOC Huntsville, AL
    Sep 21 07:27:21 Recv: NUL PHN loybbs.net
    Sep 21 07:27:21 PHN loybbs.net
    Sep 21 07:27:21 Recv: NUL NDL MO,CM,TCP,IFC,TEL,VMP,BND,IBN
    Sep 21 07:27:21 NDL MO,CM,TCP,IFC,TEL,VMP,BND,IBN
    Sep 21 07:27:21 Recv: NUL TIME Wed, 21 Sep 2016 12:27:06 -0500
    Sep 21 07:27:21 TIME Wed, 21 Sep 2016 12:27:06 -0500
    Sep 21 07:27:21 Recv: NUL VER Argus/3.210/ binkp/1.0
    Sep 21 07:27:21 VER Argus/3.210/ binkp/1.0
    Sep 21 07:27:21 Authorization State: 2 HH:0 NH:1
    Sep 21 07:27:21 Recv: ADR 1:123/256 40:100/31 42:1/1 901:1/3
    Sep 21 07:27:21 Authorization State: 2 HH:1 NH:0
    Sep 21 07:27:21 Sent: PWD RDMYST16
    Sep 21 07:27:21 Authorization State: 5 HH:0 NH:1
    Sep 21 07:27:22 Recv: OK
    Sep 21 07:27:22 Authorization State: 5 HH:1 NH:0
    Sep 21 07:27:22 Recv: NUL TRF 0 697
    Sep 21 07:27:22 Recv: FILE 14170232.PKT 697 1474430788 0
    Sep 21 07:27:22 State RxS:1 TxS:1 HH:1 NH:0
    Sep 21 07:27:22 Receiving 14170232.PKT (697 bytes)
    Sep 21 07:27:22 Sent: EOB
    Sep 21 07:27:22 State RxS:2 TxS:4 HH:0 NH:1
    Sep 21 07:27:22 Recv: Data 256/256
    Sep 21 07:27:22 State RxS:2 TxS:4 HH:1 NH:0
    Sep 21 07:27:22 Received Rx Data 256
    Sep 21 07:27:22 Recv: Data 441/441
    Sep 21 07:27:22 Received Rx Data 697
    Sep 21 07:27:22 Sent: GOT 14170232.PKT 697 1474430788
    Sep 21 07:27:22 Recv: Data 0/0
    Sep 21 07:27:22 State RxS:1 TxS:4 HH:1 NH:0
    Sep 21 07:27:22 State RxS:1 TxS:4 HH:0 NH:1
    Sep 21 07:27:22 Recv: EOB
    Sep 21 07:27:22 State RxS:1 TxS:4 HH:1 NH:0
    Sep 21 07:27:22 Session complete (0 sent, 1 rcvd, 0 skip)
    Sep 21 07:27:22 Scanning 618:200/1
    Sep 21 07:27:22 Queued 0 files (0 bytes) to 618:200/1
    Sep 21 07:27:22 Polling BINKP node 618:200/1
    Sep 21 07:27:22 Connecting to curmudge.hopto.org <<<<<<<<<<<<<<
    Sep 21 07:29:29 Unable to connect
    Sep 21 07:29:29 Scanning 80:210/0
    Sep 21 07:29:29 80:210/0 is busy; skipping
    Sep 21 07:29:29 Scanning 21:1/100
    Sep 21 07:29:29 21:1/100 is busy; skipping
    Sep 21 07:29:29 Scanning 1:396/45
    Sep 21 07:29:29 1:396/45 is busy; skipping
    Sep 21 07:29:29 Scanning 21:2/100
    Sep 21 07:29:29 21:2/100 is busy; skipping
    Sep 21 07:29:29 Scanning 618:200/36.1
    Sep 21 07:29:29 618:200/36.1 is busy; skipping
    Sep 21 07:29:29 Scanning 80:210/2.1
    Sep 21 07:29:29 80:210/2.1 is busy; skipping
    Sep 21 07:29:29 Scanning 21:1/162.1
    Sep 21 07:29:29 21:1/162.1 is busy; skipping
    Sep 21 07:29:29 Scanning 101:1100/2
    Sep 21 07:29:29 101:1100/2 is busy; skipping
    Sep 21 07:29:29 Scanning 1:19/50.1
    Sep 21 07:29:29 1:19/50.1 is busy; skipping


































































    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A31 (Raspberry Pi)
    * Origin: Razor's Domain 3.141592... (21:1/162)
  • From Avon@21:1/101 to bl00d on Thursday, September 22, 2016 18:07:00
    On 09/21/16, bl00d pondered and said...

    There, I got your attention :)

    Recently FidoPoll seems to be leaving BSY files laying around, I think I

    That's correct it creates them for all nodes while a process is running, removing them for each echonode once it has called it. Are you using fidopoll send or forced out of interest?

    might have tracked it down, but not sure. It seems to happen when it has
    a problem connecting to another system. In the last day it attempted to connect 3 times and 2 of those 3 times.

    Yep, sounds right, if a system is hanging during a binkp / fidopoll session things can go amiss.

    This morning after a fresh start (fidopoll killbusy), fidopoll ran on
    it's own at 7:27, it got one poll in, and then it timed out on the next node and then the rest are all busy. BSY files are created and then fidopoll won't run again until I clear them.

    If the fidopoll session is not ending normally then it's usual for the .bsy files to remain against the other nodes.

    They key to progressing this would be to isolate the system causing you the polling issues. Is there mail waiting to be sent to it? Could you instead set up a specific timed fidopoll to each echonode and remove the polling of this system while you debug?

    Another option is to identify the packet your trying to send for this node (assuming you are sending) and remove it from the outbound dir for now to
    free up the rest of the fidopolling session.

    Sep 21 07:27:22 Recv: EOB
    Sep 21 07:27:22 State RxS:1 TxS:4 HH:1 NH:0
    Sep 21 07:27:22 Session complete (0 sent, 1 rcvd, 0 skip)

    So the first one is fine.

    Sep 21 07:27:22 Polling BINKP node 618:200/1
    Sep 21 07:27:22 Connecting to curmudge.hopto.org <<<<<<<<<<<<<<
    Sep 21 07:29:29 Unable to connect

    That's a heck of a long time before timeout, what do you have your settings
    set to for timeout for this node?

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From bl00d@21:1/162 to Avon on Thursday, September 22, 2016 09:31:00
    Avon wrote to bl00d <=-

    On 09/21/16, bl00d pondered and said...

    That's correct it creates them for all nodes while a process is
    running, removing them for each echonode once it has called it. Are you using fidopoll send or forced out of interest?

    This was a forced poll, I run that every hour to poll all nodes - But I
    am thinking about changing it to just hubs since I have setup several
    points.

    Creating the BSY files all at once is probably the logical way to do it
    these days since things run so darn fast. But I figured it would not
    create *.bsy for a node until it actually tries to connect to it.

    If the fidopoll session is not ending normally then it's usual for the .bsy files to remain against the other nodes.

    I don't think it is ending abnormally, looking at the logs it looks
    like it is just timing out on a down node and since it creates all
    the bsy files at the start, when it goes to the rest of the nodes, it
    sees there BSY files and skips them?

    They key to progressing this would be to isolate the system causing you the polling issues. Is there mail waiting to be sent to it? Could you

    I think it is just a node that is down and the connection is timing out
    (see below)

    Sep 21 07:27:22 Polling BINKP node 618:200/1
    Sep 21 07:27:22 Connecting to curmudge.hopto.org <<<<<<<<<<<<<<
    Sep 21 07:29:29 Unable to connect

    That's a heck of a long time before timeout, what do you have your settings set to for timeout for this node?

    Yea, I noticed that myself, I have the timeout set to 30 in the node
    setup. So not sure why it was over 120 seconds.

    I have set this hub to inactive until I confirm that it is back online.

    Kev

    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A31 (Raspberry Pi)
    * Origin: Razor's Domain 3.141592... (21:1/162)