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.
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.
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)
This could be solved with just a quick `./fidopoll killbusy` command. =)
This could be solved with just a quick `./fidopoll killbusy` command. =)
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.
Not quite, ./mis poll killbusy
it shows as A47 and that is the command since A46.
Or in my case mis poll killbusy since I am running under win 32 :)
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
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)
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
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. :(
Thats so wierd, when I upgraded I didn't have .bsy issues anymore, but also abandoned the temppoll.sh right away ..
lemme know how things work for you as I'd like to upgrade to 6.20 on the RPI, but am hesitent. Like you, I'd rather be drawing ANSI, coding, or changing my menus around to confuse my users (keep them on their feet :) then to be farting around with polling issues out of my control.
-tG
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. :(
So, I assume I'll need to check my BINK port and... that side of
things. Hmmmm.
|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)
Ahhh, now I see what the hub bub is about. Another new build, eh. :P
Maybe I'll just go for it and... couldn't hurt; g00r00 did a great job
on the last one. I'm gonna give it a crack.
I pulled the trigger and did it, and actually was able to narrow down my problem newly appearing .bsy issues thanks to the improved logging. I
had been polling PiNet, but I know he's been manually reentering all of his nodes for retronet, and I'm sure PiNet is also the same case?
Anyway, I had been getting "Unauthorized something .." Anyway, I simply set it to Not active, and all of my .bsy issues went away. I am having the same issue with DoreNet and HappyNet. So turning both to Not active has made this new version run even more smoothly then the 6.7 ..
-tG
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
have some FTN issues buried away - EVEN after cr1mson ironed me out a little better than I know how. I deleted SciNet everything, and my
system is either still polling SciNet OR SciNet is still polling ME...
But I see SciNet things; so... something is amiss on my end.
But I see SciNet things; so... something is amiss on my end.
Did you remove all echos & file areas via AreaFix from SciNet before removing the setup? If not, his system will still try and send them to you.
You can always add bbs.diskshop.ca's IP address (45.72.177.237) to mystic/data/blacklist.txt as well.
True... will think about that, altho its no huge deal. TBH, I wish
SciNet was still a viable FTN - I really liked it.
Upgraded before I went on vacation for a few days and all seems well.
The real culprit was a bad packet and knock on the monitor I haven't
had a bad packet since (or if I did I haven't seen evidence of it)
Jeff
Alright; what are the new logging options that were helpful, tG? I think that I
have some FTN issues buried away - EVEN after cr1mson ironed me out a little better than I know how. I deleted SciNet everything, and my
system is either still polling SciNet OR SciNet is still polling ME...
Also, my Linux binary app/external programs issue has come back. When I run an external program (Like Lynx or cmatrix for Matrix Rain...) Linux is sending MANY extra * characters to the end user. WHY!?!??!?! OMG. My AFK looks horrible; as does Lynx... and I had fixed this with a Mystic upgrade, but it came back... so now I actually have to FIND the exact reason and iron it out.
Yeah I haven't had issues either so I'm pretty happy with this upgrade.
I went ahead and turned on the taglines for the time being as it's
pretty cool; but haven't edited any of my ANSI's to indicate so to the users yet. I also added the OC access flag as a new user ANSI for their first login only. So some neat little nuggets he's adding to v47 .. trying to keep up on them all ... one thing I'm learning is to not
simply do ./install replace ~/mystic ... as there are new ansi's and
data files being introduced as well.
-tG
You're likely getting stuff from SciNet because he hasn't removed you
from the nodelist and so his system is still calling you. I can log on your system and check out polling, if I can find the password you gave
me :)
I think ML helped ya with this one, is it all fixed now? It was Screen causing the issue I think you said.
-tG
Here is the command line logging g00r00 had me do that helped him/I discover a few more issues.
strace -s -o mistrace.txt ./mis poll forced
the rest was just poll.log and mutilXXXXXX.log which either I changed
the level of logging or I think it's in whatsnew.txt that he added extended logging to one of them.
-tG
Wait - I still only do ./install replace ~/mystic - am i missing something, tG???
No problem, my sysOp pw is "paulieisTHEis6969". Thanks for the help, man
- don't tell anyone that I have no idea what I'm doing... Omg.
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
correctly. But I'm learning to live with ./mis daemon. :P Oh, the
things we learn... don't learn... get thru, and don't get thru. I actually hate all of this and am gonna go 100% facebook soon... :P
You lost me here - but I'm gonna go type this command in and see what
pops out anyway. :P
Whiskey? Nevermind....
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
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.
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.
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...
Anyway, I'm now running in ./mis daemon mode until I decide how I wan ultimately run the Mystic server. I may just end up loading ./mis dae in a cronjob at boot...
That's kind of what I do, I run ./mis daemon in rc.local on bootup. I
was playing around with starting it as a service before I went and
played with Telegard again. Now I'm back to Mystic...
Jay
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 96 |
Nodes: | 16 (1 / 15) |
Uptime: | 10:34:28 |
Calls: | 4,663 |
Calls today: | 4 |
Files: | 8,491 |
Messages: | 349,787 |