Subj : Fw: Synology Docker Mystic Test
To   : Accession
From : opicron
Date : Sun Mar 30 2025 01:45 pm

 Ac> Hey opicron!
 Ac> 
 Ac> On Tue, Feb 18 2025 22:31:10 -0600, you wrote:
 Ac> 
 Ac>  > -- EDIT I found that Mystic gets 'stuck' on detecting termtype for
 Ac>  > these connecting bots/sessions. If an timeout for the termtype detect
 Ac>  > would be added I think it would be solved.
 Ac> 
 Ac> Ah, great find!
 Ac> 
 Ac> I think I see that happen with my Synchronet board as well, although I thi
 Ac> there is a timeout in place already (maybe 10 or 15 seconds?). That and my
 Ac> doesn't spike, so theres probably some better handling with that, too. Tho
 Ac> termtype detections seem to be logged as RAW, rather than ANSI or ASCII.
 Ac> 
I hope this is the final solution of my issue where SSH sessions where stalling the terminal detection and spiking my CPU to 100%.

Spend waaay to much time tweaking and tinkering bash scripts to kick these bots off the node.

I was using a docker based on a python image. For a completely different reason I had to rebuild my dockerfile and started to build a ubuntu:16.04 docker image. Why 16.04? Because cryptlib 3.4.3 build on that release.

Since yesterday I noticed that 1) the cpu utilization was less overall and 2) no nodes got stallled.

Today I build the 20.04 and 22.04 docker images after finding out how to build cryptlib 3.4.4 for 20.04 and 3.4.5 for ubuntu 22.04.

Fingers crossed this actually fixed it!


PS: the reason I had to switch docker image was because mystic -y scripts were not runnign in the background. This had nothing to do with the image in the end, but more with missing TTY/bash shell settings. Fixed that with spawn/expect now.

 Ac> Regards,
 Ac> Nick

oP!

.... Blood is thicker than water, and much tastier.

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

.