Hello g00r00,

I have a situation. Very frequently when Mutil is run either from an event or from the command-line to import mail. Mutil will fail to run claiming that "Some nodes are BUSY" When in fact there isn't any activity on any nodes. I
can issue the command to kill all busy but it doesn't change how Mutil responds.


----------------- MUTIL v1.12 A37 2017/12/30 Sun, Dec 31 2017 (loglevel 3)
+ Dec 31 03:02:06 Startup using mailin.ini
- Dec 31 03:02:06 EXEC ImportEchoMail
+ Dec 31 03:02:06 Process: Importing EchoMail
+ Dec 31 03:02:06 Waiting for BUSY nodes
+ Dec 31 03:03:06 Results: Cannot import. Some nodes are BUSY in 60.07s
! Dec 31 03:03:06 Status: FATAL
+ Dec 31 03:03:06 Shutdown Normal (0)

I also noticed something that may not be related and that is I recently
changed the uplink/downlink arrangement for Mystic. Mystic now feeds several Fsxnet point AKA's where it didn't before. I mention this because I see this behavior when Mystic is feeding a point AKA and not a node AKA.

In checking I see that when Fidopoll is run a .bsy file is created in the "/home/mystic/echomail/out/fsxnet.015/00010080.pnt" directory. And is
promptly removed when Fidopoll exits.

When I run Mutil manually from the commandline there are no nodes active and
no .bsy files in the /home/mystic/semaphore directory.

I have looked everywhere that I can think of for a reason that Mutil would think that one or more nodes are busy. As I have manny times said I am certainly not above missing the simple things sometimes.




Jeff

--- Mystic BBS v1.12 A37 2017/12/30 (Linux/64)
* Origin: The Ouijaboard II (21:1/128)

Any chat files in the data dir?

On 21:52 30/12 , Jeffs wrote:

Hello g00r00,

I have a situation. Very frequently when Mutil is run either from an event or >from the command-line to import mail. Mutil will fail to run claiming that >"Some nodes are BUSY" When in fact there isn't any activity on any nodes. I >can issue the command to kill all busy but it doesn't change how Mutil >responds.

----------------- MUTIL v1.12 A37 2017/12/30 Sun, Dec 31 2017 (loglevel 3)
+ Dec 31 03:02:06 Startup using mailin.ini
- Dec 31 03:02:06 EXEC ImportEchoMail
+ Dec 31 03:02:06 Process: Importing EchoMail
+ Dec 31 03:02:06 Waiting for BUSY nodes
+ Dec 31 03:03:06 Results: Cannot import. Some nodes are BUSY in 60.07s
! Dec 31 03:03:06 Status: FATAL
+ Dec 31 03:03:06 Shutdown Normal (0)

I also noticed something that may not be related and that is I recently >changed the uplink/downlink arrangement for Mystic. Mystic now feeds several >Fsxnet point AKA's where it didn't before. I mention this because I see this >behavior when Mystic is feeding a point AKA and not a node AKA.

In checking I see that when Fidopoll is run a .bsy file is created in the >"/home/mystic/echomail/out/fsxnet.015/00010080.pnt" directory. And is >promptly removed when Fidopoll exits.

When I run Mutil manually from the commandline there are no nodes active and >no .bsy files in the /home/mystic/semaphore directory.

I have looked everywhere that I can think of for a reason that Mutil would >think that one or more nodes are busy. As I have manny times said I am >certainly not above missing the simple things sometimes.

Jeff

--- Mystic BBS v1.12 A37 2017/12/30 (Linux/64)
* Origin: The Ouijaboard II (21:1/128)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/31 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

On 12/31/17, Jeffs said the following...

I have a situation. Very frequently when Mutil is run either from an
event or from the command-line to import mail. Mutil will fail to run claiming that "Some nodes are BUSY" When in fact there isn't any
activity on any nodes. I can issue the command to kill all busy but it doesn't change how Mutil responds.

In checking I see that when Fidopoll is run a .bsy file is created in the "/home/mystic/echomail/out/fsxnet.015/00010080.pnt" directory. And is promptly removed when Fidopoll exits.

I found that when I renamed the 00010080.pnt directory to 00010080.pnt-old
and then executed Mutil to process incoming mail. Mutil created a new 00010080.pnt directory. Then Mutil proceded to toss some 1148 echomail
messages that were waiting to be processed.

Is the existence of the 00010080.pnt directory a static existence or is it created and removed as needed for mail destined for point nodes?

As I recall BBBS creates/removes such directories as needed. That would also explain why I didn't notice this before as this is the first time that Mystic here has had point AKA's that it tosses echomail to.

That would raise another question. If mail for a point downlink is set to "Hold" status. Wouldn't the directory and the waiting packets inside sit
until the point system picks up the mail?

I noticed previously that when Mutil failed to run due to busy nodes there were no .bsy files in the .pnt directory. Does Mutil look at the pre-existence of the .pnt directory or the .pkt files inside as "Nodes are busy" status?




Jeff

--- Mystic BBS v1.12 A37 2017/12/30 (Linux/64)
* Origin: The Ouijaboard II (21:1/128)

I have looked everywhere that I can think of for a reason that Mutil
would think that one or more nodes are busy. As I have manny times said
I am certainly not above missing the simple things sometimes.

Did you look in the log that logs the busy files? busylog.txt ? You should see a history of every file that is created and removed and what utility does it.

If there is a BUSY issue you are guaranteed to see it there. I am aware of
no busy issues, outside of those created by the users themselves at the
moment.

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

When I run Mutil manually from the commandline there are no nodes active and no .bsy files in the /home/mystic/semaphore directory.

Binkley busy files are not created in Mystic's semaphore directory, they are maintained within the BSO directory structure, so that might be some of the confusion.

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

Hello g00r00,

On 12/31/17, g00r00 said the following...

When I run Mutil manually from the commandline there are no nodes act and no .bsy files in the /home/mystic/semaphore directory.

Binkley busy files are not created in Mystic's semaphore directory, they are maintained within the BSO directory structure, so that might be some of the confusion.

To test an idea that I had I removed the two point downlinks that my Nystic had and the Mutil busy node issue stopped. Not sure why the existance of the .pnt directory or it contents would cause Mutil think that nodes were busy.

Before, I had BBBS get the FSXNET mail and feed the Mystic installs here as FSXNET points. Which worked fine and I never had the node busy issue with that arangement. The busy node issue first showed up as soon as Mystic started feeding mail to point AKA's




Jeff

--- Mystic BBS v1.12 A37 2017/12/31 (Linux/64)
* Origin: The Ouijaboard II (21:1/128)

To test an idea that I had I removed the two point downlinks that my Nystic had and the Mutil busy node issue stopped. Not sure why the existance of the .pnt directory or it contents would cause Mutil think that nodes were busy.

Well for starters is sounds like Mystic couldn't access the previous point directory (before you renamed it). But as I said if there is a BUSY conflict it will be very clearly documented in the busylog.

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

Hello g00r00,

On 01/01/18, g00r00 said the following...

Well for starters is sounds like Mystic couldn't access the previous
point directory (before you renamed it).

Since the directory was created by Mystic I don't understand why it would
have trouble accessing it. As soon as I renamed the .pnt directory Mystic (Mutil) created a new directory of the same name.

But as I said if there is a
BUSY conflict it will be very clearly documented in the busylog.

In doing a grep of the busylog.txt for "MUTIL FAILED TO" I see the reponses start on December 12 and continue until December 31. The first and last responses are:

4:Nov 29 22:26:46 MUTIL FAILED TO CREATE (2):
/home/mystic/echomail/out/fidonet.001/011a0407.bsy
2169:Dec 12 11:11:08 MUTIL FAILED TO CREATE (2):
/home/mystic/echomail/out/fsxnet.015/00010080.pnt/00000001.bsy
2172:Dec 12 11:11:08 MUTIL FAILED TO CREATE (2):
/home/mystic/echomail/out/fsxnet.015/00010080.pnt/00000002.bsy

17182:Dec 31 02:58:10 MUTIL FAILED TO REMOVE (4294967295):
/home/mystic/echomail/out/fsxnet.015/00010064.bsy
17762:Dec 31 14:03:38 MUTIL FAILED TO REMOVE (4294967295):
/home/mystic/echomail/out/fsxnet.015/00010064.bsy
17769:Dec 31 14:04:42 MUTIL FAILED TO REMOVE (4294967295):
/home/mystic/echomail/out/fsxnet.015/00010064.bsy
18015:Dec 31 18:58:57 MUTIL FAILED TO REMOVE (4294967295):
/home/mystic/echomail/out/fsxnet.015/00010064.bsy
18021:Dec 31 18:59:47 MUTIL FAILED TO CREATE (2):
/home/mystic/echomail/out/fsxnet.015/00010080.pnt/00000003.bsy

Other than my renaming of the .pnt directory. I had made no changes, creations, or deletions to the outbound directory structure.




Jeff

--- Mystic BBS v1.12 A37 2017/12/31 (Linux/64)
* Origin: The Ouijaboard II (21:1/128)