I know this issue has been discussed before, but the advice I found from older conversations was to type ./fidopoll killbusy all, but I'm using
the latest alpha (a46) and the file "fidopoll" no longer exists in this version.
I know this issue has been discussed before, but the advice I found f older conversations was to type ./fidopoll killbusy all, but I'm usin the latest alpha (a46) and the file "fidopoll" no longer exists in th version.
It's now: mis poll killbusy all
I did that and the issue still persists (echomail not going out, and mutil.log still says "Waiting for BUSY nodes."
Do you know what else can cause that? I'm using Linux, latest alpha of Mystic.
Try shutting down mis and try that command again.
I'm not sure if that will help but it might.
The other Al...
On 12 Feb 2024 at 06:59p, Bucko pondered and said...
The other Al...
So many Al's :)
The power of Al combines.... it's like one of those super cleaning products for my computer screen :)
The power of Al combines.... it's like one of those super cleaning
products for my computer screen :)
LOL to bad my man cave is a total mess. Maybe if the original Al comes by my place I can get things cleaned..
I also tried polling for mail/running mutil with a fresh install of
Mystic and even then, the mutil.log says "Waiting for BUSY nodes."
Set "Log Level" to "Max" for both.
And then try polling again.
What does the line that says "Waiting for BUSY nodes" look like? Does
it have a "1-S:" or "1-R:" in front of it?
If it has 1-R: (or any number-R:) in front of it, it means your hub is sending you that message & would need to be dealt with on that end.
Maybe post that section of your poll.log here and we have have a look to
What does the line that says "Waiting for BUSY nodes" look like? Does
it have a "1-S:" or "1-R:" in front of it?
If it has 1-R: (or any number-R:) in front of it, it means your hub is sending you that message & would need to be dealt with on that end.
I set the "Log Level" to "Max" and tried polling again. I can't post the log file to this message because it doesn't come out well, but I looked
at poll.log and that log isn't the one that says "Waiting for BUSY
nodes." That message is only being logged in mutil.log.
Hmm... what does your .ini file look like for ExportEchoMail?
[ExportEchoMail]
; Do not export messages from users currently online
skip_online = false
If this is set to true it won't allow your messages to be exported until
During the time when this problem started (the problem of being unable to export echomail) I did not change anything in mutil.ini and I have not changed anything since then either. It just stopped working one day out of the blue.For permissions, go to your mystic root directory:
It might have happened in wake of a mystic update, or I may have changed folder permissions and/or ownership (would that have anything to do with it?)
For permissions, go to your mystic root directory:
sudo chown -R user:group *
"user:group" being the actual user and group you run Mystic with. -R to make sure it recurses into subdirectories. And sudo to force the issue
in case it won't let you change permissions of any one file under the mystic directory.
Also, I don't know if this still applies to the latest versions, but you could take a look in your mystic/data directory for "chat#.dat" I
believe it's called (# would be replaced by an actual number, ie: chat1.dat), and delete it. I think that was an old ongoing issue that caused ghost nodes.
No luck though! It still says "Waiting for BUSY nodes."
Thanks everyone, for the suggestions for my echomail issue.
I tried ./mis poll killbusy all, then I polled for mail again & ran
mutil, but I checked the log and it still says "Waiting for BUSY nodes."
I also tried polling for mail/running mutil with a fresh install of
Mystic and even then, the mutil.log says "Waiting for BUSY nodes."
Could it be a linux permissions issue? I'm not an expert at setting permissions and/or ownerships.
Not likely. Folks get lost in my own man cave but I know where
everything is as long as people don't move things around on me.. ;)
No luck though! It still says "Waiting for BUSY nodes."
Try posting the whole log here. It might be the hub you're trying to connect to that's giving that error. If that's the case, there's nothing you can do to fix it.
I have been reading this thread for a few days now. Please follow these steps 1. Shut down your BBS so it is not running waiting for calls.
2. In your BBS directory do a search for *.bsy
3. I am guessing there is .bsy files in echomail folders. Please delete any and all *.bsy files.
4. Restart Mystic -Server
5. Now, jump to a shell and then the BBS directory and do a MIS Poll
XXXX and verify you are connecting to your Target Host.
If, this fails, Please reach out to me via email. rickdeluco@gmail.com
and I will be more than happy to remote into your windows system and resolve. If this is linux or RPI, sorry I know nothing about linux.
Have you checked in your semaphore directory for poll.bsy? With the BBS DOWN delete that file, it will fix you right up.. You are getting the waiting for busy nodes because MIS poll thinks the BBS is currently polling..
I checked, and there was a .bsy file in mystic/echomail/out
I deleted the file, tried polling again, and it still says "Waiting for BUSY nodes."
If, this fails, Please reach out to me via email. rickdeluco@gmail.co and I will be more than happy to remote into your windows system and resolve. If this is linux or RPI, sorry I know nothing about linux.
Well, it's linux. But thanks anyway! It's no big deal if I don't get it working, but it would be cool if I could! ;)
Ok .. this is on the right track .. There is several folders there that contain your FTN node names. please look in the Mystic/echomail/out directory ... inside each one of the folders there please check for any .BSY files.. Also, in the Mystic/semaphore directory, there should be three files (maybe) mis.bsy and nodeinfo.now
Ok .. this is on the right track .. There is several folders there that contain your FTN node names. please look in the Mystic/echomail/out directory ... inside each one of the folders there please check for any .BSY files.. Also, in the Mystic/semaphore directory, there should be three files (maybe) mis.bsy and nodeinfo.now
If you shut down the Mystic -Server and look again these file should go away. If not Delete them all.
In:
./mystic -cfg
System Paths -> Message Base Path
Does that match where your message base paths are when you edit a
message base in:
Editors -> Message Base Editor -> (select message base) -> Path
Yes, the paths are the same in both sections.
Thanks for this advice. I checked the semaphore folder and the only file in there is nodeinfo.now
Yes, the paths are the same in both sections.
Looking back, your original issue was that echomail was not going out. When you were posting as "Shitty" you were posting from your BBS.
So, echomail is/was going out?
LOL to bad my man cave is a total mess. Maybe if the original Al comes b place I can get things cleaned..
Not likely. Folks get lost in my own man cave but I know where
everything is as long as people don't move things around on me.. ;)
I have lost the entrance to my man cave, there was a large box of floppy disks stored on a nearby shelf that tumbled and blocked/hid the
entrance. I've spent the last few months trying to dig it out but then
got called away by my wife who needed me on BBQ duties and when I got
back I forgot where the entrance was <--- some of this may not be strictly true, well most of it really, but we do have a BBQ :)
Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz
Sorry about that confusion. I am "Metalhead" on Avon's BBS and I'm "Shitty" on Alcoholiday BBS. My BBS is a different one (Compufuck) and no,
unfortunately the echomail issue still persists.
Either way, I would look a little deeper into your logs, maybe set them
to the max log capabilities. The "Waiting for busy nodes" thing may not
be an error, as seen by others posting their logs that say the same
thing, but packets are still going out.
Is this a new setup? Or did you have things working and you changed something causing things to stop working?j
If it's Mystic, check your links in 'mystic -cfg' and see if they're
still there. I had an issue once where they all disappeared on me for no apparant reason.
I had echomail working fine for a few years, but one day I noticed that my messages weren't going out. It might have happened after a Mystic update, or it might have happened after I restored the BBS from a backup, but I don't know. I have a node number on Fido, fsxnet, and on Metronet, and test messages won't go out on any of them, which makes me think it's on my end.
What do you mean by "links?"
I have lost the entrance to my man cave, there was a large box of floppy disks stored on a nearby shelf that tumbled and blocked/hid the
entrance. I've spent the last few months trying to dig it out but then
got called away by my wife who needed me on BBQ duties and when I got
back I forgot where the entrance was <--- some of this may not be strictly true, well most of it really, but we do have a BBQ :)
What do you mean by "links?"
So if I remember right, you can check two places. One would be "Uplinks" under each individual message base, and make sure your network uplink is still listed there. The other place would be "Echomail Nodes" to see if your uplinks are still listed there.
Oh ok, I checked everything in settings, and the paths are all correct
I appreciate your help with this issue, and I thank you and everyone else who assisted. I'm giving up on it.
| Sysop: | tracker1 |
|---|---|
| Location: | Phoenix, AZ |
| Users: | 54 |
| Nodes: | 25 (0 / 25) |
| Uptime: | 104:26:53 |
| Calls: | 367 |
| Files: | 1,364 |
| Messages: | 36,299 |