I'm currently trying to work out why there may be issues polling a system
running BinkD 1.1a-27/Win64 binkp/1.1

When I poll using my Mystic BBS I get the following

[snip]

Jan 06 19:49:43 FIDOPOLL Version 1.12 A38 2018/01/01
Jan 06 19:49:43 Scanning 21:1/158
Jan 06 19:49:43 Queued 73 files (268271346 bytes) to 21:1/158
Jan 06 19:49:43 Polling BINKP node 21:1/158 by IPV4
Jan 06 19:49:43 Connecting to starlight.altimit.nl
Jan 06 19:49:44 Connected
Jan 06 19:49:44 S: NUL SYS fsxHUB [fsxNet WHQ]
Jan 06 19:49:44 S: NUL ZYZ Paul Hayton
Jan 06 19:49:44 S: NUL VER Mystic/1.12A38 binkp/1.0
Jan 06 19:49:44 S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet
21:1/0@fsxnet 21:0/0@fsxnet
Jan 06 19:49:45 C: NUL OPT CRAM-MD5-95c9157f3809df6d75e119bf4116faee
Jan 06 19:49:45 C: NUL SYS Starlight
Jan 06 19:49:45 System Starlight
Jan 06 19:49:45 C: NUL ZYZ Lars van Dijk
Jan 06 19:49:45 SysOp Lars van Dijk
Jan 06 19:49:45 C: NUL LOC Beek en Donk
Jan 06 19:49:45 Location Beek en Donk
Jan 06 19:49:45 C: NUL NDL 115200,TCP,BINKP
Jan 06 19:49:45 Info NDL 115200,TCP,BINKP
Jan 06 19:49:45 C: NUL TIME Sat,  6 Jan 2018 07:49:54 +0100
Jan 06 19:49:45 Info TIME Sat,  6 Jan 2018 07:49:54 +0100
Jan 06 19:49:45 C: NUL VER binkd/1.1a-27/Win64 binkp/1.1
Jan 06 19:49:45 Mailer binkd/1.1a-27/Win64 binkp/1.1
Jan 06 19:49:45 C: ADR  2:280/2020@fidonet 21:1/158@fsxnet
Jan 06 19:49:45 S: PWD
Jan 06 19:49:45 C: BSY Secure AKA 21:1/100@fsxnet busy
Jan 06 19:49:45 Authorization failed

[snip]

Earlier logs sent to me by Lars show this sort of thing at his end.

[snip]

- 25 Dec 09:20:39 [3404] incoming from 219.89.83.33 (58904)
  25 Dec 09:20:39 [3404] started server #2, id=500
  25 Dec 09:20:39 [3456] binkp init done, socket # is 580
+ 25 Dec 09:20:39 [3456] incoming session with 219-89-83-33.adsl.xtra.co.nz
[219.89.83.33]
  25 Dec 09:20:39 [3456] send message NUL OPT
CRAM-MD5-eec921f5739d64f825eb22d47b8f18ee
  25 Dec 09:20:39 [3456] send message NUL SYS Starlight
  25 Dec 09:20:39 [3456] send message NUL ZYZ Lars van Dijk
  25 Dec 09:20:39 [3456] send message NUL LOC Beek en Donk
  25 Dec 09:20:39 [3456] send message NUL NDL 115200,TCP,BINKP
  25 Dec 09:20:39 [3456] send message NUL TIME Mon, 25 Dec 2017 09:20:39 +0100
  25 Dec 09:20:39 [3456] send message NUL VER binkd/1.1a-27/Win64 binkp/1.1
  25 Dec 09:20:39 [3456] send message ADR  2:280/2020@fidonet 21:1/158@fsxnet
  25 Dec 09:20:39 [3456] rcvd msg NUL SYS fsxHUB [fsxNet WHQ]
- 25 Dec 09:20:39 [3456] SYS fsxHUB [fsxNet WHQ]
  25 Dec 09:20:39 [3456] rcvd msg NUL ZYZ Paul Hayton
- 25 Dec 09:20:39 [3456] ZYZ Paul Hayton
  25 Dec 09:20:39 [3456] rcvd msg NUL VER Mystic/1.12A37 binkp/1.0
- 25 Dec 09:20:39 [3456] VER Mystic/1.12A37 binkp/1.0
  25 Dec 09:20:39 [3456] remote uses binkp v.1.0
  25 Dec 09:20:39 [3456] rcvd msg ADR 21:1/100@fsxnet 21:1/3@fsxnet
21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
  25 Dec 09:20:39 [3456] Can't create c:/fidonet/binkd/ftn\outb\00010064.bsy:
File exists
+ 25 Dec 09:20:39 [3456] addr: 21:1/100@fsxnet (n/a or busy)
? 25 Dec 09:20:39 [3456] Secure AKA 21:1/100@fsxnet busy, drop the session
  25 Dec 09:20:39 [3456] send message BSY Secure AKA 21:1/100@fsxnet busy
+ 25 Dec 09:20:39 [3456] done (?, failed, S/R: 0/0 (0/0 bytes))
  25 Dec 09:20:39 [3456] processing kill list
  25 Dec 09:20:39 [3456] binkp deinit done...
  25 Dec 09:20:39 [3456] session closed, quitting...
  25 Dec 09:20:39 [3456] downing server...


[snip]

Lars suspected it may be a permissions thing at his end with respect how busy
semaphores are being created and perhaps not removed correctly?

This from a recent email.

[snip]

Hi Paul,

I just did:

Polling:

C:\FidoNet\BinkD>binkd64.exe -p -P 21:1/100 binkd.cfg
$ -d 21:1/100@fsxnet    busy
  14:48 [4952] idle

outbox contains:
01-01-2018  14:48              .
01-01-2018  14:48              ..
01-01-2018  14:44                 6 00000000.bsy
01-01-2018  14:44                 6 00010000.bsy
01-01-2018  14:44                 6 00010002.bsy
01-01-2018  14:44                 6 00010003.bsy
01-01-2018  14:44                 6 00010064.bsy
01-01-2018  14:48                 0 00010064.dlo
27-12-2017  13:45                16 0118138b.try


even when the service is stopped.

All files contain "768" except the last one which reads:
"   
CONNECT/BND"

I doubt you find anything in the logs. If you like I could remove the bsy
files and try again.

[snip]

Does anyone have any thoughts?

I'm 99% sure we're fine for session password details and he's flying the
correct AKA for his fsxNet node.

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)