So I'm wondering if this is just me (on a Debian 7 VPS through buyVM, aka FranTech aka elcheapo deluxe) or if others have this trouble too.

It's mostly telnet/rlogin/ssh Which I assume are tightly connected in the
code since they are also all enabled/disabled together in the .ini file. However, just now I watched failure messages appear in the syslog for http
and smtp for no apparent reason.

These can be fixed by a /etc/init.d/sbbs restart command, but of course if
I'm not watching it, it can go dark for who knows how long before I attempt a connection and find no answer.

So it's Telnet (rlogin, ssh), usually after a visitor logs off of the BBS;
HTTP and SMTP seemingly at random; crashing. 'netstat -plnt' shows no listeners on the associated ports, it's like they just vanished.

War stories, suggestions, clues on which logs to check (and where they are,
I'm new on Linux), whatever HUGELY appreciated. -----------------------------------------------
Yip, Yip, Yip, Yip, Yip, Yip, Yip, Yip
BANG!
NO TERRIER...
-----------------------------------------------

---
þ Synchronet þ PipeDreams BBS - Burbank, Calif. USA - Earth

Re: Random Server/Listener failures
By: JoyCrusher to All on Fri Mar 18 2016 02:00 am

So I'm wondering if this is just me (on a Debian 7 VPS through buyVM, aka FranTech aka elcheapo deluxe) or if others have this trouble too.

It's mostly telnet/rlogin/ssh Which I assume are tightly connected in the code since they are also all enabled/disabled together in the .ini file. However, just now I watched failure messages appear in the syslog for http

it's probably your vps provider.
---
þ Synchronet þ ::: BBSES.info - free BBS services :::

Re: Random Server/Listener failures
By: JoyCrusher to All on Fri Mar 18 2016 02:00 am

So I'm wondering if this is just me (on a Debian 7 VPS through buyVM, aka FranTech aka elcheapo deluxe) or if others have this trouble too.

It's mostly telnet/rlogin/ssh Which I assume are tightly connected in the code since they are also all enabled/disabled together in the .ini file. However, just now I watched failure messages appear in the syslog for http and smtp for no apparent reason.

These can be fixed by a /etc/init.d/sbbs restart command, but of course if I'm not watching it, it can go dark for who knows how long before I attempt a connection and find no answer.

So it's Telnet (rlogin, ssh), usually after a visitor logs off of the BBS; HTTP and SMTP seemingly at random; crashing. 'netstat -plnt' shows no listeners on the associated ports, it's like they just vanished.

Is the sbbs process still running? If not, there should be a log entry and/or a core-dump of the crash (if there was in fact a crash). More details would be needed to provide any meaningful assistance.

digital man

Synchronet "Real Fact" #30:
The Synchronet IRC server (ircd) was written in JS by Randy Sommerfeld (Cyan). Norco, CA WX: 56.5øF, 89.0% humidity, 3 mph SSE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: Random Server/Listener failures
By: Digital Man to JoyCrusher on Sat Mar 19 2016 00:04:27

Is the sbbs process still running? If not, there should be a log entry and/or a core-dump of the crash (if there was in fact a crash). More details would be needed to provide any meaningful assistance.

Yes, sbbs is still running. What will happen is that I'll attempt to telnet in and can connect. So I'll try to use the website, and it will load and run fine. If I connect via SSH to the server and do a 'netstat -plnt' I can see all the other listeners still in place and credited to 'sbbs' but there will be no listener on 23, 513, or 10000 (I moved the SBBS SSH port to 10000 because as a VPS there was already SSHD on 22).

If I then look at /var/log/syslog I can see that on the last telnet disconnect there is a following entry that says 'failure for localhost Telnet 1458171980 localhost' (That's from an actual recient failure).

Sometimes '/etc/init.d/bbs recycle' will get the telnet back up, other times I have to go with 'etc/init.d/bbs restart'

If there's a log file you need to see, or have me set up to collect data, please let me know and I'll provide it. (Debian 7, SBBS 3.16, although 3.17 also had this sucidal telnet).

-----------------------------------------------
Yip, Yip, Yip, Yip, Yip, Yip, Yip, Yip
BANG!
NO TERRIER...
-----------------------------------------------

---
þ Synchronet þ PipeDreams BBS - Burbank, Calif. USA - Earth

Re: Random Server/Listener failures
By: JoyCrusher to Digital Man on Sat Mar 19 2016 14:14:38

Yes, sbbs is still running. What will happen is that I'll attempt to telnet in and can connect. So I'll try to use the website, and it will load and run fine. If I connect via SSH to the server and do a 'netstat -plnt' I can

TYPO - shoud be ...telnet in an can't connect. So.... -----------------------------------------------
Yip, Yip, Yip, Yip, Yip, Yip, Yip, Yip
BANG!
NO TERRIER...
-----------------------------------------------

---
þ Synchronet þ PipeDreams BBS - Burbank, Calif. USA - Earth

Re: Random Server/Listener failures
By: JoyCrusher to Digital Man on Sat Mar 19 2016 02:14 pm

Re: Random Server/Listener failures
By: Digital Man to JoyCrusher on Sat Mar 19 2016 00:04:27

Is the sbbs process still running? If not, there should be a log entry and/or a core-dump of the crash (if there was in fact a crash). More details would be needed to provide any meaningful assistance.

Yes, sbbs is still running. What will happen is that I'll attempt to telnet in and can connect. So I'll try to use the website, and it will load and run fine. If I connect via SSH to the server and do a 'netstat -plnt' I can see all the other listeners still in place and credited to 'sbbs' but there will be no listener on 23, 513, or 10000 (I moved the SBBS SSH port to 10000 because as a VPS there was already SSHD on 22).

If I then look at /var/log/syslog I can see that on the last telnet disconnect there is a following entry that says 'failure for localhost Telnet 1458171980 localhost' (That's from an actual recient failure).

Can you please paste the actual complete error message from the log?

If there's a log file you need to see, or have me set up to collect data, please let me know and I'll provide it. (Debian 7, SBBS 3.16, although 3.17 also had this sucidal telnet).

Just the relevant snippets from your syslog output should do it.

digital man

Synchronet "Real Fact" #33:
The back-up synchro.net nameserver and CVS repository is hosted by Deuce. Norco, CA WX: 73.0øF, 56.0% humidity, 5 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

JoyCrusher wrote to Digital Man <=-

Yes, sbbs is still running. What will happen is that I'll attempt to telnet in and can connect. So I'll try to use the website, and it will load and run fine. If I connect via SSH to the server and do a
'netstat -plnt' I can see all the other listeners still in place and credited to 'sbbs' but there will be no listener on 23, 513, or 10000
(I moved the SBBS SSH port to 10000 because as a VPS there was already SSHD on 22).

I've had similar issues in the past, haven't noticed it for a while though. I'm running SBBS 3.16 on Raspian Wheezy on a Pi 1B+


... What?! I'm missing Star Tre$#%$^ NO CARRIER
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net