Hi all. I recently connected to PiNet, and now nodes have begun
reporting as busy. I'm not yet sure if it only affects PiNet, or whether
it also affects my ability to send to fsxNet. I guess that will be
answered after sending this, seeing if it gets sent out or not.

Fidopoll is reporting this:

Jan 30 19:44:07 FIDOPOLL Version 1.12 A41 2018/12/27
Jan 30 19:44:07 Scanning 21:1/100
Jan 30 19:44:07 21:1/100 is busy; skipping
Jan 30 19:44:07 Scanning 314:314/0
Jan 30 19:44:07 314:314/0 is busy; skipping
Jan 30 19:44:07 Polled 0 nodes

Likewise, exporting echomail via mutil reports this:
Û Process ÄÄÄÄÄÄÄÄÄÄÄÄÄ Ä Status ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Result
Exporting EchoMail Cannot export. Some nodes are BUSY FATAL

And mailout_mutil.log reports the following:

----------------- MUTIL v1.12 A41 2018/12/27 Wed, Jan 30 2019 (loglevel
3)
+ Jan 30 19:56:58 Startup using mailout.ini
- Jan 30 19:56:58 EXEC ExportEchoMail
+ Jan 30 19:56:58 Process: Exporting EchoMail
+ Jan 30 19:56:58 Waiting for BUSY nodes
! Jan 30 19:57:58 Cannot export. Some nodes are BUSY
+ Jan 30 19:57:58 Results: Cannot export. Some nodes are BUSY in 60.06s
! Jan 30 19:57:58 Status: FATAL
+ Jan 30 19:57:58 Shutdown Normal (0)

What am I doing wrong?

¿ÚÂÄ ³ CatX, ³ . . . . . . . . . .
ÃÁ´. ³ SysOp Of ³ . . : . : . : . : . .
³ ÀÙ ³ Trigonia ³ . : . : . .

--- Mystic BBS v1.12 A41 2018/12/27 (Linux/64)
* Origin: Trigonia (21:1/197)

UPDATE: I think I solved it (by running "./fidopoll killbusy all"), but
I'm still curious as of why this issue occurred and how I can prevent it
from re-occurring.

¿ÚÂÄ ³ CatX, ³ . . . . . . . . . .
ÃÁ´. ³ SysOp Of ³ . . : . : . : . : . .
³ ÀÙ ³ Trigonia ³ . : . : . .

--- Mystic BBS v1.12 A41 2018/12/27 (Linux/64)
* Origin: Trigonia (21:1/197)

Hi all. I recently connected to PiNet, and now nodes have begun
reporting as busy. I'm not yet sure if it only affects PiNet, or whether it also affects my ability to send to fsxNet. I guess that will be answered after sending this, seeing if it gets sent out or not.

Well there are several possibilities. They could actually be busy. But really the most common one is that someone will do a CTRL-C or something to end fidopoll, mis, or mutil while its running. If these programs are killed in any ungraceful way it can cause all sorts of issues. A crash of the program itself could also do it.

You can try taking the server offline to make sure no one is connected, and
run fidopoll killbusy all to reset everything. Also the BSY files should automatically detect a "bad" busy flag after a few hours and reset it automatically. I think its after a node stays busy for 2 or 4 hours it will reset it... Sort of like what it also does with ghost BBS nodes after 24 hours.

--- Mystic BBS v1.12 A42 2019/01/25 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)