Alright; what are the new logging options that were helpful, tG? I think that I

It's been some time since I've read the readme.txt file for that specific bullet point, but I think it was both poll.log and mutil that has more data when things aren't performing right. However if you're looking for the more robust logging to view .. I'll check out ArakNet's Mystic Support where he replied to me with some special logging command that could be performed as well.

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...

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 :)

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.

I think ML helped ya with this one, is it all fixed now? It was Screen causing the issue I think you said.

-tG

... A program is used to turn data into error messages.

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

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

... Top secret! Burn before reading!

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

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

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

since you know... 05/07 or whatever, thru 06/21????



|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)

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 :)

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.

I think ML helped ya with this one, is it all fixed now? It was Screen causing the issue I think you said.

-tG

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 all my binary Linux apps that I called from Mystic. Anyway, running ./mis daemon fixed all of it - and with some fancy schmancy cli commands I COULD run screen still and have ./mis server still function 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



|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)

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

You lost me here - but I'm gonna go type this command in and see what pops out anyway. :P

Whiskey? Nevermind....



|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)

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

I haven't read the rest of your replies so I should probably not write this but I will anyway lol!

Yes .. I would do a clean install in a temp directory and take a look within scripts, text, and data directories. What I found yesterday but not likely ALL:

1. New commands to input into your message readers .ini file. These do not affect your ANSI, but they do change the pop up ESC menu command choices to add tagline options for users who want to or not use taglines. (I just followed the whats new instructions and copied the str#'s out of this .ini file and into my own, since I have custom ansi file and didn't want my x/y coordinates messed up.
2. taglines.ini to make custom tagline menu ansi as well as other options.
3. taglines.dat is a global database of pre written taglines users can use, while also users can create their own custom taglines (*think Marly :) in their "personal tagline" database. The s255 access level is the only that can delete taglines from the global, but any user can delete from their personal.

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. that you specifically call them to. But I could be wrong ... I haven't had issues with the new version using as is, and just skim read the whatsnew.txt relating to all of the new ./mis stuff as most of it is for hubs.

Hope this helps.

-tG

... I know a good tagline when I steal one!

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

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.

Haha .. 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

So weird that that happens every update.

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

Hahaha .. just remember, FB gets hacked.

-tG

... Operator, give me the number for 911

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

You lost me here - but I'm gonna go type this command in and see what
pops out anyway. :P
Whiskey? Nevermind....

Cheers!

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

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)

On 28 Jun 2021, paulie420 said the following...

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...

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

... Insufficient facts always invite danger. Spock, stardate 3141.9.

--- Mystic BBS v1.12 A47 2021/06/28 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

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

Theres another way I could do it, in rc.local or... one of the other ones.

I really like the mystic_systemd .service thats out there, but it requires to run as root which doesn't [easily] work with my system. Its REALLY nice, tho, and has safegaurds built in to check for bsy's and make sure mis stays running... I wish I could use it; too many MPLs break from permissions issues while running mis in root.

https://vswitchzero.com/mystic-systemd/

... ASCII stupid question, get a stupid ANSI.



|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)