On 24 Oct 2021, Chris Hizny said the following...
CH> Howdy. Well, it happened again, but this time I got granular and preserved
CH> the problem file.
CH> Toss FDN/TIC Files 0 import, 0 toss, 0 hatch, 0 bad DONE 0.01s
CH> Importing EchoMail Importing 9FC80759.PKT (954:895/1 t WORKING
I also got a bad packet from 954:895/1:
----------------- MUTIL v1.12 A47 2021/09/29 Tue, Oct 19 2021 (loglevel 2)
+ Oct 19 19:06:18 Startup using mailin.ini
+ Oct 19 19:06:18 Process: Toss FDN/TIC Files
+ Oct 19 19:06:18 Waiting for BUSY nodes
+ Oct 19 19:06:18 Scanning Hatches
+ Oct 19 19:06:18 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.01s
+ Oct 19 19:06:18 Process: Importing EchoMail
+ Oct 19 19:06:18 Waiting for BUSY nodes
+ Oct 19 19:06:19 Extracting 512A62CA.TU1
+ Oct 19 19:06:19 Importing 90F59CDD.PKT (954:895/1 to 954:895/27)
+ Oct 19 19:06:19 Shutdown Corrupted memory (216)
Things started backing up after this as it said mutil was already running:
+ Oct 19 19:18:39 Results: Cannot import. Some nodes are BUSY in 60.09s
+ Oct 19 19:19:39 Results: Cannot import. Some nodes are BUSY in 60.10s
+ Oct 19 19:20:49 Results: Cannot import. Some nodes are BUSY in 60.08s
+ Oct 19 19:21:49 Results: Cannot import. Some nodes are BUSY in 60.09s
Moving 512A62CA.TU1 out of the way and runing ./mis poll killbusy allowed the
backlog to get processed.
Here's a copy of 512A62CA.TU1:
https://drive.google.com/file/d/1OUXGp6XSj9LZUUv9VhTrzfd9GW1aljUw/
Jay
... Yield to temptation, it may not pass your way again. - L. Long
--- Mystic BBS v1.12 A47 2021/09/29 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)
|
