Ive sent messages to MarisaG but havent heard back. Im using her free shared server for my BBS. This morning it started getting erros
binding the sockets to the ports, Ive Increased the attempts and the
dleay but still no luck. Since its a remote server Im limited on what
I can do. Its running Linux and all the logs show is the error
binding.
Hello Melkor,Since it was setup by someone not sure on most of that. If I have to manually recycle I ssh in sudo to root and use smc to reset the bbs process.
Ive sent messages to MarisaG but havent heard back. Im using her free shared server for my BBS. This morning it started getting erros
binding the sockets to the ports, Ive Increased the attempts and the dleay but still no luck. Since its a remote server Im limited on what
I can do. Its running Linux and all the logs show is the error
binding.
How are you starting sbbs? You may need to use sudo so sbbs can bind the por Another option is to use setcap or authbind so you can run sbbs as a regular user.
I use the setcap method myself and it works well for me. You'll need to run setcap command on your sbbs binary every time you rebuild it if you use that method.
Info is in the wiki in the how-to pages, look for Linux non-root.
Ttyl :-),
Al
Since it was setup by someone not sure on most of that. If I have to manually recycle I ssh in sudo to root and use smc to reset the bbs process.
On 03-09-20 09:58, Melkor wrote to All <=-
Ive sent messages to MarisaG but havent heard back. Im using her free shared server for my BBS. This morning it started getting erros binding the sockets to the ports, Ive Increased the attempts and the dleay but still no luck. Since its a remote server Im limited on what I can do.
Its running Linux and all the logs show is the error binding.
On 03-09-20 12:15, Al wrote to Melkor <=-
Hello Melkor,
Since it was setup by someone not sure on most of that. If I have to manually recycle I ssh in sudo to root and use smc to reset the bbs process.
In that case since we don't know how sbbs is being started you'll have
to get Marisa to look into it.
Tony Langdon wrote to Melkor <=-
Ive sent messages to MarisaG but havent heard back. Im using her free shared server for my BBS. This morning it started getting erros binding the sockets to the ports, Ive Increased the attempts and the dleay but still no luck. Since its a remote server Im limited on what I can do.
Its running Linux and all the logs show is the error binding.
This usually means one of two things:
1. Something else already has those ports (is there another copy
of sbbs running?). Use "ps aux" to check if sbbs is running, or
use lsof to see what has the ports open. If lsof isn't
available, then the following command will at least tell you if
something is using the ports you want for sbbs:
netstat -lan | grep LISTEN
or
2. sbbs does not have permission to bind the low ports. This
reauires the use of "setcap" as root to fix.
On 03-10-20 08:33, Gamgee wrote to Tony Langdon <=-
Good point here... since this is a "shared server" with MarisaG,
there may indeed be another instance of SBBS running...
or
2. sbbs does not have permission to bind the low ports. This
reauires the use of "setcap" as root to fix.
Well.... it doesn't *require* the use of setcap, there are other
ways. I start my BBS with this command while in the /sbbs/exec
directory: sudo -E ./sbbs syslog
That lets it bind to the low ports (because of 'sudo'), and then
it immediately reverts to a normal user which is specified in the
sbbs.ini file. Seems easier/cleaner to me to do it that way.
Good point here... since this is a "shared server" with MarisaG,If it's a VPS, it shouldn't be an issue, because a VPS acts like an independent machine. If it's truly shared, surely you've been given your own port assignments to use. My suspicion is an instance of your own sbbs that didn't terminate for some reason.
there may indeed be another instance of SBBS running...
On 03-10-20 21:47, Marisag wrote to Tony Langdon <=-
Only one BBS runs on one of my servers. But sometimes a MUD or Minetest server will be running but aside from port 23 and 80/443 will be just
the BBS instance. Often people try and start up another instance of
SBBS rather than killing the process and letting it restart the SBBS process on it's own.
I just put out a smc update that warns people against using that...
I just put out a smc update that warns people against using that...Sounds like a good idea. :)
On 03-11-20 00:51, Marisag wrote to Tony Langdon <=-
Re: Re: Binding Problem
By: Tony Langdon to Marisag on Wed Mar 11 2020 16:16:00
I just put out a smc update that warns people against using that...Sounds like a good idea. :)
Yep :) Took me a while to think of adding that.
Tony Langdon wrote to Gamgee <=-
Good point here... since this is a "shared server" with MarisaG,
there may indeed be another instance of SBBS running...
If it's a VPS, it shouldn't be an issue, because a VPS acts like
an independent machine. If it's truly shared, surely you've been
given your own port assignments to use. My suspicion is an
instance of your own sbbs that didn't terminate for some reason.
On 03-11-20 08:20, Gamgee wrote to Tony Langdon <=-
Well, it's not my issue, this was something that we were replying
to somebody else about... I've lost track of the thread as to who
it was.
All good, hopefully they've got things sorted out now.
I think Marisa is all over it, and is adding warnings for her clients. :)
On 03-12-20 15:59, Paul Quinn wrote to Vk3jed <=-
Hi! Tony,
On 03/12/2020 01:38 PM, yo wrote:
I think Marisa is all over it, and is adding warnings for her clients. :)
Without context, that is the most delicious note I ever saw in Fidonet that was still legal in all states. ;)
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 41:42:03 |
| Calls: | 508 |
| Messages: | 220029 |