Hello g00r00,



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 the same remote system or even the same FTN. This round of polling continued until I seen it happening and issued the command 'bbbs bom d
1:14/5'. Any thoughts on 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.

190312 07:34 Calling The Twisted Balloon, ftn.region14.org
190312 07:34 CONNECT 57600/RAW
190312 07:34 BinkP mail session
190312 07:34 Region 14 IP Server, 1:14/5
190312 07:34 AKA: 1:14/0
190312 07:34 SysOp: Jeff Smith
190312 07:34 From: Anoka, MN, USA
190312 07:34 Using: binkd/1.0.4/Linux binkp/1.1
190312 07:34 Flags: 115200,TCP,BINKP
190312 07:34 Mail session completed
190312 07:34 --------------------------

[...] Another 32 consecutive and continuous polls

190312 07:37 --------------------------
190312 07:37 Calling The Twisted Balloon, ftn.region14.org
190312 07:37 CONNECT 57600/RAW
190312 07:37 BinkP mail session
190312 07:37 Region 14 IP Server, 1:14/5
190312 07:37 AKA: 1:14/0
190312 07:37 SysOp: Jeff Smith
190312 07:37 From: Anoka, MN, USA
190312 07:37 Using: binkd/1.0.4/Linux binkp/1.1
190312 07:37 Flags: 115200,TCP,BINKP
190312 07:37 Mail session completed

The above was posted in the Fido BBBS support echo. I thought it
only right also post it here. Upon further checking it looks to only
occur when BBBS is connecting to a Mystic system. And then only when
BBBS initiates the poll to a Mystic system. But not if Mystic initiates
a poll to the BBBS system. I am still looking into the situation and will provide what info that I find. The current Mystic version in use is
1.12 A43 2019/03/02 although the same behavior was seen with previous
version of Mystic as well as previous versions of BBBS.





Jeff.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Fsxnet: The Twisted Ba (21:1/128)

On 12 Mar 2019 at 10:42p, Jeffs pondered and said...

190312 07:34 Flags: 115200,TCP,BINKP
190312 07:34 Mail session completed
190312 07:34 --------------------------

[...] Another 32 consecutive and continuous polls

190312 07:37 --------------------------
190312 07:37 Calling The Twisted Balloon, ftn.region14.org

what would be helpful would be to see some of the BinkP logging at the Mystic end.. If I understand you right your BBBS system keeps on polling the same Mystic system.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

'bbbs bom d 1:14/5'. Any thoughts on 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.

I would have to see the Mystic log but I think this was something BBBS has always struggled with? I think I looked into a long time ago but I can't remember what it was.

190312 07:34 Flags: 115200,TCP,BINKP
190312 07:34 Mail session completed

From your own log though it looks like BBBS is saying the session was completed. Are you able to get a log from the system its connecting to? Mystic logs the entire BINKP session to the log.

It could also be that you are blocked from the server you're trying to
connect to.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Sector 7 (21:1/108)