OK so I came home last night and check my board and after I run my bat file for
my interbbs league I notice that it won't connect to the hub saying it is busy.
So I trying polling FSXNet and it says it is busy. Then I notice that that mutil starts to run mailin and it says it is waiting for busy nodes. So I shut down mystic, reboot the computer and same problem.
Solution: I deleted all busy semaphores from the echomail out directories and
cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it) then ran mutil mailin again and it tossed everything else that was in my echomail in directory. Started up mystic server and all was good again. So one bad packet mucked up everything.

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

OK so I came home last night and check my board and after I run my bat file for

my interbbs league I notice that it won't connect to the hub saying it
is busy.

So I trying polling FSXNet and it says it is busy. Then I notice that
that mutil starts to run mailin and it says it is waiting for busy
nodes. So I shut down mystic, reboot the computer and same problem. Solution: I deleted all busy semaphores from the echomail out directories and

cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it) then ran mutil mailin again and it tossed everything else that was in my echomail in directory. Started up mystic server and all was good again.
So one bad packet mucked up everything.

I have the very same issue happen to me 3 months ago. You described,
verbatim, a total replay! I was able to resolve using the very same process and have not had the issue since. Crazy.

---

Rocket Town BBS - Telnet: rtbbs.ddns.net
fsxNET: 21:1/203 fidoNET:1:135/383 - sciNET: 77:1/125 Titusville, FL. USA

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Rocket Town BBS (21:1/203)

On 16 Jun 2021, Argos said the following...

OK so I came home last night and check my board and after I run my ba file for

my interbbs league I notice that it won't connect to the hub saying i is busy.

So I trying polling FSXNet and it says it is busy. Then I notice that that mutil starts to run mailin and it says it is waiting for busy nodes. So I shut down mystic, reboot the computer and same problem. Solution: I deleted all busy semaphores from the echomail out directories and

cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it then ran mutil mailin again and it tossed everything else that was in echomail in directory. Started up mystic server and all was good agai So one bad packet mucked up everything.

I have the very same issue happen to me 3 months ago. You described, verbatim, a total replay! I was able to resolve using the very same processand have not had the issue since. Crazy.

This could be solved with just a quick `./fidopoll killbusy` command. =)

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)

On 15 Jun 2021, Sparky said the following...

my interbbs league I notice that it won't connect to the hub saying it
is busy.

cleaned out the semaphore directory and tried running mutil mailin. I errored out on one packet. Checked the packet (looked OK but moved it) then ran mutil mailin again and it tossed everything else that was in
my echomail in directory. Started up mystic server and all was good again. So one bad packet mucked up everything.

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Yes that was a problem for me with the 2021/02/12 in Linux as well. There are updates even this month that fixed many of the bad packet hangs. Try updating
if your really using 2021/02/12 (Windows/32) as the tag line shows.

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

On 16 Jun 2021, MeaTLoTioN said the following...

This could be solved with just a quick `./fidopoll killbusy` command. =)

Not quite, ./mis poll killbusy
it shows as A47 and that is the command since A46.

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

This could be solved with just a quick `./fidopoll killbusy` command. =)

Actually no, first I don't use or still have fidopoll (I use mis poll) second the bad packet would just create more .bsy flags next time packets were tossed . (but thanks for the suggestion) Hopefully (as i see someone else had the same
issue) someone else who comes across this problem will be able to find this solution.
Jeff

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Or in my case mis poll killbusy since I am running under win 32 :)

Did you get your version of v47 updated? I noticed you're running an older version from February. The latest version fixed all of those issues for me on linux, however I did not try my windows test box. Curious to know if the new version fixed your polling issues on windows prior to upgrading it, as I'm currently running a stable v47 on windows for my testing system. My RPI is on one of the later (but not the latest) version and it's running great. Prior I had to add a .sh file to mis poll killbusy all, poll each hub individually, with a 10 second delay in between each, and then process my inbound mail. It was a pain but the new MIS seems to work perfectly.

-tG

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Or in my case mis poll killbusy since I am running under win 32 :)

Did you get your version of v47 updated? I noticed you're running an older version from February. The latest version fixed all of those
issues for me on linux, however I did not try my windows test box. Curious to know if the new version fixed your polling issues on windows prior to upgrading it, as I'm currently running a stable v47 on windows for my testing system. My RPI is on one of the later (but not the
latest) version and it's running great. Prior I had to add a .sh file to mis poll killbusy all, poll each hub individually, with a 10 second
delay in between each, and then process my inbound mail. It was a pain but the new MIS seems to work perfectly.

-tG

I updated to the newest, AND I had cr1mson(KANSIT) go over my FTN setup.. he sayes its all ironed out now (Netmail should work on 2o again!) BUT I'm still getting danged poll.bsy files in my /semaphore that holds up my polling of the FTNs.

I *did*, however, STILL have that temppoll.sh running - SO I just turned THAT off and ONLY have the standard ./mis poll forced | ./mutil mailin running now... I'm hoping to see that iron all the bubbles out. I'm over this farting around trying to get things running like they did a couple months ago. :P



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

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hello paulie420.

20 Jun 21 17:43, you wrote to The Godfather:

Or in my case mis poll killbusy since I am running under win
32 :)

Did you get your version of v47 updated? I noticed you're
running an older version from February. The latest version fixed
all of those issues for me on linux, however I did not try my
windows test box. Curious to know if the new version fixed your
polling issues on windows prior to upgrading it, as I'm currently
running a stable v47 on windows for my testing system. My RPI is
on one of the later (but not the latest) version and it's running
great. Prior I had to add a .sh file to mis poll killbusy all,
poll each hub individually, with a 10 second delay in between
each, and then process my inbound mail. It was a pain but the
new MIS seems to work perfectly.

-tG

I updated to the newest, AND I had cr1mson(KANSIT) go over my FTN
setup.. he sayes its all ironed out now (Netmail should work on 2o
again!) BUT I'm still getting danged poll.bsy files in my /semaphore
that holds up my polling of the FTNs.

i've tested the netmail and only the fsxnet netmail arrived from your system to mine. but nothing goes back. no fidonet or tqwnet netmails arrived to/from me.
:(

I *did*, however, STILL have that temppoll.sh running - SO I just
turned THAT off and ONLY have the standard ./mis poll forced | ./mutil mailin running now... I'm hoping to see that iron all the bubbles out.
I'm over this farting around trying to get things running like they
did a couple months ago. :P

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

--- Mystic BBS v1.12 A47 2021/06/07 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Daniel

... 10:02am up 5 days, 23:02:00, load: 69 processes, 275 threads.
--- GoldED+/EMX 1.1.4.7
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

Wait - I still only do ./install replace ~/mystic - am i missing something, tG???

1. New commands to input into your message readers .ini file. These do 2. taglines.ini to make custom tagline menu ansi as well as other
3. taglines.dat is a global database of pre written taglines

Yea, I know I've asked you at a few places.. BUT, I figured it out and READ the dang upgrade.txt and whatsnew.txt. :P Thats kinda important - but with so many a47 builds, sometimes you just do what you always do...

I will now be checking that EVERYTIME. I know thru the upgrades that I've missed out on a couple 'new demos' that g00 included... and wonder if there was anything else...

I can't remember what else I copied over .. this evening I'm looking at mutil.ini as there appears to be changes to this as well, however I *think* they are just new event commands that can be executed that would read a singular mutil.ini file, and only run the semaphores, etc.

Yea, I didn't do anything with mutil.ini either... since I had custom .ini's, I made the tagline edits myself to my current msg_editor.ini - which is good because I keep learning more and more about how Mystic works and things that can be done. In a round-about way, theres LOTS of modification possibilities.

... Documentation: The worst part of programming.



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

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Yup - all 'fixed'. Screen was changing the terminal settings from 256 colors to, I think, 8... and that caused Mystic to return some nasty characters over

So weird that that happens every update.

Just in case someone else might read this and have a similar issue... it wasn't because of the Mystic updates. It actually was a cause of my using SCREEN...

I'd started loading ./mis server thru SCREEN so that I could re-attach the MIS 'wfc' screen on any SSH connection that I made to my BBS box. A while ago I'd load ./mis server just on the graphical desktop on my Raspberry Pi OS... if I wanted to see it, I'd either have to go to the Pi with a monitor/keyboard or VNC into it...

So I was using SCREEN instead. What this caused, and can be fixed with commands that set SCREENs terminal color mode, was my Linux external apps that ran thru Mystic either with a (DD) command or called by MPL code where displaying extra ANSI/ASCII characters rendering the application to show garbled to the end user.

Anyway, I'm now running in ./mis daemon mode until I decide how I want to ultimately run the Mystic server. I may just end up loading ./mis daemon in a cronjob at boot... I'm learning to use the logs a lot more and another Linux app called LNAV is really helpful and digging thru data in logs...

Who knows...

... Everyone is entitled to my opinion!



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

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)