On Mon, Feb 17 2025 16:37:26 -0600, you wrote:

My first thought is that this is some bot/connection which tr connect unconventionally. Triggering something in Mystic whic
up the cpu for a minute or two.

So, after a lot of testing, debugging and trying to be on time to see what
is happening during these spikes.

It only happens when a telnet session is connecting to Mystic. The status
the node is: 'Logging in' for those 1:30-2:30 minutes at 99% CPU usage.

In the startup.mps script I added a MenuCMD function call to set the Node status to something else when my custom login prompt shows. Which means th
cpu spike is happening before startup.mps is called. Which could be BEFORE
or AFTER the Termtype detection.

I cannot set detect to ANSI only to solve this issue, because then we lost widescreen auto-support in Syncterm and Netrunner. And my board relies hea
on regular or widescreen support, depending on what is detected.

Now that I know this I will set the Node status in connect.mps to see if i
is before or after detection to maybe help g00r00 in figuring out what
might be happening.

-- EDIT
I found that Mystic gets 'stuck' on detecting termtype for these connecting bots/sessions. If an timeout for the termtype detect would be added I think
it would be solved.


oP!

... Boss spelled backwards is "double-SOB"

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

Hey opicron!

On Tue, Feb 18 2025 22:31:10 -0600, you wrote:

-- EDIT I found that Mystic gets 'stuck' on detecting termtype for
these connecting bots/sessions. If an timeout for the termtype detect
would be added I think it would be solved.

Ah, great find!

I think I see that happen with my Synchronet board as well, although I think there is a timeout in place already (maybe 10 or 15 seconds?). That and my CPU doesn't spike, so theres probably some better handling with that, too. Those termtype detections seem to be logged as RAW, rather than ANSI or ASCII.

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)

Hey opicron!

On Tue, Feb 18 2025 22:31:10 -0600, you wrote:

-- EDIT I found that Mystic gets 'stuck' on detecting termtype for these connecting bots/sessions. If an timeout for the termtype detect would be added I think it would be solved.

Ah, great find!

I think I see that happen with my Synchronet board as well, although I thi there is a timeout in place already (maybe 10 or 15 seconds?). That and my doesn't spike, so theres probably some better handling with that, too. Tho termtype detections seem to be logged as RAW, rather than ANSI or ASCII.

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.

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