Hi g00r00

Need some help please. NET 2 HUB running Mystic 1.12 A37 Pre Build 17/12/13 16:16:02 has a *.bsy issue will mutil failing to import any packets building
up in echomail\in

I have run a fidopoll killbusy all process and then run mutil again but the probs persist. It seems to create the busy files when the process is run and does remove them after the fatal timeout some 60 secs later.

I then updated the HUB to the latest build 2017/12/15 15:26:35 and tried
again, but there the problem remains.

At this stage I am unable to process inbound/outbound echomail for the nodes attached to this HUB.

Worse case is that I may need to roll back to A36 but wanted to check in
first to see if there was anything I could do? Seems there are no busy logs
in the root dir now so can't offer anything there but will zip up the logs
from the last 24 or so hours and send them to you shortly via filebox.

This HUB is running windows 64 bit. And interesting when I call the -ver
switch I also see a Runtime error 2016 appear

[snip]

v1.12 A37 Windows/64

Compiled 2017/12/15 15:26:35
Runtime error 216 at $0000000100002069
$0000000100002069
$00000001000137A1
$00007FFC83D14CBD
$00007FFC83C8E465
$00000001000130AA
$0000000100002D0B
$0000000100004136
$0000000100012D13
$0000000100013811
$00007FFC83A21FE4
$00007FFC83CDEF91

[snip]

Best, Paul

--- Mystic BBS v1.12 A37 2017/12/15 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 12/17/17, Avon pondered and said...

Need some help please. NET 2 HUB running Mystic 1.12 A37 Pre Build 17/12/13 16:16:02 has a *.bsy issue will mutil failing to import any packets building up in echomail\in

[time passes]

OK I rolled back to A35 and then from a backup of the failed
installation I tossed the packets that were in the echomail\in directory that had got stuck. All working again.

I had created a two new echomail nodes prior to this issue occurring in the last 24 hours on NET2 and when I did my first restore back to A35 I copied
the echonode.dat file from the failed A37 that had locked up and copied the packets requiring tossing in to the echomail\in directory.

I hit the same *.bsy issue. So I am wondering if somehow there was an issue with the extra echonodes recently added? I was trying my luck to see if I
could just use the latest echonode.dat file to save having to re-enter the echonode added post update to A37 but it seems it did not work out.

So blew away the mystic dir and went with the complete restore of A35 and all is well... have since added in the couple of echonodes to A35.

Best, Paul

--- Mystic BBS v1.12 A37 2017/12/15 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 12/17/17, Avon pondered and said...

first to see if there was anything I could do? Seems there are no busy logs in the root dir now so can't offer anything there but will zip up
the logs from the last 24 or so hours and send them to you shortly via filebox.

In your filebox are x 2 zips of the logs from NET2 prior to and during the *.bsy issue.

Files are called

logbackup Sat 12-16-2017 2-30.zip
net2-logs.zip

First is the backup of logs taken from before the issue, the second is during the issue until I acted to fix.

Best, Paul

--- Mystic BBS v1.12 A37 2017/12/15 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Need some help please. NET 2 HUB running Mystic 1.12 A37 Pre Build

Update to the latest when you can please

--- Mystic BBS v1.12 A37 2017/12/16 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

issue with the extra echonodes recently added? I was trying my luck to
see if I could just use the latest echonode.dat file to save having to re-enter the echonode added post update to A37 but it seems it did not work out.

There shouldn't be any change to the format of that file, so they should be compatible between A37 and A35. Can you clarify what didn't work out?

--- Mystic BBS v1.12 A37 2017/12/16 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/16/17, g00r00 pondered and said...

Need some help please. NET 2 HUB running Mystic 1.12 A37 Pre Build

Update to the latest when you can please

Working on this now :) There's a few systems to work on these days..

--- Mystic BBS v1.12 A37 2017/12/16 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 12/16/17, g00r00 pondered and said...

issue with the extra echonodes recently added? I was trying my luck t see if I could just use the latest echonode.dat file to save having t re-enter the echonode added post update to A37 but it seems it did no work out.

There shouldn't be any change to the format of that file, so they should be compatible between A37 and A35. Can you clarify what didn't work out?

I was trying to toss some packets in echomail\in after reverting to A35 but using the A37 echonode.dat file. That .dat had a couple of new echonodes I
had added before A37 seemed to stop processing packets with the MUTIL *.bsy issue. So I copied it back over in to the A35 data dir and tried to run MUTIL but hit the same *.bsy errors.. so I wondered at the time if it was somehow related to the changes I had made in the echonode setup in A37 some 12+ hours earlier?

Not sure, but in any regard the 'latest' build has been applied across all
NETs now.. so we're back on the same playing field. And the *.bsy tracking is back which is good.

--- Mystic BBS v1.12 A37 2017/12/16 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Not sure, but in any regard the 'latest' build has been applied across
all NETs now.. so we're back on the same playing field. And the *.bsy tracking is back which is good.

Yep, unfortunately I haven't made any changes (at least knowingly) that would address any issues, but at least we should have some better logging.

--- Mystic BBS v1.12 A37 2017/12/16 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)