Subj : Synology Docker Mystic Test
To   : opicron
From : Accession
Date : Tue Feb 18 2025 06:15 pm

Hey opicron!

On Mon, Feb 17 2025 22:52:16 -0600, you wrote:

 > Yes, thats what I feel too. Lost.

 > I havent figured that out completely. Is it really a connection,
 > because I also run some event which call ./mystic -y (script) -ppass
 > -uuser.

Have you double checked that that event doesn't accidentally call './mystic -t (script) ..' due to a typo of any sort? That's VERY close, and the letters are right next to each other. ;)

 >>> So I noticed the process only very occassionaly runs ar 99% for more
 >>> than 2:30 minutes. I adjusted my script to only inform me when it
 >>> goes on longer than 5:00 minutes.

 >> Which script is this, connect.mps? When is this specifically ran?

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

I know what process you're referring to, but after that you said "I adjusted my script .." I was asking what script you were referring to.

 >> I wouldn't want my CPU spiked for even that long, to be honest. Why
 >> not se for like 10-20 seconds or something? I can't imagine anything
 >> else would o should spike the CPU for that long, unless something
 >> actually hangs or get stuck or something is wrong with your hardware
 >> - which you don't really wa 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.

Is there any way you can pull your Mystic setup out of the docker instance and see if you have the same issue(s)? Maybe this is specific to docker..

 > 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

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

I imagine you have your loglevel set too high. Debugging in 'mystic -cfg' may be turned off, but how high do you have logging set in all of your mutil.ini files?

 > This might have to do with it?

I don't know for sure. I don't use any python with my Mystic install, so thousands of those may indeed be assisting in the spiking of your CPU. I suppose, in that case you could disable your python scripts for maybe 24 hours, and see if you have any more spiking issues.

If I remember right, Mystic was specifically setup for python 2.7, and then people started trying to force python 3.x into it, which started messing things up, and I don't think g00r00 has been around to address any of that yet.

Regards,
Nick

.... He who laughs last, thinks slowest.
--- slrn/pre1.0.4-9 (Linux)
 * Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

.