Hi all.

Had an interesting one tonight

[snip]

----------------- MUTIL v1.12 A39 2018/04/21 Wed, Aug 15 2018 (loglevel 3)
+ Aug 15 19:13:01 Startup using mailin.ini
- Aug 15 19:13:01 EXEC ImportEchoMail
- Aug 15 19:13:01 EXEC FileToss
+ Aug 15 19:13:01 Process: Toss FDN/TIC Files
+ Aug 15 19:13:01 Scanning Hatches
+ Aug 15 19:13:01 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.00s
+ Aug 15 19:13:01 Process: Importing EchoMail
+ Aug 15 19:13:01 Waiting for BUSY nodes
+ Aug 15 19:14:01 Results: Cannot import. Some nodes are BUSY in 60.01s
! Aug 15 19:14:01 Status: FATAL
+ Aug 15 19:14:01 Shutdown Normal (0)

----------------- MUTIL v1.12 A39 2018/04/21 Wed, Aug 15 2018 (loglevel 3)
+ Aug 15 19:15:41 Startup using mailin.ini
- Aug 15 19:15:41 EXEC ImportEchoMail
- Aug 15 19:15:41 EXEC FileToss
+ Aug 15 19:15:41 Process: Toss FDN/TIC Files
+ Aug 15 19:15:41 Scanning Hatches
+ Aug 15 19:15:41 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.00s
+ Aug 15 19:15:41 Process: Importing EchoMail
+ Aug 15 19:15:41 Waiting for BUSY nodes
+ Aug 15 19:16:41 Results: Cannot import. Some nodes are BUSY in 60.01s
! Aug 15 19:16:41 Status: FATAL
+ Aug 15 19:16:41 Shutdown Normal (0)

[snip]

Logs had been like that since earlier in the day.

Ran a Fidopoll killbusy all command and tried again...

[snip]

----------------- MUTIL v1.12 A39 2018/04/21 Wed, Aug 15 2018 (loglevel 3)
+ Aug 15 19:45:27 Startup using mailin.ini
- Aug 15 19:45:27 EXEC ImportEchoMail
- Aug 15 19:45:27 EXEC FileToss
+ Aug 15 19:45:27 Process: Toss FDN/TIC Files
+ Aug 15 19:45:27 Scanning Hatches
+ Aug 15 19:45:27 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.03s
+ Aug 15 19:45:27 Process: Importing EchoMail
+ Aug 15 19:45:27 Waiting for BUSY nodes
- Aug 15 19:45:27 LINKS:
- Aug 15 19:45:27 Node 14 3:770/1@fidonet
- Aug 15 19:45:27 Node 15 46:3/103@agoranet
- Aug 15 19:45:27 Node 16 39:970/0@amiganet
- Aug 15 19:45:27 Node 5 24:400/1@sportnet
- Aug 15 19:45:27 Node 7 21:1/100@fsxnet
- Aug 15 19:45:27 Node 9 44:100/0@dorenet
- Aug 15 19:45:27 Node 6 21:1/10@fsxnet
! Aug 15 19:45:27 Import from c:\bbs\mystic\echomail\in\
+ Aug 15 19:45:27 Extracting 986C82E9.WE0
- Aug 15 19:45:27 unzip -oqqjC c:\bbs\mystic\echomail\in\986C82E9.WE0
*.pkt -d c:\bbs\mystic\temputil\
+ Aug 15 19:45:27 Importing 9283EB81.PKT (46:3/103 to 46:3/203)
+ Aug 15 19:45:27 Shutdown Runtime error (217)

[snip]

On the front end it looked like this

[snip]

°°²ÛÛÛÛ ²ÜÜÜܲ ÛÛÛÛÛ ±Ý Þ°°°°°°°°°°°°°°°°°°°°°°°°°
50 ²
ÜÜþ ßß² ± °°²ÜÜÜÜÜÜܲÜÜÜÜÜÜÜÜÜÜܲ ÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜ ÜÜÜÜÜÜÜÜ Ü ÜÜÜÜÜÜÜ
ܲÛ
° mUTIL v1.12 Üß ß ßß ° ß
°
° ß ÜÜß mailin.ini (2/2)

Þ Process ÄÄÄÄÄÄÄÄÄÄÄÄÄ Ä Status ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Result ÄÄÄÄú
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄijÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄijÄÄÄÄÄÄÄÄÄÄÄÄ¿
Toss FDN/TIC Files 0 import, 0 toss, 0 hatch, 0 bad DONE 0.03s
An unhandled exception occurred at $00433E62:T (46:3/103 to WORKING EAccessViolation: Access violation
$00433E62
$00428AC1
$00428505
$00427D3D
$00402603ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
> Execution of 2 processes complete

[snip]

Checked the packet and it seemed 'experimental' from another Agoranet node... removed the packet, ran fidopoll killbusy all again and success..

[snip]

+ Aug 15 19:50:00 Results: 185 echo, 0 net, 0 dupes, 0 tossed in 4.35s
+ Aug 15 19:50:00 Shutdown Normal (0)

[snip]

I checked the packet and there must be something amiss in it... [g00r00 have kept it in case you want to have a look sometime when you're about next]

[snip]

MSGID: 46:1/190@agoranet 5b73b06c
PID: CNet 3.0
Here's a shot in the dark.. multi networks on Cnet/3 for Amiga, now to sort
out the rest :D

So.. this is a test
--- CNet/3
* Origin: idbbs.dlinkddns.com:2023 -- cnet/amiga (46:1/190)

[snip]

So Night Stalker .. for info... it seems like something may be amiss in the packet creation, and happy to filebox this one to you if it helps also.

Best, Paul

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

Dear Avon,

nothing uncommon on my side at 11:00 (prior Your FATAL report)...

+ Aug 15 11:00:18 Result 1
+ Aug 15 11:00:18 Compare FSXNET.040 2018 / FSXNET.040 2018
+ Aug 15 11:00:18 Result 2
+ Aug 15 11:00:18 Merging /u01/bbs/temputil/FSXNET.040
+ Aug 15 11:00:18 Results: Merged 1 of 1 nodelist(s) in 0.01s
+ Aug 15 11:00:18 Shutdown Normal (0)

But the mail processing afterwards (at my 12:00 ... Your 20:00)

There are some Uknown files reported

----------------- MUTIL v1.12 A38 2018/01/01 Wed, Aug 15 2018 (loglevel 3)

+ Aug 15 12:00:01 Startup using mutil.ini
- Aug 15 12:00:01 EXEC Import_MessageBase
- Aug 15 12:00:01 EXEC ExportEchoMail
- Aug 15 12:00:01 EXEC ImportEchoMail
- Aug 15 12:00:01 EXEC MergeNodeLists
- Aug 15 12:00:01 EXEC FileToss
+ Aug 15 12:00:01 Process: Toss FDN/TIC Files
+ Aug 15 12:00:01 Scanning Hatches
+ Aug 15 12:00:01 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.01s
+ Aug 15 12:00:01 Process: Importing EchoMail
+ Aug 15 12:00:01 Waiting for BUSY nodes
- Aug 15 12:00:01 LINKS:
- Aug 15 12:00:01 Node 2 21:1/10@fsxnet
! Aug 15 12:00:01 Import from /u01/bbs/echomail/in/
! Aug 15 12:00:01 Unknown inbound file BBS.1.CFG
! Aug 15 12:00:01 Unknown inbound file BBS.2.CFG
! Aug 15 12:00:01 Unknown inbound file BBS.3.CFG
! Aug 15 12:00:01 Unknown inbound file BBS.4.CFG
! Aug 15 12:00:01 Unknown inbound file BBS.CFG
! Aug 15 12:00:01 Unknown inbound file GDYNSRC.1.ZIP
! Aug 15 12:00:01 Unknown inbound file fsxinfo.1.zip
! Aug 15 12:00:01 Unknown inbound file BBS.5.CFG

... especially this is interesting and never seen that before

! Aug 15 12:00:01 Unknown inbound file 469B0103.GAL.BAD
! Aug 15 12:00:01 Unknown inbound file 4B390103.GAL.BAD
! Aug 15 12:00:01 Unknown inbound file 4B3C0103.GAL.BAD
! Aug 15 12:00:01 Unknown inbound file 4B720103.GAL.BAD
! Aug 15 12:00:01 Unknown inbound file BBS.6.CFG
! Aug 15 12:00:01 Unknown inbound file 4C600103.GAL.BAD
! Aug 15 12:00:01 Unknown inbound file GDYNSRC.ZIP
+ Aug 15 12:00:01 Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.02s
+ Aug 15 12:00:01 Process: Exporting EchoMail
+ Aug 15 12:00:01 Waiting for BUSY nodes
+ Aug 15 12:00:01 Scanning...
- Aug 15 12:00:01 LINKS:
- Aug 15 12:00:01 Node 2 21:1/10@fsxnet


... some bad files appeared on my system.

However the processing ended up O.K. and if You read this mail everything works as expected I think.

+ Aug 15 12:00:01 Compare FSXNET.040 2018 / FSXNET.040 2018

+ Aug 15 12:00:01 Result 2
+ Aug 15 12:00:01 Merging /u01/bbs/temputil/FSXNET.040
+ Aug 15 12:00:01 Results: Merged 1 of 1 nodelist(s) in 0.01s
+ Aug 15 12:00:01 Shutdown Normal (0)

Best regards from Fatal Echo

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Fatal Echo BBS (21:1/153)

Avon wrote:

Hi all.

Had an interesting one tonight

[snip]

----------------- MUTIL v1.12 A39 2018/04/21 Wed, Aug 15 2018 (loglevel 3) + Aug 15 19:13:01 Startup using mailin.ini
- Aug 15 19:13:01 EXEC ImportEchoMail
- Aug 15 19:13:01 EXEC FileToss
+ Aug 15 19:13:01 Process: Toss FDN/TIC Files
+ Aug 15 19:13:01 Scanning Hatches
+ Aug 15 19:13:01 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.00s
+ Aug 15 19:13:01 Process: Importing EchoMail
+ Aug 15 19:13:01 Waiting for BUSY nodes
+ Aug 15 19:14:01 Results: Cannot import. Some nodes are BUSY in 60.01s
! Aug 15 19:14:01 Status: FATAL
+ Aug 15 19:14:01 Shutdown Normal (0)

----------------- MUTIL v1.12 A39 2018/04/21 Wed, Aug 15 2018 (loglevel 3) + Aug 15 19:15:41 Startup using mailin.ini
- Aug 15 19:15:41 EXEC ImportEchoMail
- Aug 15 19:15:41 EXEC FileToss
+ Aug 15 19:15:41 Process: Toss FDN/TIC Files
+ Aug 15 19:15:41 Scanning Hatches
+ Aug 15 19:15:41 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.00s
+ Aug 15 19:15:41 Process: Importing EchoMail
+ Aug 15 19:15:41 Waiting for BUSY nodes
+ Aug 15 19:16:41 Results: Cannot import. Some nodes are BUSY in 60.01s
! Aug 15 19:16:41 Status: FATAL
+ Aug 15 19:16:41 Shutdown Normal (0)

[snip]

Logs had been like that since earlier in the day.

Ran a Fidopoll killbusy all command and tried again...

[snip]

----------------- MUTIL v1.12 A39 2018/04/21 Wed, Aug 15 2018 (loglevel 3) + Aug 15 19:45:27 Startup using mailin.ini
- Aug 15 19:45:27 EXEC ImportEchoMail
- Aug 15 19:45:27 EXEC FileToss
+ Aug 15 19:45:27 Process: Toss FDN/TIC Files
+ Aug 15 19:45:27 Scanning Hatches
+ Aug 15 19:45:27 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.03s
+ Aug 15 19:45:27 Process: Importing EchoMail
+ Aug 15 19:45:27 Waiting for BUSY nodes
- Aug 15 19:45:27 LINKS:
- Aug 15 19:45:27 Node 14 3:770/1@fidonet
- Aug 15 19:45:27 Node 15 46:3/103@agoranet
- Aug 15 19:45:27 Node 16 39:970/0@amiganet
- Aug 15 19:45:27 Node 5 24:400/1@sportnet
- Aug 15 19:45:27 Node 7 21:1/100@fsxnet
- Aug 15 19:45:27 Node 9 44:100/0@dorenet
- Aug 15 19:45:27 Node 6 21:1/10@fsxnet
! Aug 15 19:45:27 Import from c:\bbs\mystic\echomail\in\
+ Aug 15 19:45:27 Extracting 986C82E9.WE0
- Aug 15 19:45:27 unzip -oqqjC c:\bbs\mystic\echomail\in\986C82E9.WE0 *.pkt -d c:\bbs\mystic\temputil\
+ Aug 15 19:45:27 Importing 9283EB81.PKT (46:3/103 to 46:3/203)
+ Aug 15 19:45:27 Shutdown Runtime error (217)

Looks like I have a similar issue. I received 3 bad packets. So I guess
it's nothing for me to worry about.
--- SBBSecho 3.05-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

On 08/15/18, Avon said the following...

+ Aug 15 19:45:27 Importing 9283EB81.PKT (46:3/103 to 46:3/203)
+ Aug 15 19:45:27 Shutdown Runtime error (217)

I've come across this scenario before as well with Mystic. While I havent dumped the packet to see what field might be the cause (and didnt find a
packet dumping utility) - I put it down to my 1995 Ezycom - as it was a
netmail packet from it each time that caused Mystic to balk.

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)

On 08/15/18, Avon said the following...

Had an interesting one tonight

[snip]

That old message just went out for unknown reasons. I had looked at it yesterday, so maybe that had something to do with it - it got in the queue somehow. Just now I was working on that Vampire Snowman bot which hasn't been working much of the last two months. I made a couple of commands to make it, check it, and another to send it out. Before that I ran a poll and I think that's when the old 08/15/18 (US date format) went out. Seems it had been queued up and that poll sent it out, but I don't really know why it got
queued.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)