I have had another repeat instance where MIS seems to have stopped accepting any incoming telnet or binkp sessions. The last logged binkp connection was at 22:32 last night and the last telnet session closed at 22:34

Thereafter nothing in the way of any binkp or telnet sessions. Other internal servers were unable to connect the the binkp system... the bbs.geek.nz
website when I tested it showed no reply from Mystic either.

So at 5:57 the following morning I shut down MIS, it took the full 60 secs to close,

+ 2018.01.10 05:57:49 MANAGER Server shutdown received from console
+ 2018.01.10 05:57:49 MANAGER Shutdown: EVENT
+ 2018.01.10 05:57:49 MANAGER Shutdown: TELNET
+ 2018.01.10 05:57:49 MANAGER Shutdown: BINKP
+ 2018.01.10 05:57:49 MANAGER Waiting for servers to stop (up to 60 seconds)
+ 2018.01.10 05:57:49 EVENT Event system stopped
+ 2018.01.10 05:58:51 MANAGER Shutdown complete

After restarting it, telnet and binkp were running again.... although for
how long I don't know. When this last happened a few days ago things stopped working again within 20-30 mins :(

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)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 01/10/18, Avon pondered and said...

I have had another repeat instance where MIS seems to have stopped accepting any incoming telnet or binkp sessions. The last logged binkp connection was at 22:32 last night and the last telnet session closed at 22:34

Thereafter nothing in the way of any binkp or telnet sessions. Other

It happened again within 30 minutes so I have rolled back the exe's to Mystic BBS v1.12 A37 compiled 2017/12/30 00:21:46

Will see what happens next :)

Best, Paul


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

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

I have had another repeat instance where MIS seems to have stopped accepting any incoming telnet or binkp sessions. The last logged binkp connection was at 22:32 last night and the last telnet session closed at 22:34

I've added some additional logging for any returned errors when a new connection is being listened for, or when a connection in the queue is being accepted. This will be in A39 whenever I can get it to a good place for pre-alpha.

--- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/10/18, g00r00 pondered and said...

I've added some additional logging for any returned errors when a new connection is being listened for, or when a connection in the queue is being accepted. This will be in A39 whenever I can get it to a good
place for pre-alpha.

Thanks. It must be something specific to my BBS setup / OS ver etc. Not sure. This issue is not appearing in any other install of A38 running on the same machine. It's got me a tad stumped as it's intermittent and appears to come
out of nowhere. Rolling back to the last A37 seems to be fine at the moment
but I'm watching it like a hake :)

Best, Paul


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

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

Thanks. It must be something specific to my BBS setup / OS ver etc. Not sure. This issue is not appearing in any other install of A38 running on the same machine. It's got me a tad stumped as it's intermittent and appears to come out of nowhere. Rolling back to the last A37 seems to be fine at the moment but I'm watching it like a hake :)

The problem with that is then you're also going back to the version that may have that intermittent crash. You just can't win! :(

The issue now is if I give you A39 it has record changes so downgrading
becomes increasingly difficult. I wanted to make sure A38 was stable before
I did the changes and for a week it seemed it was, go figure as soon as I
make the changes...

--- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/10/18, g00r00 pondered and said...

The problem with that is then you're also going back to the version that may have that intermittent crash. You just can't win! :(

The issue now is if I give you A39 it has record changes so downgrading becomes increasingly difficult. I wanted to make sure A38 was stable before I did the changes and for a week it seemed it was, go figure as soon as I make the changes...

Do you have a snapshot of A38 you could switch on the logging we see in the version of A37 I am running or is it beyond that now given you've worked on A39? I'm guessing beyond...

If so, well then the only way is to move forward I guess and I move to A39
like the rest of us, as and when you release something. And that's fine.
Given you're adding in some extra logging to try and catch something that may be a bit off with this one instance then I tend to think that's all we can do.

Best, Paul


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

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