Hello all, I am having a weird issue. I run both a BBS and network hub with latest version of Mystic. On the Hub system when MUTIL is ran is stays stuck waiting on busy nodes and never continues. I had to write a small script that does Fidopoll Kilbusy All every 10 seconds and then
this lets mutil continue. Any idea what may be wrong? Thanks.

__ _ _ __ _ __ _ ____ . _ _ __

I've been having the same issue and also just added a small script, and
run as an hourly event, to fidopoll killbusy then poll each of my
networks, however I don't run a hub and don't have to do so every 10
seconds. I noticed the issue started as more people began upgrading to
.46; I'm still on .45 .. I had not had this problem prior. I have not
delve into that upgrade yet, and admittedly just quick scanned the
"whats new," and it appears a lot of changes to MIS have occurred ..
gr00r00 would be an obvious better source of info ... but it appears a
lot of back end development occurred on the new version .. I'm pretty
excited to get it up and running, but .... scared to death to dive into
it at the moment. I literally am just finishing all of my
customization.

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Hello all, I am having a weird issue. I run both a BBS and network with latest version of Mystic. On the Hub system when MUTIL is ran i stays stuck waiting on busy nodes and never continues. I had to writ small script that does Fidopoll Kilbusy All every 10 seconds and then

You may be experiencing the same issue I am. I have my echomail folder that gets XXXX.bsy flags put into it on occassion which never lets mutil/fidopoll run until they are gone. So instead of killall, I just run:
"find . -name *.bsy -exec rm {} \;"
To purge the bsy flags. I don't know what causes them to hang up but it's
been happening since A45. I attributed it to my Fidonet uplink being slow and causing hangs. But not I"m not so sure.

Analog

|20|15┌─|16|08┤ |08De|07ad|15be|07a|08tz b|07b|15s
|08└─┘├─┐ |08:>.|07A|08rk |0710|08:|07101|08/|0714|08.
|04■ |08└|20|15─|16|08┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|04A|07n|15al|07o|08g |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|04.|08dPR|04. |08:>.|15S|07ci |1577|08:|151|08/|15131|08. |04░▒░|08▒██▄▌|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

You may be experiencing the same issue I am. I have my echomail folder that gets XXXX.bsy flags put into it on occassion which never lets mutil/fidopoll run until they are gone. So instead of killall, I just
run: "find . -name *.bsy -exec rm {} \;"
To purge the bsy flags. I don't know what causes them to hang up but it's been happening since A45. I attributed it to my Fidonet uplink being
slow and causing hangs. But not I"m not so sure.

You're running linux or windows? I never got the error until others
started running .46 .. but maybe I just didn't have enough networks at
the time to create the error. hmm... it's working as I have it set up.
Once I brave the upgrade (hopefully I don't lose much config) the
problem will go away :)

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Re: Re: MUTIL
By: The Godfather to Analog on Tue Aug 11 2020 08:58 am

You're running linux or windows? I never got the error until others started running .46 .. but maybe I just didn't have enough networks at
the time to create the error. hmm... it's working as I have it set up. Once I brave the upgrade (hopefully I don't lose much config) the
problem will go away :)

Are you talking about the issue of mutil not tossing mail/files because of errant busy files?

This has been an issue since early in the A45 time frame, 2016 or so. It has happened to me also although not often. I have never been able to come to any conclusion as to why it happens but the only solution is to shutdown mis and run the killbusy commands.

g00r00 is aware and has this in mind and I'm certain we will get passed it at some point. I had to run the killbusy command on my up to date A46 install not long ago.

The fix will likely be easy but figuring out just what the problem is may not be.

Ttyl :-),
Al

... An Elephant; A Mouse built to government specifications.
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Are you talking about the issue of mutil not tossing mail/files because
of errant busy files?

Yes, specifically half way through polling networks, they all start
showing up "busy" and being skipped. Then mutil spits an error out
saying that mutil is busy. So .. I fidopoll killbusy, and the problem
clears for a while. Now I run a batch file to clear it out prior to
each poll.

This has been an issue since early in the A45 time frame, 2016 or so. It has happened to me also although not often. I have never been able to
come to any conclusion as to why it happens but the only solution is to shutdown mis and run the killbusy commands.

I was unaware as I've only been running Mystic since March/April, and
the problem only began to occur once I added a 5th network (which was
around the time people were conversing about trouble shooting their .46 installs). So glad to know it's already been discussed and people much
better with back end programming are on it.

thx,

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Re: Re: MUTIL
By: The Godfather to Al on Tue Aug 11 2020 06:15 pm

Yes, specifically half way through polling networks, they all start showing up "busy" and being skipped. Then mutil spits an error out
saying that mutil is busy. So .. I fidopoll killbusy, and the problem clears for a while. Now I run a batch file to clear it out prior to
each poll.

It can be kind of a kiss in the petunia, I know.

Clearing the busy files manually could cause unexpected results. g00r00's advice has been to shutdown mis and issue the killbusy commands so that's the way I would do it.

Ttyl :-),
Al

... Do it! It's easier to get forgiveness than permission.
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 10 Aug 2020, The Godfather said the following...

Hello all, I am having a weird issue. I run both a BBS and network with latest version of Mystic. On the Hub system when MUTIL is ran i stays stuck waiting on busy nodes and never continues. I had to writ small script that does Fidopoll Kilbusy All every 10 seconds and then this lets mutil continue. Any idea what may be wrong? Thanks.

__ _ _ __ _ __ _ ____ . _ _ __

I've been having the same issue and also just added a small script, and run as an hourly event, to fidopoll killbusy then poll each of my networks, however I don't run a hub and don't have to do so every 10 seconds. I noticed the issue started as more people began upgrading to .46; I'm still on .45 .. I had not had this problem prior. I have not delve into that upgrade yet, and admittedly just quick scanned the
"whats new," and it appears a lot of changes to MIS have occurred .. gr00r00 would be an obvious better source of info ... but it appears a
lot of back end development occurred on the new version .. I'm pretty excited to get it up and running, but .... scared to death to dive into
it at the moment. I literally am just finishing all of my
customization.

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

I have been noticing the same issue and I know that some of the nodes it
throws off are not busy. I have not dug into this any deeper other than to note that this happens on both my A46 and A45 Systems and has been going on
for some time.

It seems that once a "busy" node is encountered, all nodes that are polled after are also "busy". They can be polled individually or if you just wait a few minutes the issue seems to resolve itself.

- Mike

--- Mystic BBS v1.12 A46 2020/08/10 (Linux/64)
* Origin: Arcadia BBS | Connecticut USA | bbs.arcadiabbs.com (21:3/107)

Clearing the busy files manually could cause unexpected results. g00r00's advice has been to shutdown mis and issue the killbusy commands so
that's the way I would do it.

Thanks for the heads up, switched that over right after reading your
reply! I'll trust the experts suggestions over my own fixes any time :)

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

It seems that once a "busy" node is encountered, all nodes that are polled after are also "busy". They can be polled individually or if you just wait a few minutes the issue seems to resolve itself.

Thanks Mike. I had been polling individually, however once I got past
(I think) 5 networks on my system .. the event editor started acting
wonky. I would set up a new network to poll at a specific time, exit
config, and a day later would not see any messages coming through. I'd
load event editor, and sure enough the event I created disappeared as
well as a few previous networks duplicated, resulting in them being
polled twice. So Stizzed assisted me in setting up a batch file which
works better, as it's now just one event .. however now the fidokill
.bsy is necessary as I get the mutil .bsy error. I haven't seen it
resolve on it's own without fidokill busy though .. you're lucky there.
What has been slightly helpful is making the largest traffic networks
poll last within the batch file. I may even split the batch file into
two, to reduce how much mutil is being asked to process at one time.
I know it's probably just an extra step, but it's worth a shot and
can't hurt anything. But if it's not the version change that caused
the issue ..... I wonder if it's the number of networks?

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)