Hi All,

This is driving me $%%&^%& insane.......

I know its not an SBBS issue, but I was wondering, has anyone here tried to install SBBS on a modern
systemd based linux ditto like Centos 7?

I am currently trying to upgrade "The Dungeon BBS" from Centos 6.5 based to Centos 7 Based because the
current subs code refuses to compile under Centos 6.5. It compiles perfectly under Centos 7. I seem to have
everything ready to go, but when I start sobs, it is completely unable to Bind to all the ports for its Listening
services. Such as 25, 21, 2200, 2300, 6669 etc.

At first I thought selinux.... So I disabled that for now....... NOPE.

Then I thought .... Maybe the Firewall, Though that shouldn't stop binds as root..... NOPE.

I and almost 99 % sure it is the new systemd $%^#^% that is somehow blocking it, but the docs is immensely
confusing, and the google searches very vague and non specific.

systemd wants to control every bloody thing, but I just want to be able to start the subs executable and have
it bind to ports. Apparently that is no longer allowed in Linux.......!!!!! %$#$%^%%^$

Anyhow anyone else tried??
--------------------------------------
Regards........Geo
oooOOOooo

---
* Synchronet * The Dungeon BBS - Risen from the ashes! - Canberra, Australia
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Install on New systemd based Linux distress?
By: Geo to All on Tue Mar 20 2018 02:29 pm

This is driving me $%%&^%& insane.......

I know its not an SBBS issue, but I was wondering, has anyone here tried to install SBBS on a modern
systemd based linux ditto like Centos 7?

I've been running on CentOS 7 for about a year and a half now.

I am currently trying to upgrade "The Dungeon BBS" from Centos 6.5 based to Centos 7 Based because the
current subs code refuses to compile under Centos 6.5. It compiles perfectly under Centos 7. I seem to have

Erm, the latest CentOS 6.x version is 6.9. have you done a full "yum update" before going the route of moving to CentOS 7?

everything ready to go, but when I start sobs, it is completely unable to Bind to all the ports for its Listening
services. Such as 25, 21, 2200, 2300, 6669 etc.

Do you have an FTP server running in CentOS 7? or osmething else using those ports?

At first I thought selinux.... So I disabled that for now....... NOPE.

Always a good idea. selinux causes more problems than it solves IMO.

Then I thought .... Maybe the Firewall, Though that shouldn't stop binds as root..... NOPE.

Correct, that's not going to stop things from binding. Especially if you're running it as root.

I and almost 99 % sure it is the new systemd $%^#^% that is somehow blocking it, but the docs is immensely
confusing, and the google searches very vague and non specific.

systemd shouldn't have anything to do with it. You should be able to fire sbbs up just by running the sbbs executable. Once you know it works, then set up the systemd configs to start/stop SBBS.

Your best bet is to check and see if the ports are already in use. You can see what ports are listening with:

netstat -plnt

sshd is enabled by default in CentOS 7, and other things may be as well, depending upon how you did your install. It's likely that's the issue.


DaiTengu

... To eat is human; to digest divine.

---
* Synchronet * War Ensemble BBS - The sport is war, total war - warensemble.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hi DaiTengu

Nah it was a minimal Centos 7 install plus "Development Tools" Group.

jetstar shows.

[root@Manifold3 ~]# netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 837/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1075/master
tcp6 0 0 :::22 :::* LISTEN 837/sshd
tcp6 0 0 ::1:25 :::* LISTEN 1075/master

ssh is the only thing listening on any port.

Its so weird!!
--------------------------------------
Regards........Geo
oooOOOooo

---
* Synchronet * The Dungeon BBS - Risen from the ashes! - Canberra, Australia
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

[root@Manifold3 ~]# netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 837/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1075/master
tcp6 0 0 :::22 :::* LISTEN 837/sshd
tcp6 0 0 ::1:25 :::* LISTEN 1075/master

ssh is the only thing listening on any port.

Its so weird!!
--------------------------------------

I now suspect it may be somhow related to file ownerships.??

Anyhow it doesn't matter, because a fresh build and configure of SBBS seems to work just
fine. I must have copied something over from the old BBS ctrl dir that threw things into a spin
somehow.

Not to worry, I think I will just do a fresh install and configure from scratch using the data
from the current BBS and import the message and file bases fresh. At least that way I know I
am not mixing old and new configs file versions in SBBS.

8-)

Regards........Geo
oooOOOooo

--------------------------------------
Regards........Geo
oooOOOooo

---
* Synchronet * The Dungeon BBS - Risen from the ashes! - Canberra, Australia
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Install on New systemd based Linux distress?
By: DaiTengu to Geo on Mon Mar 19 2018 23:28:49

Re: Install on New systemd based Linux distress?
By: Geo to All on Tue Mar 20 2018 02:29 pm

This is driving me $%%&^%& insane.......

I know its not an SBBS issue, but I was wondering, has anyone here trie to install SBBS on a modern
systemd based linux ditto like Centos 7?

I've been running on CentOS 7 for about a year and a half now.

I am currently trying to upgrade "The Dungeon BBS" from Centos 6.5 base to Centos 7 Based because the
current subs code refuses to compile under Centos 6.5. It compiles perfectly under Centos 7. I seem to have

Erm, the latest CentOS 6.x version is 6.9. have you done a full "yum updat before going the route of moving to CentOS 7?

everything ready to go, but when I start sobs, it is completely unable Bind to all the ports for its Listening
services. Such as 25, 21, 2200, 2300, 6669 etc.

Do you have an FTP server running in CentOS 7? or osmething else using thos ports?

At first I thought selinux.... So I disabled that for now....... NOPE.

Always a good idea. selinux causes more problems than it solves IMO.

Then I thought .... Maybe the Firewall, Though that shouldn't stop bind as root..... NOPE.

Correct, that's not going to stop things from binding. Especially if you're running it as root.

I and almost 99 % sure it is the new systemd $%^#^% that is somehow blocking it, but the docs is immensely
confusing, and the google searches very vague and non specific.

systemd shouldn't have anything to do with it. You should be able to fire sbbs up just by running the sbbs executable. Once you know it works, then s up the systemd configs to start/stop SBBS.

Your best bet is to check and see if the ports are already in use. You can s what ports are listening with:

netstat -plnt

sshd is enabled by default in CentOS 7, and other things may be as well, depending upon how you did your install. It's likely that's the issue.

DaiTengu

... To eat is human; to digest divine.

Hi DaiTengu,

Ive worked it all out 8-)

Its working nicely now 8-) Thx.


--------------------------------------
Regards........Geo
oooOOOooo
--- SBBSecho 2.27-Linux
* Origin: The Dungeon BBS, Canberra, Australia (3:712/620)

Re: Install on New systemd based Linux distress?
By: Keith Matthews to DaiTengu on Fri Mar 23 2018 12:19 am

Ive worked it all out 8-)

Its working nicely now 8-) Thx.

Awesome, good to hear!

DaiTengu

... Ahh! Come on Erick, just this one last little feature!

---
* Synchronet * War Ensemble BBS - The sport is war, total war - warensemble.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)