I've been talking with Al & Warpslide about this, but I think they've done all for me that they can.

Anyone else had issues with "Waiting for BUSY nodes?" It's showing up in my mutil.log when I try to import echomail.

My only problem is that incoming messages from Fidonet are not getting imported (They don't show up on my BBS in my message bases.)

Messages from other nets (Scinet & Metronet) are importing just fine though.

Before coming here asking for more help, I scanned Fidonet, Scinet, and fsxNet for "BUSY nodes" and found a few conversations, but I didn't find any success stories.

My situation is unique, I think, because it's only with importing Fidonet echomail and not the other nets.

I've tried doing this:
./fidopoll killbusy
./mis poll killbusy
./mis poll killbusy all

I'm still using a45.

--- Mystic BBS/QWK Gate v1.12 A47 2020/11/23 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (77:1/100)

Anyone else had issues with "Waiting for BUSY nodes?" It's showing up in my mutil.log when I try to import echomail.
I'm still using a45.

I don't think this is the answer yer looking for, because... yer on 45. But; I did have that issue when I first switched to a47... and an update to the newest a47 fixed it FOR ME.

Which is not yer situation, and prolly doesn't help and.... but.... that fixed MY issue. :/



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbS>>20ForBeers.com:1337 (77:1/158)

I don't think this is the answer yer looking for, because... yer on 45. But; I did have that issue when I first switched to a47... and an update

Do you mean a46? I tried a46 and it seemed kinda messed up. After entering my username and password to log in, Mystic just paused for like 5 seconds before proceeding. I'll try it again though.

Thanks for the words of hope!

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)

Anyone else had issues with "Waiting for BUSY nodes?" It's showing up my mutil.log when I try to import echomail.
I'm still using a45.

I don't think this is the answer yer looking for, because... yer on 45. But; I did have that issue when I first switched to a47... and an update to the newest a47 fixed it FOR ME.

Which is not yer situation, and prolly doesn't help and.... but.... that fixed MY issue. :/

There was a bug or at least improvements in that area but I can't remember when it was though.

But also, BUSY issues can happen if your application crashes or if your BBS or computer is shutdown unexpectedly or improperly (like people doing kill -9 in Linux for example or shutting down their computer with the BBS running) so its hard to say exactly what the cause is. There could be anything from a bug to a one-off bad shutdown, etc.

A47 should help though in that area at least if it were an "unprovoked" issue.

--- Mystic BBS v1.12 A47 2020/12/21 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

Do you mean a46? I tried a46 and it seemed kinda messed up. After
entering myusername and password to log in, Mystic just paused for like
5 seconds beforeproceeding. I'll try it again though.

Pausing for 5 seconds means you probably have file access issues. Mystic waits 5 seconds trying to access a data file when it gives up because it can't (ie doesn't have access in Unix).

--- Mystic BBS v1.12 A47 2020/12/21 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

Do you mean a46? I tried a46 and it seemed kinda messed up. After entering myusername and password to log in, Mystic just paused for li 5 seconds beforeproceeding. I'll try it again though.

Pausing for 5 seconds means you probably have file access issues.
Mystic waits 5 seconds trying to access a data file when it gives up

Some day I will stop forgetting about file permissions.

Thank you!

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)

Pausing for 5 seconds means you probably have file access issues. Mystic waits 5 seconds trying to access a data file when it gives up

Some day I will stop forgetting about file permissions.

Hope it helps resolve it. I could be wrong too but thats the most common sign.

And don't feel bad I do it all the time too. I'll load up mystic -cfg or something and notice the delay which is the only reason I end up realizing that I screwed up my permissions! :)

--- Mystic BBS v1.12 A47 2021/01/04 (Windows/32)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

Do you mean a46? I tried a46 and it seemed kinda messed up. After entering myusername and password to log in, Mystic just paused for li 5 seconds beforeproceeding. I'll try it again though.

Pausing for 5 seconds means you probably have file access issues.
Mystic waits 5 seconds trying to access a data file when it gives up because it can't (ie doesn't have access in Unix).

Sorry to bring this up again - but I'm still trying to upgrade from a45 to
a46. After upgrading, I still have an issue with a 5 second delay immediately after logging in.

I tried chmod 755 *.* in every folder and subfolder.

I checked my login process. My start menu is prelogin. Prelogin just sets an access flag, sends a node message, then goes to main. All files in the data folder are set to 755 and all files in the menus folder are also set to 755. (Everything in my Mystic tree is set to 755)

Could there be anything else from the upgrade causing that? The delay doesn't happen anywhere else that I've found. It's only upon login.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)

Sorry to bring this up again - but I'm still trying to upgrade from a45 toa46. After upgrading, I still have an issue with a 5 second delay immediately after logging in.

I tried chmod 755 *.* in every folder and subfolder.

chmod does not assign ownership of files, you need to use chown.

What is the "user" and "group" you use to start your BBS?

Your command should look something more like this:

sudo chown -r user:group /mystic

Where user:group is replaced with the user and group you are using to run your BBS. When you look at files with something like "ls -la" it should show that all files in every directory are owned by the user who runs the BBS.

If they are not, then Mystic will not be able to access the file which means its sits there trying to wait for ~5 seconds just in case the file is locked by another process before it has to fail.

--- Mystic BBS v1.12 A47 2021/01/05 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

sudo chown -r user:group /mystic

Sorry I had to ask you this twice. I did a screenshot this time.

Thank you!

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)

sudo chown -r user:group /mystic

Sorry I had to ask you this twice. I did a screenshot this time.

Thank you!

No worries all good. Did it help you get it sorted out?

--- Mystic BBS v1.12 A47 2021/01/05 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

sudo chown -r user:group /mystic

Sorry I had to ask you this twice. I did a screenshot this time.

Thank you!

No worries all good. Did it help you get it sorted out?

Yes.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Compufuck | Binghamton, NY | compufuck.xyz (77:1/142)