• Oddity

    From Rick Smith@1:105/10.1 to All on Sat May 1 20:51:58 2021
    Greetings All!

    So occasionally when I poll my bbs using binkd/hpt I get this error, it repeats my aka's then errors but if I poll again its fine? Any thoughts?

    addr: 1:105/10@fidonet (n/a or busy)
    + 20:48 [131872] addr: 21:1/190@fsxnet
    + 20:48 [131871] addr: 21:1/190@fsxnet (n/a or busy)
    + 20:48 [131871] addr: 77:1/130@scinet (n/a or busy)
    + 20:48 [131872] addr: 77:1/130@scinet
    + 20:48 [131872] addr: 46:10/136@agoranet (n/a or busy)
    + 20:48 [131871] addr: 46:10/136@agoranet
    + 20:48 [131871] addr: 44:100/28@dorenet (n/a or busy)
    + 20:48 [131872] addr: 44:100/28@dorenet
    ? 20:48 [131871] called 21:1/190@fsxnet, but remote has no such AKA
    + 20:48 [131871] done (to 21:1/190@fsxnet, failed, S/R: 0/0 (0/0 bytes))



    ----
    Regards,


    Rick Smith (Nitro)

    ... Stress - the phone bill after BBSing
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (1:105/10.1)
  • From Oli@2:280/464.47 to Rick Smith on Sun May 2 09:28:51 2021
    Rick wrote (2021-05-01):

    Greetings All!

    So occasionally when I poll my bbs using binkd/hpt I get this error, it repeats my aka's then errors but if I poll again its fine? Any thoughts?

    addr: 1:105/10@fidonet (n/a or busy)
    + 20:48 [131872] addr: 21:1/190@fsxnet
    + 20:48 [131871] addr: 21:1/190@fsxnet (n/a or busy)
    + 20:48 [131871] addr: 77:1/130@scinet (n/a or busy)
    + 20:48 [131872] addr: 77:1/130@scinet
    + 20:48 [131872] addr: 46:10/136@agoranet (n/a or busy)
    + 20:48 [131871] addr: 46:10/136@agoranet
    + 20:48 [131871] addr: 44:100/28@dorenet (n/a or busy)
    + 20:48 [131872] addr: 44:100/28@dorenet
    ? 20:48 [131871] called 21:1/190@fsxnet, but remote has no such AKA
    + 20:48 [131871] done (to 21:1/190@fsxnet, failed, S/R: 0/0 (0/0 bytes))

    do you have a 4D setup? (same default zone number for every domain)

    ---
    * Origin: . (2:280/464.47)
  • From Rick Smith@1:105/10.1 to Oli on Sun May 2 13:48:10 2021
    Greetings Oli!

    Sunday May 02 2021 09:28, you wrote to me about an urgent matter!:

    * Forwarded from area 'binkd'
    Rick wrote (2021-05-01):

    Greetings All!

    So occasionally when I poll my bbs using binkd/hpt I get this
    error, it repeats my aka's then errors but if I poll again its
    fine? Any thoughts?

    addr: 1:105/10@fidonet (n/a or busy)
    + 20:48 [131872] addr: 21:1/190@fsxnet
    + 20:48 [131871] addr: 21:1/190@fsxnet (n/a or busy)
    + 20:48 [131871] addr: 77:1/130@scinet (n/a or busy)
    + 20:48 [131872] addr: 77:1/130@scinet
    + 20:48 [131872] addr: 46:10/136@agoranet (n/a or busy)
    + 20:48 [131871] addr: 46:10/136@agoranet
    + 20:48 [131871] addr: 44:100/28@dorenet (n/a or busy)
    + 20:48 [131872] addr: 44:100/28@dorenet
    ? 20:48 [131871] called 21:1/190@fsxnet, but remote has no such
    AKA + 20:48 [131871] done (to 21:1/190@fsxnet, failed, S/R: 0/0
    (0/0 bytes))

    do you have a 4D setup? (same default zone number for every domain)

    Yes, well do you mean in binkd cfg where the outb is set? I have them all set as 1


    ----
    Regards,


    Rick Smith (Nitro)

    ... It was good BBSing with you @F
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (1:105/10.1)
  • From Oli@2:280/464.47 to Rick Smith on Mon May 3 12:40:31 2021
    Rick wrote (2021-05-02):

    So occasionally when I poll my bbs using binkd/hpt I get this
    error, it repeats my aka's then errors but if I poll again its
    fine? Any thoughts?

    addr: 1:105/10@fidonet (n/a or busy)
    + 20:48 [131872] addr: 21:1/190@fsxnet
    + 20:48 [131871] addr: 21:1/190@fsxnet (n/a or busy)
    + 20:48 [131871] addr: 77:1/130@scinet (n/a or busy)
    + 20:48 [131872] addr: 77:1/130@scinet
    + 20:48 [131872] addr: 46:10/136@agoranet (n/a or busy)
    + 20:48 [131871] addr: 46:10/136@agoranet
    + 20:48 [131871] addr: 44:100/28@dorenet (n/a or busy)
    + 20:48 [131872] addr: 44:100/28@dorenet
    ? 20:48 [131871] called 21:1/190@fsxnet, but remote has no such
    AKA + 20:48 [131871] done (to 21:1/190@fsxnet, failed, S/R: 0/0
    (0/0 bytes))

    do you have a 4D setup? (same default zone number for every domain)


    Yes, well do you mean in binkd cfg where the outb is set? I have them all set as 1

    I think I had similar issues with a 4D setup, but maybe your problem is unrelated.


    I looks like binkd start two polls in parallel. 131871 and 131872 are different process numbers. For one of the processes the node number is busy. The questions is why are there two parallel polls?

    ---
    * Origin: . (2:280/464.47)
  • From Tommi Koivula@2:221/360 to Rick Smith on Mon May 3 18:45:10 2021
    Hi Rick.

    03 May 21 12:40:30, Oli wrote to you:

    Rick wrote (2021-05-02):

    So occasionally when I poll my bbs using binkd/hpt I get this
    error, it repeats my aka's then errors but if I poll again its
    fine? Any thoughts?

    addr: 1:105/10@fidonet (n/a or busy)
    + 20:48 [131872] addr: 21:1/190@fsxnet
    + 20:48 [131871] addr: 21:1/190@fsxnet (n/a or busy)
    + 20:48 [131871] addr: 77:1/130@scinet (n/a or busy)
    + 20:48 [131872] addr: 77:1/130@scinet
    + 20:48 [131872] addr: 46:10/136@agoranet (n/a or busy)
    + 20:48 [131871] addr: 46:10/136@agoranet
    + 20:48 [131871] addr: 44:100/28@dorenet (n/a or busy)
    + 20:48 [131872] addr: 44:100/28@dorenet
    ? 20:48 [131871] called 21:1/190@fsxnet, but remote has no such
    AKA + 20:48 [131871] done (to 21:1/190@fsxnet, failed, S/R: 0/0
    (0/0 bytes))

    do you have a 4D setup? (same default zone number for every domain)


    Yes, well do you mean in binkd cfg where the outb is set? I have them all
    set as 1

    I think I had similar issues with a 4D setup, but maybe your problem is unrelated.


    I looks like binkd start two polls in parallel. 131871 and 131872 are different process
    numbers. For one of the processes the node number is busy. The questions is why are there two
    parallel polls?

    Setting "maxclients 1" might help.

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/360)
  • From Oli@2:280/464.47 to Tommi Koivula on Mon May 3 17:14:52 2021
    Tommi wrote (2021-05-03):

    I looks like binkd start two polls in parallel. 131871 and 131872
    are different process numbers. For one of the processes the node
    number is busy. The questions is why are there two parallel polls?

    Setting "maxclients 1" might help.

    but it would be only a workaround and doesn't fix the root cause of the problem.

    ---
    * Origin: . (2:280/464.47)
  • From Matthias Hertzog@2:301/1 to Oli on Mon May 3 18:19:57 2021
    Hello Oli!

    Setting "maxclients 1" might help.
    but it would be only a workaround and doesn't fix the root cause of
    the problem.

    True. Try to keep your outbound clear and always use the same address to poll a system.
    If you have automated polls to the same system, but it's othernet address, don's poll it in the same minute.

    That said, polling the same system to get othernet's mail makes no sense at all because the othernet's stuff will be transmitted during your fidonet poll.

    Therefore: Use a singe address to initiate polls and the problem will go away. Inspect your outbound and see what's causing the calls.

    Good luck
    Matthias
    --- GoldED+/W64-MSVC 1.1.5-b20180707
    * Origin: MHS Systems (2:301/1)
  • From Tommi Koivula@2:221/360 to Oli on Mon May 3 19:33:02 2021
    Hi Oli.

    03 May 21 17:14:52, you wrote to me:

    Tommi wrote (2021-05-03):

    I looks like binkd start two polls in parallel. 131871 and 131872
    are different process numbers. For one of the processes the node
    number is busy. The questions is why are there two parallel polls?

    Setting "maxclients 1" might help.

    but it would be only a workaround and doesn't fix the root cause of the problem.

    Of course.

    Investigating the BSO also might help. And running binkd with -vv :)

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/360)
  • From Oli@2:280/464.47 to Matthias Hertzog on Mon May 3 20:03:46 2021
    Matthias wrote (2021-05-03):

    Hello Oli!

    Setting "maxclients 1" might help.
    but it would be only a workaround and doesn't fix the root cause of
    the problem.

    True. Try to keep your outbound clear and always use the same address to poll a system. If you have automated polls to the same system, but it's othernet address, don's poll it in the same minute.

    That said, polling the same system to get othernet's mail makes no sense at all because the othernet's stuff will be transmitted during your fidonet poll.

    Therefore: Use a singe address to initiate polls and the problem will go away. Inspect your outbound and see what's causing the calls.

    This is not how BSO is supposed to work. The tosser creates flow files for all nodes that receive mails (files), the mailer does the polling and should be able to sort it out.

    I think we missed an important clue:

    ? 20:48 [131871] called 21:1/190@fsxnet, but remote has no such AKA

    We need a complete session log and/or the config file to see what's wrong.

    ---
    * Origin: . (2:280/464.47)
  • From Matthias Hertzog@2:301/1 to Oli on Tue May 4 10:56:48 2021
    Hello Oli!

    True. Try to keep your outbound clear and always use the same
    address to poll a system. If you have automated polls to the same
    system, but it's othernet address, don's poll it in the same
    minute.

    That said, polling the same system to get othernet's mail makes
    no sense at all because the othernet's stuff will be transmitted
    during your fidonet poll.

    Therefore: Use a singe address to initiate polls and the problem
    will go away. Inspect your outbound and see what's causing the
    calls.

    This is not how BSO is supposed to work. The tosser creates flow files
    for all nodes that receive mails (files), the mailer does the polling
    and should be able to sort it out.

    Oehm, i think BSO is exactly supposed to work like that. Only true within
    a single network, of course. Rule of thumb is: Only one outgoing file per destination system within the same network ... or at least all of them addressed to the same nodenumber - WITHIN the same network.

    Matthias
    --- GoldED+/W64-MSVC 1.1.5-b20180707
    * Origin: MHS Systems (2:301/1)