Re: Re: mutil issues
  By: Aaron Thomas to Al on Mon Dec 28 2020 10:49 am

 AT> I posted a test message in "Fidonet: Asian Links"
 AT> I ran mutil (with import echomail=true and export echomail=true)
 AT> - mutil indicated that 1 echomail was exported
 AT> I ran fidopoll to poll my Fido hub
 AT> - fidopoll indicated that 1 message was sent and that a packet was

Was that Dec. 26? I see a message in ASIAN_LINK from you and just replied.

OK, now I see that message was posted at Shenks Express.

I wonder if there is some issue between yourself and Shenks? Maybe a packet
password error? If you are currently using a packet password, try removing it
or if not try adding it and testing.

You might have to get a hold of Carol and confirm the settings you are using
and things are working as expected.

FIDOTEST is a good place (or this one) to test away and we'll tell you what we
see.

 AT> ----- That "Waiting for BUSY nodes" part is suspicious! -----

Yes, it is. That can be a problem. Mystic doesn't toss or scan if there are
busy nodes, it'll do the toss and scan after the outbound is not busy.

I've had that happen before but not in quite a while. If that happens I would
run "./mis poll killbusy all". If mis is running you might have to shut it down
before running that command.

Fidopoll has been removed from recent versions of Mystic. If you are running a
recent version I would delete fidopoll and use "mis poll 1:234/567" or "mis
poll killbusy all".

 AT> Further into the log shows what happened when I ran mutil AFTER polling:
 AT> Process: Importing EchoMail
 AT> Waiting for BUSY nodes
 AT> Extracting 00000001.MO0
 AT> Importing 28085851.PKT (1:275/100 to 1:275/99)

 AT> Then I logged on to my hub's BBS (Shenk's Express) and found that my test
 AT> message that I posted in Fido: Asian Links did not post to the network.

This is what makes me suspicious of a packet password issue. Try adding or
removing your packet password and see if things work better. If that still
doesn't work you have to get a hold of Carol and ask her to look into it.

 AT> Let me know what you make of this. I suspect there's something up with
 AT> "Waiting for BUSY nodes."

That's a different issue that can happen from time to time. I'm not sure how we
get into that situation but the only cure that I know is to shut down mis (if
it is running) and run "mis poll killbusy all".

 Ttyl :-),
         Al

... You cannot achieve the impossible without attempting the absurd.
--- SBBSecho 3.12-Linux