Noticed that when I change the sbbs.ini file (either manually or through the config script) when I am logged into the BBS via SSH that when the BBS goes to restart/reload the config file after I log off that it will no longer accept connections. I have to go in and manually stop the sbbs service and restart it via systemctl. Then everything is back to normal.
Has anyone noticed this behaviour?
It's due to the ports remaining in TIME-WAIT status. It takes around 60 second s to clear and the port to get released. I'm not really sure if there's a C call or what that could force the port closed without a TIME-WAIT when the server restarts/shuts down, that'd probably be a question
If nothing else, a wait loop may be the answer. Just throw in a sleep(60); perhaps after shutdown?
You can edit sbbs.ini and change:
BindRetryCount
BindRetryDelay
I have mine set to 10 and 15 respectively, it works fine when I restart the server.
SBBS 3.17 running on CentOS 7
Noticed that when I change the sbbs.ini file (either manually or through the config script) when I am logged into the BBS via SSH that when the BBS goes to restart/reload the config file after I log off that it will no longer accept connections. I have to go in and manually stop the sbbs service and restart it via systemctl. Then everything is back to normal.
Has anyone noticed this behaviour?
Rob
That happens to me also on Slackware only I have to kill -9 or pkill sbbs. my solution to get a graceful shutdown/restart is to run sbbs in console on one tty and everything else on another.
Re: Re: BBS partially hangs when config file changes
By: Mortifis to Dmxrob on Wed Feb 13 2019 05:54 am
That happens to me also on Slackware only I have to kill -9 or pkill sbbs. my solution to get a graceful shutdown/restart is to run sbbs in console on one tty and everything else on another.
After applying the changes to sbbs.ini for the timeout and retry values for sockets, the issue has went away, at least for me.
SBBS 3.17 running on CentOS 7
Noticed that when I change the sbbs.ini file (either manually or through the config script) when I am logged into the BBS via SSH that when the BBS goes to restart/reload the config file after I log off that it will no longer accept connections. I have to go in and manually stop the sbbs service and restart it via systemctl. Then everything is back to normal.
Has anyone noticed this behaviour?
Rob
That happens to me also on Slackware only I have to kill -9 or pkill
sbbs. my solution to get a graceful shutdown/restart is to run sbbs in console on one tty and everything else on another.
On 02-13-19 08:31, Jagossel wrote to Mortifis <=-
And then, this morning, I tried to log in to my BBS this morning using QModem in DOSBox on my phone and QModem kept saying "NO CARRIER" (not really sure what that means in the emulated modem realm). I saw that my
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 28 |
Nodes: | 8 (0 / 8) |
Uptime: | 20:36:25 |
Calls: | 2,011 |
Calls today: | 1 |
Files: | 11,117 |
Messages: | 944,013 |