Rick wrote (2021-05-02):

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

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

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


 RS> Yes, well do you mean in binkd cfg where the outb is set? I have them all
 RS> 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?

---