• Re: MUTIL

    From Al@21:4/106.1 to The Godfather on Tue Aug 11 15:40:17 2020
    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)
  • From Nazferiti@21:3/107 to The Godfather on Tue Aug 11 19:57:29 2020
    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)
  • From The Godfather@21:1/165 to Al on Wed Aug 12 10:07:38 2020
    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)
  • From The Godfather@21:1/165 to Nazferiti on Wed Aug 12 10:14:53 2020
    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)