Subj : CPU Hog
To   : Digital Man
From : deon
Date : Fri Aug 05 2022 16:52:02

Howdy,

Today I discovered SBBS with 2 threads both running at 98% CPU - having stopped and restarted SBBS, its all back to normal.

At the same time, my fido hub alerted me to my system being "slow" and refusing packets. Curious, I looked through the logs and indeed it seems that when I polled my fsxhub, mail flowed normally, but when I polled my fido hub, it was stuck there receiving a file:

Authentication successful:
Attempting poll for node 3:633/280@fidonet
JSBinkP/4 callout to 3:633/280@fidonet started
Connecting to 3:633/280@fidonet at ftn633.vk3heg.net:24554
Peer version: binkd/1.1a-115/Linux
Will encrypt session.Authentication successful: secure
Receiving file: /opt/sbbs/temp/e8c38a06.pkt (1.4KB)
[no more output]

It doesnt appeaer that this thread dies - (and it should time out after 5 minutes right?) I ran "binkit -p" and it's still stuck on this node after 20 mins.

My fido hub is set to "Poll: Yes", so I'm suspecting everytime my system was polling, the old thread hadnt died yet, so eventually I end up with many threads tied up polling my fido hub.

So, shouldnt it ultimately time out after 5 mins?

Is there a way to "busy out" the polled node, so another thread doesnt try and call it again?




....лоеп

---
 ю Synchronet ю Alterant | an SBBS in Docker on Pi!

.