Subj : Busy? To : Tony Langdon From : Jeff Smith Date : Wed Jul 17 2019 11:08 pm Hello Tony! 18 Jul 19 07:56, you wrote to me: TL> -=> On 07-16-19 16:40, Jeff Smith wrote to All <=- JS>> Of late I have been having an issue with "All nodes Busy" or busy JS>> files that keep Fidopoll or Mutil from running. Last weekend I JS>> was away and when I got home I found that Mystic hadn't polled JS>> out in a couple days. I had assumed that Mutil and/or Fidopoll JS>> would normally remove the busy file upon program termination. TL> I'm curious, what version of Mystic? Mystic v1.12 A43 2019/03/02 TL> I know there were versions a TL> while ago that had semaphore issues, but the latest (latest is 1.12 TL> A43) few versions have no issues in this regard. Also, this assumes a TL> clean shutdown of Mystic and its utilities at all times. My Mystic TL> FTN hub runs pretty much hands off these days, and no file locking TL> issues. TL> It's also possible, though I haven't seen it, that Fidopoll is TL> crashing in the middle of doing something. What do your logs say - is TL> there any sign of an incomplete session, just before things go pear TL> shaped? As I said, I haven't seen any stability issues with Mystic or TL> its utilities, but just covering all bases. The error log shows: 2019.16.07 14:04:48 MUTIL 000 Runtime error 1 The Fidopoll log shows: Jul 12 04:59:03 Connecting to bbs.ouijabrd.net Jul 12 04:59:03 Using address 65.103.12.161 Jul 12 04:59:03 Connected IPV4 to 65.103.12.161 Jul 12 04:59:03 S: NUL SYS Region 14 IP Server Jul 12 04:59:03 S: NUL ZYZ Jeff Smith Jul 12 04:59:03 S: NUL TIME Fri, 12 Jul 2019 04:59:03 -0500 The above execution looks to have failed to complete. And there are no log entries after the above 7/12 entry until the 7/16 entry when I manually cleared the existing busy files. Jul 16 13:57:37 FIDOPOLL Version 1.12 A43 2019/03/02 Jul 16 13:57:37 Looking up address "1:261/38" in nodelist Jul 16 13:57:37 Scanning 1:261/38 Jul 16 13:57:37 Queued 0 files (0 bytes) to 1:261/38 In the Mutil log I get the following log entry times 100 during the same 7/12-7/16 time period: ----------------- MUTIL v1.12 A43 2019/03/02 Fri, Jul 12 2019 (loglevel 2) + Jul 12 05:08:43 Startup using import.ini + Jul 12 05:08:43 Process: Importing EchoMail + Jul 12 05:08:43 Waiting for BUSY nodes + Jul 12 05:09:43 Results: Cannot import. Some nodes are BUSY in 60.07s ! Jul 12 05:09:43 Status: FATAL + Jul 12 05:09:43 Shutdown Normal (0) Once I made sure no Mystic executables were loaded (Except for MIS) I cleared the busy files and Fidopoll loaded and polled out fine and then called Mutil fine. I checked to make sure I didn't have any events or tasks that might have caused an overlapping issue. Jeff --- GoldED+/LNX 1.1.5-b20170303 * Origin: Region 14 IP Server - ftn.region14.org (1:14/5) .