Re: Synchronet --- telnet issues
By: Rmh to Digital Man on Thu May 03 2018 07:46 pm
Digital Man et all,
Nots sure whether you have found before the scenario the telnet service dies after a connection.
I am experiencing the issue since I started playing with the software.
Now, I am using a VPS based on openvz, so it's using a shared kernel and I suspect the issue might be related to this:
net.ipv4.tcp_tw_reuse = 1
(I cannot change that...)
So, the kernel is trying to re-use the existing socket.
Synchronet after a disconnection will open a new socket but given there is an active connection (time_wait) the software just crashes.
tcp 0 0 185.5.52.214:2323 81.102.236.197:62880
TIME_WAIT 691/sbbs
That's the connection state when the telnet service dies. The kernel hasn't cleared it up so I have to wait and to run a sbbs restart otherwise the only service left will be ssh (which works correctly. I have never found any issue with that one..)
APologies as I cannot change that kernel flag given the restrictions over the kernel, and from the top of my hear that's my theory (I might be wrong there).
Any errors..::
Thu May 03 2018 07:52 am bbs.unicyber.co.uk
term 0005 !ERROR 98 binding Telnet Server socket to port 2323
Thu May 03 2018 07:52 am bbs.unicyber.co.uk
term 0005 !ERROR 98 binding Telnet Server socket to port 2323
Thu May 03 2018 07:52 am bbs.unicyber.co.uk
term 0005 !ERROR 98 binding Telnet Server socket to port 2323
Thu May 03 2018 08:58 am bbs.unicyber.co.uk
term 0005 !ERROR 98 binding Telnet Server socket to port 2323
Some more logs:
------
May 3 20:40:29 34819 synchronet: term Done waiting for events thread to terminate
May 3 20:40:29 34819 synchronet: term Terminal Server thread terminating
May 3 20:40:29 34819 synchronet: term 0004 Telnet Server closing socket 185.5.52.214 port 2323
May 3 20:40:29 34819 synchronet: term 0005 RLogin Server closing socket 127.0.0.1 port 5130
May 3 20:40:29 34819 synchronet: term 0007 SSH Server closing socket 185.5.52.214 port 2424
May 3 20:40:29 34819 synchronet: term 0010 Spy Socket closing socket localspy1.sock port 0
May 3 20:40:29 34819 synchronet: term 0011 Spy Socket closing socket localspy2.sock port 0
May 3 20:40:29 34819 synchronet: term 0012 Spy Socket closing socket localspy3.sock port 0
May 3 20:40:29 34819 synchronet: term 0013 Spy Socket closing socket localspy4.sock port 0
May 3 20:40:29 34819 synchronet: term 0014 Spy Socket closing socket localspy5.sock port 0
May 3 20:40:29 34819 synchronet: term 0016 Spy Socket closing socket localspy6.sock port 0
May 3 20:40:29 34819 synchronet: term 0015 Spy Socket closing socket localspy7.sock port 0
May 3 20:40:29 34819 synchronet: term 0017 Spy Socket closing socket localspy8.sock port 0
May 3 20:40:29 34819 synchronet: term 0018 Spy Socket closing socket localspy9.sock port 0
May 3 20:40:29 34819 synchronet: term 0019 Spy Socket closing socket localspy10.sock port 0
May 3 20:40:29 34819 synchronet: term Recycling server...
May 3 20:40:31 34819 synchronet: Reading /home/bbs/sbbs/ctrl/sbbs.ini
May 3 20:40:31 34819 synchronet: term Synchronet Terminal Server Version 3.17 Revision A
May 3 20:40:31 34819 synchronet: term Compiled Apr 27 2018 08:15:16 with GCC 4.8.5
May 3 20:40:31 34819 synchronet: term Initializing on Thu May 3 20:40:31 2018 with options: 1032
May 3 20:40:31 34819 synchronet: term Loading configuration files from /home/bbs/sbbs/ctrl/
May 3 20:40:31 34819 synchronet: term Verifying/creating data directories
May 3 20:40:31 34819 synchronet: term Verifying/creating node directories
May 3 20:40:31 34819 synchronet: term Telnet Server listening on socket 185.5.52.214 port 2323
May 3 20:40:31 34819 synchronet: term 0004 !ERROR 98 binding Telnet Server socket to port 2323
May 3 20:40:31 34819 synchronet: term 0004 Will retry in 15 seconds (1 of 2)
May 3 20:40:46 34819 synchronet: term 0004 !ERROR 98 binding Telnet Server socket to port 2323
May 3 20:40:46 34819 synchronet: term 0004 Will retry in 15 seconds (2 of 2) May 3 20:41:01 34819 synchronet: term 0004 !ERROR 98 binding Telnet Server socket to port 2323
May 3 20:41:01 34819 synchronet: term RLogin Server listening on socket 127.0.0.1 port 5130
May 3 20:41:01 34819 synchronet: term SSH Server listening on socket 185.5.52.214 port 2424
May 3 20:41:01 34819 synchronet: term Node 1 local spy using socket localspy1.sock
May 3 20:41:01 34819 synchronet: term Node 2 local spy using socket localspy2.sock
May 3 20:41:01 34819 synchronet: term Node 3 local spy using socket localspy3.sock
May 3 20:41:01 34819 synchronet: term Node 4 local spy using socket localspy4.sock
May 3 20:41:01 34819 synchronet: term Node 5 local spy using socket localspy5.sock
May 3 20:41:01 34819 synchronet: term Node 6 local spy using socket localspy6.sock
May 3 20:41:01 34819 synchronet: term Node 7 local spy using socket localspy7.sock
May 3 20:41:01 34819 synchronet: term Node 8 local spy using socket localspy8.sock
May 3 20:41:01 34819 synchronet: term Node 9 local spy using socket localspy9.sock
May 3 20:41:01 34819 synchronet: term Node 10 local spy using socket localspy10.sock
May 3 20:41:01 34819 synchronet: term Terminal Server thread started for nodes 1 through 10
May 3 20:41:01 34819 synchronet: evnt BBS Events thread started
-----
15 seconds and just 2 retries wasn't enough.
Digital man, would be possible to maybe setup the time/retries as a variable? That might actually be helpful on scenarios like mine.
Many thanks
RainManHood<---
---
þ Synchronet þ UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424