Subj : Synology Docker Mystic Test
To   : Accession
From : opicron
Date : Mon Feb 17 2025 10:52 pm

 Ac> On Mon, Feb 17 2025 16:37:26 -0600, you wrote:
 Ac> 
 Ac>  > When I run ./mystic -T+ myself it just starts a local board node. I
 Ac>  > guess its the command to open a telnet session when someone connects.
 Ac> 
 Ac> I believe the command is './mystic -T#' where "#" is a time in minutes tha
 Ac> whoever logging in would be limited to (even if their user account is set 
 Ac> something higher). If something is running './mystic -T+' then you've real
 Ac> lost me, since that doesn't seem to be a valid parameter for that command,
 Ac> all.

Yes, thats what I feel too. Lost.

 Ac> 
 Ac>  > My first thought is that this is some bot/connection which tries to
 Ac>  > connect unconventionally. Triggering something in Mystic which runs
 Ac>  > up the cpu for a minute or two.
 Ac> 
 Ac> I'm pretty stumped on this one, to say the least. The _only_ way I can get
 Ac> -c' to produce that command is if I manually type './mystic -T20' or somet
 Ac> similar at the Linux console prompt (which means I'm actually forcing it t
 Ac> happen).
 Ac> 
 Ac> Also, I don't remember if you said that it only happens when a user connec
 Ac> not? The fact that no other commands were passed to Mystic on a regular te
 Ac> connection would also leave me completely confused, since usually things l
 Ac> '-HOST', '-IP', and '-TID' are passed on those connections.
 Ac> 
I havent figured that out completely. Is it really a connection, because I
also run some event which call ./mystic -y (script) -ppass -uuser.

 Ac>  > So I noticed the process only very occassionaly runs ar 99% for more
 Ac>  > than 2:30 minutes. I adjusted my script to only inform me when it
 Ac>  > goes on longer than 5:00 minutes.
 Ac> 
 Ac> Which script is this, connect.mps? When is this specifically ran?

Thats the ./mystic -T+ process wich I am referring to.

 Ac> 
 Ac>  > Nothing triggered the script so far. I'll probably leave it like this
 Ac>  > and only reset on the rare occurrence when it runs for too long.
 Ac> 
 Ac> I wouldn't want my CPU spiked for even that long, to be honest. Why not se
 Ac> for like 10-20 seconds or something? I can't imagine anything else would o
 Ac> should spike the CPU for that long, unless something actually hangs or get
 Ac> stuck or something is wrong with your hardware - which you don't really wa
 Ac> happen anyways.

Well true, though Mystic runs in a docker, which is taking 100%. The CPU 
of the servers goes from 3% to 14% during this time. So I am not too worried
yet.

 Ac> Have you by chance tried setting up a default install outside of your setu
 Ac> see if it happens there, too? Then you can re-introduce all of your
 Ac> mods/scripts one by one to see if one of them triggers either the command,
 Ac> the CPU spikes.
No I havent, but its a good idea.

One thing which I noticed when moving to Mystic a49 is my log files piling up
with stuff like this:

2025.02.17 22:44:56 DEBUG PyDepth=0
2025.02.17 22:44:56 DEBUG PyFree6
2025.02.17 22:44:56 DEBUG PyFree7
2025.02.17 22:44:57 DEBUG PyFree4
2025.02.17 22:44:57 DEBUG PyFree5
2025.02.17 22:44:57 DEBUG PyDepth=0
2025.02.17 22:44:57 DEBUG PyFree6
2025.02.17 22:44:57 DEBUG PyFree7
2025.02.17 22:44:58 DEBUG PyFree4
2025.02.17 22:44:58 DEBUG PyFree5
2025.02.17 22:44:58 DEBUG PyDepth=0
2025.02.17 22:44:58 DEBUG PyFree6
2025.02.17 22:44:58 DEBUG PyFree7
2025.02.17 22:44:59 DEBUG PyFree4
2025.02.17 22:44:59 DEBUG PyFree5
2025.02.17 22:44:59 DEBUG PyDepth=0
2025.02.17 22:44:59 DEBUG PyFree6
2025.02.17 22:44:59 DEBUG PyFree7
2025.02.17 22:45:00 DEBUG PyFree4
2025.02.17 22:45:00 DEBUG PyFree5
2025.02.17 22:45:00 DEBUG PyDepth=0
2025.02.17 22:45:00 DEBUG PyFree6
2025.02.17 22:45:00 DEBUG PyFree7

Like thousands of these. Even when I turn off all debugging in Mystic CFG
they keep piling up.

This might have to do with it?

oP!

.... Dammit, Jim, I'm a floor wax, not a dessert topping!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: TheForze - bbs.theforze.eu:23 (21:3/126)

.