It would be good to add the alpha number there too :)
The only reason it doesn't show the alpha there is just because it
didn't fit on the screen. :)
I'll have to see if I can get it fixed up to allow space for the alpha version and add in the -ver too.
There is a new MUTIL that should hopefully fix the bad CRC generation in the same place:
www.mysticbbs.com/downloads/mutil.rar
This is for Win32.
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.
Hey Necro =)
Are you running Mystic as root user or a non root user? Windows or Linux? I can't say I have had this issue and I run it as root user on Ubuntu 18.04 LTS server.
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.
Hi there
So if you shut MIS and just run MUTIL you see this issue right?
Is it when you run either the mailin.ini or mailout.ini or just happens for one ini?
It happens anytime MUTIL is ran. It was working just fine before.
Thanks
I'm gonna throw a monkeywrench into the fray.. When Necro's BBS polls my board, I get a authentication failure a password issue, but when I poll him the networks flow fine. I have tried turning off Cram5 no
difference.. Is it possible like you (Avon) said there is some corruption??
My hunch is that it's a corrupted echomail node.
I'd take a backup then..
Slim but possible.. but I'd say very unlikely to be related.
If you get an error what is it?
The probs you describe could be things like presenting the incorrect password or incorrect domain name that's been incorrectly spelled..
You would need to review what yours and Carlos's setting were.
Also check you're both using passwords that are 8 chars or less and ideally keep case to uppercase and use just letters and or numbers
My board calls through just fine to him.. It's weird, I have to check my logs but I think his board connected fine to me today.. It's a weird one but I thought I would throw that out there... :)
I think if you can poll him, get a secure connection and see packets exchange in your fidopoll logs then it would show passwords are fine and the basics of the usual handshaking are also ok.
If he polls you can things fail, I'd check to see if your MIS is
enforcing MD5 secure connects, perhaps that's it?
--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
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.
__ _ _ __ _ __ _ ____ . _ _ __
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.
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.
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.
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)
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.
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.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 203:14:40 |
| Calls: | 2,083 |
| Calls today: | 1 |
| Files: | 11,139 |
| Messages: | 947,992 |