Re: CPU Hog
By: Digital Man to deon on Mon Aug 08 2022 05:34 pm
> > My logs show it does run twice a day (not 12 hrs apart, ergo 2 times a day
- but...)
>
> > Aug 5 00:35:54 d-11-1 synchronet: evnt BINKPOLL Running native timed even
t: BINKPOLL
> > Aug 5 14:36:58 d-11-1 synchronet: evnt BINKPOLL Running native timed even
t: BINKPOLL
>
> > So if the first question is yes, then that would imply that binkit -p does
eventually exit.
>
> Yes.
>
> And for ever foreground "Running" log entry there should be a corresponding l
og entry like this:
>
> BINKPOLL Timed event: BINKPOLL returned 0
Ahh, OK - so it ran for 2hrs and 1 min the first time:
Aug 5 02:36:58 d-11-1 synchronet: evnt BINKPOLL Timed event: BINKPOLL returned
0
Aug 5 14:37:26 d-11-1 synchronet: evnt BINKPOLL Timed event: BINKPOLL returned
0
And the 2nd time it finished after 30s - because when it did poll my fido uplink
, it was stuck already (the uplink polled me at 14:33 - and thus my connect to t
hem got a "busy" message):
Aug 5 14:37:19 d-11-1 synchronet: evnt BINKPOLL Attempting poll for node 3:633/
280@fidonet
Aug 5 14:37:19 d-11-1 synchronet: evnt BINKPOLL JSBinkP/4 callout to 3:633/280@
fidonet started
Aug 5 14:37:20 d-11-1 synchronet: evnt BINKPOLL Connecting to 3:633/280@fidonet
at ftn633.vk3heg.net:24554
Aug 5 14:37:20 d-11-1 synchronet: evnt BINKPOLL Peer version: binkd/1.1a-115/Li
nuxAug 5 14:37:20 d-11-1 synchronet: evnt BINKPOLL BinkP got non-fatal error 'S
ecure AKA 3:633/509@fidonet busy' from remote: 3:633/280@fidonet,3:633/0@fidonet
,21:1/195@fsxnet,39:901/280@amiganet,39:901/0@amiganet,46:3/101@agoranet
It appeared my fido polled me roughly every hour or so, and what I did notice is
the absense of a corresponding:
BINKP service thread terminated (4 clients remain, 4 total, 60 served)
for his polls, when his poll would have ended.
Checking through my logs I see often "[3-6] clients remain" for the BINKP servic
e thread - so that indicates binkp sessions that havent yet exited?
Aug 5 00:11:16 d-11-1 synchronet: srvc 0107 BINKP service thread terminated (5
clients remain, 4 total, 2973 served)
Aug 5 00:12:14 d-11-1 synchronet: srvc 0108 BINKP service thread terminated (6
clients remain, 5 total, 2975 served)
Aug 5 00:12:19 d-11-1 synchronet: srvc 0110 BINKP service thread terminated (5
clients remain, 4 total, 2975 served)
Aug 5 00:15:52 d-11-1 synchronet: srvc 0108 BINKP service thread terminated (5
clients remain, 4 total, 2976 served)
Aug 5 00:16:19 d-11-1 synchronet: srvc 0108 BINKP service thread terminated (5
clients remain, 4 total, 2977 served)
Aug 5 00:16:38 d-11-1 synchronet: srvc 0108 BINKP service thread terminated (5
clients remain, 4 total, 2978 served)
Aug 5 00:20:53 d-11-1 synchronet: srvc 0109 BINKP service thread terminated (5
clients remain, 4 total, 2979 served)
Aug 5 00:21:27 d-11-1 synchronet: srvc 0109 BINKP service thread terminated (6
clients remain, 5 total, 2981 served)
Aug 5 00:21:59 d-11-1 synchronet: srvc 0111 BINKP service thread terminated (5
clients remain, 4 total, 2981 served)
Aug 5 00:22:20 d-11-1 synchronet: srvc 0109 BINKP service thread terminated (5
clients remain, 4 total, 2982 served)
Aug 5 00:22:39 d-11-1 synchronet: srvc 0109 BINKP service thread terminated (5
clients remain, 4 total, 2983 served)
> Well if you figure out how to reproduce the problem, let me know.
I might be able to, as I think it is MTU related - and I can revert my MTU confi
guration back to 1500 to try and get it to happen again. I'm not too worried abo
ut fixing it, as it's no longer an issue over IPv4 - so I copied the above for y
ou in case there is another underlying issue with the BINKP service thread and n
ot exiting that you are interested in.
...δεσ∩
---
■ Synchronet ■ Alterant | an SBBS in Docker on Pi!
|
