Hello There,
Here is something I have noticed that has happened occasionally for awhile now >BBBS will get stuck in a continuous polling loop. It doesn't always involve th >same remote system or even the same FTN. This round of polling continued unti >I seen it happening and issued the command 'bbbs bom d 1:14/5'. Any thoughts o
what might be causing this behavior? It's like BBBS doesn't detect that the connection was completed and tries again and again and again. Or Mystic isn't expressing that the connection was completed and so BBBS retries. This also happened on previous versions of BBBS.
Here is something I have noticed that has happened occasionally for awhile no >>BBBS will get stuck in a continuous polling loop Or Mystic isn't
expressing that the connection was completed and so BBBS retries. This also >> happened on previous versions of BBBS.
I've seen this too, not continuous polling but I sometimes press <alt> p from
BBBS to poll a node and the poll will complete successfully but the poll isn't >removed so BBBS polls the node a second time. I see that at times when polling
a link running Mystic or binkd.
system. Currently last time it happened was with my Mystic 1:14/5 system and according
to the logs the next previous time was with Paul's 21:1/100 Mystic
system. In testing it
Jeff, just reaching out here. I can see problems with you polling the Z21 NET 1 HUB looks like no correct AKAs are being presented?
[snip]
+ 2019.03.14 18:23:54 BINKP > Connect on slot 1/25 (65.103.12.161)
+ 2019.03.14 18:23:54 BINKP 1-HostName Unknown
+ 2019.03.14 18:23:54 BINKP 1-S: NUL OPT CRAM-MD5-f66e688ea332a93cb8dbb22a174cf960
+ 2019.03.14 18:23:54 BINKP 1-S: NUL SYS fsxHUB Risa [NET1]
+ 2019.03.14 18:23:54 BINKP 1-S: NUL ZYZ Avon
+ 2019.03.14 18:23:54 BINKP 1-S: NUL TIME Thu, 14 Mar 2019 18:23:54 1300
+ 2019.03.14 18:23:54 BINKP 1-S: NUL VER Mystic/1.12A43 binkp/1.0
+ 2019.03.14 18:23:54 BINKP 1-S: NUL BUILD 2019/03/03 01:35:01 Windows/32
+ 2019.03.14 18:23:54 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet
This round of polling continued until I seen it happening and issued
the command 'bbbs bom d 1:14/5'.
190312 07:34 Region 14 IP Server, 1:14/5
190312 07:34 AKA: 1:14/0
This round of polling continued until I seen it happening and issued
the command 'bbbs bom d 1:14/5'.
Polling loop can happen if:
1) You have crashmail to nodenumber X, but remote doesn't present that nodenumber as primary / AKA.
2) Mail session is not fully completed and that poll message still exists.
If your above "bbbs bom d 1:14/5" helps then it's not case #1, as primary is 1:14/5.
Unfortunately BBBS doesn't log enough to see if it's case #2. Can you get debug
logs from remote site? Does it disconnect incoming connection for some reason?
Unfortunately BBBS doesn't log enough to see if it's case #2. Can you get debu >logs from remote site? Does it disconnect incoming connection for some reason?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,038 |
Nodes: | 15 (0 / 15) |
Uptime: | 43:51:22 |
Calls: | 500,199 |
Files: | 95,196 |
D/L today: |
117 files (8,763K bytes) |
Messages: | 465,892 |