I am still having (or started having again) issues with binkit hanging during outbound sessions. I have a crontab script event that calls binkit every few hours by running this single command:
touch /sbbs/data/binkit.now
That has been working without issue for months. Just recently, I have noticed that binkit has been hung on the system. I notice it because QWK mail sessions (users and nodes) come in, sit about 5 minutes, and then timeout without creating a QWK *OR* they upload a REP which does not unpack.
If I 'Q'uit synchronet and start it up again, I will see a BINKIT error flash by when it is going down, and will see the REP(s) uppack when I am bringing it back up.
This is under linux, BTW.
Here is some log output. Note that the BINKIT session in question was started at 1600 local time, so it sat that long until I hit 'Q' and it spat out these messages (there was no error when everything stopped at 1600):
11/2 18:51:15 srvc 0040 BinkIT closing socket 0.0.0.0 port 24554
11/2 18:51:15 srvc 0041 BinkIT closing socket :: port 24554
11/2 18:51:15 srvc #### Services thread terminated (222 clients served)
11/2 18:51:15 evnt BINKIT Failed to receive the whole file '/sbbs/temp/event/0000ffb5.sa0'.
I checked my sbbsecho.ini and there do not appear to be any rogue entries at the bottom as there were the last time I had any issues with binkit connections. I did see these entries, which look a little weird to me:
BsyTimeout = 12H
BsoLockDelay = 10S
BsoLockAttempts = 60
MaxEchomailAge = 60D
MaxNetmailAge = 0S
Should those entries be a mix of alpha and numeric characters?
Here is some log output. Note that the BINKIT session in question was started at 1600 local time, so it sat that long until I hit 'Q' and it spat
out these messages (there was no error when everything stopped at 1600):
11/2 18:51:15 srvc 0040 BinkIT closing socket 0.0.0.0 port 24554
11/2 18:51:15 srvc 0041 BinkIT closing socket :: port 24554
11/2 18:51:15 srvc #### Services thread terminated (222 clients served) 11/2 18:51:15 evnt BINKIT Failed to receive the whole file '/sbbs/temp/event/0000ffb5.sa0'.
Looks like it was attempting to receive a file and went into some kind of blocking poll/select or receive without timeout.
Looks like it was attempting to receive a file and went into some kind of blocking poll/select or receive without timeout.
Yeah, except it waited nearly 3 hours to do so, and only did so when I hit
Q to stop synchronet. I don't think it is supposed to do that, is it?
Re: binkit timeouts/hanging
By: Dumas Walker to DIGITAL MAN on Sat Nov 03 2018 07:16 pm
Looks like it was attempting to receive a file and went into some kind of blocking poll/select or receive without timeout.
Yeah, except it waited nearly 3 hours to do so, and only did so when I hit
Q to stop synchronet. I don't think it is supposed to do that, is it?
No, I wasn't trying to suggest it should be doing that.
Looks like it was attempting to receive a file and went into some kind of >> > blocking poll/select or receive without timeout.
Yeah, except it waited nearly 3 hours to do so, and only did so when I hit >> Q to stop synchronet. I don't think it is supposed to do that, is it?
No, I wasn't trying to suggest it should be doing that.
And you can file a bug report with the author (Deuce) here: https://github.com/RealDeuce/cvs-synchronet-exec/issues
And you can file a bug report with the author (Deuce) here: https://github.com/RealDeuce/cvs-synchronet-exec/issues
It was a real pain getting an account set up... I seemed to get stuck in an endless "verify your email account" loop, but it is posted now.
Any chance you can nudge him into reading the bbs echoes that support the software he works on?
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 123:28:35 |
Calls: | 506 |
Messages: | 219663 |