Hey DM,

Now that I've started using the 'User' and 'Group' keywords in sbbs.service, I started receiving some new errors, and just want to make sure what I have done, or would like to do is a proper way of solving it:

Sep 09 10:21:20 reaper systemd[1]: sbbs.service: Got notification message from PID 13482, but reception only permitted for main PID which is currently not known
Sep 09 10:21:20 reaper systemd[1]: sbbs.service: Got notification message from PID 13484, but reception only permitted for main PID which is currently not known

With the above errors, and after a quick search found that there may be an issue with systemd and notifying of starting forking applications. Setting 'NotifyAccess=all' instead of 'NotifyAccess=main' (which is in the current sbbs.service file provided in the repo and on the wiki) seems to have fixed it. Hopefully that one is more of an FYI and I'm not doing something I shouldn't. ;)

Sep 09 10:21:20 reaper synchronet[13484]: !ERROR 13 (Permission denied) creating/opening /var/run/sbbs.pid

With this one, I haven't done anything yet. My question I guess, is now that I'm not using systemd to start sbbs as root and switching to a user via sbbs.ini, should I change the 'PidFile=' option in sbbs.ini to use something like '/sbbs/ctrl/sbbs.pid' instead? If not, where would be the proper location to set that?

Sep 09 10:21:20 reaper synchronet[13484]: !Started as non-root user (id 1000): May fail to bind TCP/UDP ports below 1024

Lastly, this one I'm assuming I might just have to ignore, since that's a legit warning that I probably can't do anything about? I'm using the repo provided sbbs.service file which uses 'AmbientCapabilities=CAP_NET_BIND_SERVICE', am not using sbbs.ini to run/switch to a user any more (as we previously discussed), and am compiling with 'make DEBUG=1 setcap symlink' as the wiki suggests (obviously 'debug' in place of 'release' by choice). With all of this in place and my router settings, I'm binding to ports lower than 1024 just fine. Just figured I'd ask about it in case maybe there is another way to get rid of it I haven't figured out yet.

Regards,
Nick

... Don`t force it, get a larger hammer.
---
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: sbbs.service
By: Accession to All on Sat Sep 09 2023 10:47 am

Hey DM,

Now that I've started using the 'User' and 'Group' keywords in sbbs.service, I started receiving some new errors, and just want to make sure what I have done, or would like to do is a proper way of solving it:

Sep 09 10:21:20 reaper systemd[1]: sbbs.service: Got notification message from PID 13482, but reception only permitted for main PID which is currently not known
Sep 09 10:21:20 reaper systemd[1]: sbbs.service: Got notification message from PID 13484, but reception only permitted for main PID which is currently not known

With the above errors, and after a quick search found that there may be an issue with systemd and notifying of starting forking applications. Setting 'NotifyAccess=all' instead of 'NotifyAccess=main' (which is in the current sbbs.service file provided in the repo and on the wiki) seems to have fixed it. Hopefully that one is more of an FYI and I'm not doing something I shouldn't. ;)

Ah, thanks for the head's up. I'm seeing that same message in my syslog output. Perhaps that started with a systemd update, but your fix seems fine. I'll make that change in Git as well.

Sep 09 10:21:20 reaper synchronet[13484]: !ERROR 13 (Permission denied) creating/opening /var/run/sbbs.pid

With this one, I haven't done anything yet. My question I guess, is now that I'm not using systemd to start sbbs as root and switching to a user via sbbs.ini, should I change the 'PidFile=' option in sbbs.ini to use something like '/sbbs/ctrl/sbbs.pid' instead? If not, where would be the proper location to set that?

sbbs doesn't use the PID file, so it can be whatever you like. It's a harmless warning message, but you change the path to some place your sbbs process has permission to write to get rid of it.

Sep 09 10:21:20 reaper synchronet[13484]: !Started as non-root user (id 1000): May fail to bind TCP/UDP ports below 1024

Lastly, this one I'm assuming I might just have to ignore, since that's a legit warning that I probably can't do anything about?

Correct.

I'm using the repo
provided sbbs.service file which uses 'AmbientCapabilities=CAP_NET_BIND_SERVICE', am not using sbbs.ini to run/switch to a user any more (as we previously discussed), and am compiling with 'make DEBUG=1 setcap symlink' as the wiki suggests (obviously 'debug' in place of 'release' by choice). With all of this in place and my router settings, I'm binding to ports lower than 1024 just fine. Just figured I'd ask about it in case maybe there is another way to get rid of it I haven't figured out yet.

I live with that warning message (and systemd status) message myself. I've pondered getting rid of it, but I suppose it might be still helpful for some *nix sysops that are not using our same systemd setup:

sbbs.service - Synchronet BBS
Loaded: loaded (/lib/systemd/system/sbbs.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/sbbs.service.d
??override.conf
Active: active (running) since Wed 2023-09-06 10:59:16 PDT; 2 days ago
Docs: http://wiki.synchro.net/
Process: 2555007 ExecStart=/sbbs/exec/sbbs d (code=exited, status=0/SUCCESS)
Main PID: 2555008 (sbbs)
Status: "!Started as non-root user (id 1001): May fail to bind TCP/UDP ports below 1024"
--
digital man (rob)

Breaking Bad quote #28:
Gomey, got beat your pinata. - Hank Schrader
Norco, CA WX: 85.9øF, 34.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: sbbs.service
By: Digital Man to Accession on Sat Sep 09 2023 09:52 am

Ah, thanks for the head's up. I'm seeing that same message in my syslog output. Perhaps that started with a systemd update, but your fix seems fine. I'll make that change in Git as well.

Right on.

sbbs doesn't use the PID file, so it can be whatever you like. It's a harmless warning message, but you change the path to some place your sbbs process has permission to write to get rid of it.

Perfect, and easy enough.

I live with that warning message (and systemd status) message myself. I've pondered getting rid of it, but I suppose it might be still helpful for some *nix sysops that are not using our same systemd setup:

Yeah, this one is more kind of expected than the rest.

Status: "!Started as non-root user (id 1001): May fail to bind TCP/UDP ports below 1024" --

Mine says the same, so good to know I'm in the right book and close to the same page now. Thanks! ;)

Regards,
Nick

... There's no intelligent life down here.
---
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)