Subj : A47 System won't poll / Runtime error 216 To : All From : Chris Hizny Date : Tue Sep 28 2021 09:11 am This was a problem for me on A46. I had hoped an upgrade to A47 would make a difference and it doesn't appear to. 2021.28.09 16:00:10 MUTIL 000 Runtime error 216 What is this? The effect is the same when I stop and restart mis and the poll jobs (about every 5 minutes, one for each network) runs. The first poll will work okay, but then subsequently every poll fails: + 2021.09.28 16:00:07 1-Connecting to net1.fsxnet.nz on port 24556 + 2021.09.28 16:00:07 1-Using address 219.89.83.33 + 2021.09.28 16:00:08 1-Connected by IPV4 to 219.89.83.33 + 2021.09.28 16:00:08 1-System Agency + Risa HUB + 2021.09.28 16:00:08 1-SysOp Paul Hayton + 2021.09.28 16:00:08 1-Location Dunedin, New Zealand + 2021.09.28 16:00:08 1-Mailer binkd/1.1a-112/Linux binkp/1.1 + 2021.09.28 16:00:08 1-Receiving: 53397b12.we0 (849 bytes) + 2021.09.28 16:00:09 1-Session ended (0 sent, 1 rcvd, 0 skip) + 2021.09.28 16:00:10 Polled 1 systems --------------------- POLL v1.12 A47 2021/09/24 Tue, Sep 28 2021 (loglevel 1) + 2021.09.28 16:05:07 Poll BINKP node via address lookup: 21:1/10 + 2021.09.28 16:05:09 Polled 0 systems (all subsequent polls will show "Polled 0 systems"). It doesn't appear to be one network. Depending on what part of the hour it is, it will always poll whatever network is scheduled correctly once, and then fail for all subsequent ones. I do not know if this is normal or not, but the other thing that happens is .bsy files appear in a whole bunch of my echomail/out folders: mystic@shibboleths:/mystic$ find . -name *.bsy ../echomail/out/fidonet.001/00da02bc.bsy ../echomail/out/agoranet.02e/0001009c.bsy ../echomail/out/tqwnet.539/00030064.bsy ../echomail/out/micronet.26a/012c0001.bsy ../echomail/out/spooknet.2bc/00640000.bsy ../echomail/out/primary/00010064.bsy ../echomail/out/primary/0001000a.bsy ../echomail/out/metronet.019/00190000.bsy ../echomail/out/weednet.1a4/00020001.bsy ../semaphore/mutil.bsy ../semaphore/mis.bsy Note also that mutil.bsy stays there even though mis is not running between polls; I assume this runtime error causes it to die before it can remove that file. The mutil.log file shows this: + Sep 28 16:10:25 Waiting for BUSY nodes + Sep 28 16:11:25 Results: Cannot import. Some nodes are BUSY in 60.06s ! Sep 28 16:11:25 Status: FATAL + Sep 28 16:11:25 Process: Importing EchoMail + Sep 28 16:11:25 Waiting for BUSY nodes + Sep 28 16:12:25 Results: Cannot import. Some nodes are BUSY in 60.06s ! Sep 28 16:12:25 Status: FATAL + Sep 28 16:12:25 Process: Merging Nodelists + Sep 28 16:12:25 Results: Merged 0 of 0 nodelist(s) in 0.00s + Sep 28 16:12:25 Shutdown Normal (0) Currently dead in the water and unsure how to proceed. --- Mystic BBS v1.12 A47 2021/08/29 (Raspberry Pi/32) * Origin: 2o fOr beeRS bbS>>20ForBeers.com:1337 (1:105/420) .