Hey DM,

First,

I seem to be having an issue with smbutil. While using what I believe is the default timed event to execute "%!smbutil%. -C Rmp1000 *.shd", and even when I run it from the command line, I get this:

Scanning for pre-flagged messages...
100% (0 pre-flagged for deletion)
Scanning for read messages to be killed...
100% (0 flagged for deletion due to read status) /home/axisd/sbbs/data/subs/sync locked successfully
Packing /home/axisd/sbbs/data/subs/sync
Analyzing /home/axisd/sbbs/data/subs/sync
Already compressed.

/home/axisd/sbbs/data/subs/sync unlocked successfully

All of my sub-boards are set to 2000 messages and 365 days old. However, sub-board "SYNC" above has 12,340 messages in it. It said it packed it, but
it doesn't seem to actually be doing it.. That holds true for every sub-board containing more than 2000 messages.

Second,

I'm getting a couple errors in my system log that seems to happen every time an event is ran:

!setregid FAILED with error 1 (Operation not permitted)
!setreuid FAILED with error 1 (Operation not permitted)

Not sure what that's about, or if it has anything to do with the above issue. Any insight would be helpful.

Regards,
Nick
---
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: smbutil
By: Accession to All on Tue Aug 29 2023 05:23 pm

Hey DM,

First,

I seem to be having an issue with smbutil. While using what I believe is the default timed event to execute "%!smbutil%. -C Rmp1000 *.shd",

I'm not clear why you're using the 'R' command (Re-initialize SMB status header) - that's not a normal command you should be using. And you shouldn't be using the -C option unless you're repairing a corrupted message base.

and even when
I run it from the command line, I get this:

Scanning for pre-flagged messages...
100% (0 pre-flagged for deletion)
Scanning for read messages to be killed...
100% (0 flagged for deletion due to read status) /home/axisd/sbbs/data/subs/sync locked successfully
Packing /home/axisd/sbbs/data/subs/sync
Analyzing /home/axisd/sbbs/data/subs/sync
Already compressed.

/home/axisd/sbbs/data/subs/sync unlocked successfully

All of my sub-boards are set to 2000 messages and 365 days old. However, sub-board "SYNC" above has 12,340 messages in it. It said it packed it, but it doesn't seem to actually be doing it.. That holds true for every sub-board containing more than 2000 messages.

I suspect your use of the 'R' command has corrupted the SMB status header for the message bases, where the max messages value is stored. Don't do that. Running 'scfg -a' should repair those SMB status headers. You can use 'smbutil s' to view them and confirm the max msgs and max age values are set correctly after running 'scfg -a'.

Second,

I'm getting a couple errors in my system log that seems to happen every time an event is ran:

!setregid FAILED with error 1 (Operation not permitted)
!setreuid FAILED with error 1 (Operation not permitted)

Not sure what that's about, or if it has anything to do with the above issue. Any insight would be helpful.

Seems totally unrelated. Maybe you're starting sbbs as root?
--
digital man (rob)

Synchronet/BBS Terminology Definition #13:
CBM = Commodore Business Machines
Norco, CA WX: 98.8øF, 28.0% humidity, 5 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: smbutil
By: Digital Man to Accession on Tue Aug 29 2023 03:45 pm

I seem to be having an issue with smbutil. While using what I believe
is the default timed event to execute "%!smbutil%. -C Rmp1000 *.shd",

I'm not clear why you're using the 'R' command (Re-initialize SMB status header) - that's not a normal command you should be using. And you shouldn't be using the -C option unless you're repairing a corrupted message base.

Probably something I added in from the wiki when there was corrupted sub-boards. Has since been fixed and I've now changed it to what the wiki suggests.

I suspect your use of the 'R' command has corrupted the SMB status header for the message bases, where the max messages value is stored. Don't do that. Running 'scfg -a' should repair those SMB status headers. You can use 'smbutil s' to view them and confirm the max msgs and max age values are set correctly after running 'scfg -a'.

'scfg -a' brings me into SCFG, where I changed the timed event to reflect the wiki (smbutil mp100 /path/to/sbbs/data/subs/*.shd), saved and exited. Also ran 'scfg -a' multiple times to see if anything was logged, nothing. Just brings me into what seems like a normal SCFG session.

Then I ran 'smbutil s /path/to/sbbs/data/subs/*.shd' and it showed this:

Opening /home/axisd/sbbs/data/subs/syncprog
last_msg =12664
total_msgs =12664
header_offset =32
max_crcs =0
max_msgs =0
max_age =0
attr =0002h
Opening /home/axisd/sbbs/data/subs/sync
last_msg =51726
total_msgs =51724
header_offset =32
max_crcs =0
max_msgs =0
max_age =0
attr =0002h

Every sub-board has max_msgs=0 and max_age=0, so maybe 'scfg -a' didn't take?

I double checked SCFG > Message Areas > Fidonet > Message Sub-Boards > SYNC_SYS (as well as a quick peek at random other ones to make sure it was set throughout) Maximum Messages is set to 2000, and Purge by Age is set to 'Enabled (365 days old)'. These are the common settings throughout all of my sub-boards.

!setregid FAILED with error 1 (Operation not permitted)
!setreuid FAILED with error 1 (Operation not permitted)

Not sure what that's about, or if it has anything to do with the above
issue. Any insight would be helpful.

Seems totally unrelated. Maybe you're starting sbbs as root?

I start sbbs on boot through systemd. In sbbs.ini under 'User/group name to run as' I have my user and group (not root). I don't seem to have any permissions conflicts whatsoever. 'top -c' says /home/axisd/sbbs/sbbs d is being run by my user, not root.

Regards,
Nick
---
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: smbutil
By: Accession to Digital Man on Tue Aug 29 2023 09:06 pm

Re: smbutil
By: Digital Man to Accession on Tue Aug 29 2023 03:45 pm

I seem to be having an issue with smbutil. While using what I believe
is the default timed event to execute "%!smbutil%. -C Rmp1000 *.shd",

I'm not clear why you're using the 'R' command (Re-initialize SMB status header) - that's not a normal command you should be using. And you shouldn't be using the -C option unless you're repairing a corrupted message base.

Probably something I added in from the wiki when there was corrupted sub-boards. Has since been fixed and I've now changed it to what the wiki suggests.

I suspect your use of the 'R' command has corrupted the SMB status header for the message bases, where the max messages value is stored. Don't do that. Running 'scfg -a' should repair those SMB status headers. You can use 'smbutil s' to view them and confirm the max msgs and max age values are set correctly after running 'scfg -a'.

'scfg -a' brings me into SCFG, where I changed the timed event to reflect the wiki (smbutil mp100 /path/to/sbbs/data/subs/*.shd), saved and exited. Also ran 'scfg -a' multiple times to see if anything was logged, nothing. Just brings me into what seems like a normal SCFG session.

Then I ran 'smbutil s /path/to/sbbs/data/subs/*.shd' and it showed this:

Opening /home/axisd/sbbs/data/subs/syncprog
last_msg =12664
total_msgs =12664
header_offset =32
max_crcs =0
max_msgs =0
max_age =0
attr =0002h
Opening /home/axisd/sbbs/data/subs/sync
last_msg =51726
total_msgs =51724
header_offset =32
max_crcs =0
max_msgs =0
max_age =0
attr =0002h

Every sub-board has max_msgs=0 and max_age=0, so maybe 'scfg -a' didn't take?

If you don't make any message area configuration changes, that would be expected.

Use the '-f' (force save) option as well: 'scfg -f -a' and then upon exiting SCFG, it should automatically update the config files and all the message base headers.

I double checked SCFG > Message Areas > Fidonet > Message Sub-Boards > SYNC_SYS (as well as a quick peek at random other ones to make sure it was set throughout) Maximum Messages is set to 2000, and Purge by Age is set to 'Enabled (365 days old)'. These are the common settings throughout all of my sub-boards.

'scfg -f -a' should fix the message bases to align again with your configuration.

!setregid FAILED with error 1 (Operation not permitted)
!setreuid FAILED with error 1 (Operation not permitted)

Not sure what that's about, or if it has anything to do with the above
issue. Any insight would be helpful.

Seems totally unrelated. Maybe you're starting sbbs as root?

I start sbbs on boot through systemd. In sbbs.ini under 'User/group name to run as' I have my user and group (not root). I don't seem to have any permissions conflicts whatsoever. 'top -c' says /home/axisd/sbbs/sbbs d is being run by my user, not root.

Remove the user/group settings in the [unix] section of sbbs.ini in that case. --
digital man (rob)

Rush quote #2:
If the future's looking dark, we're the ones who have to shine.
Norco, CA WX: 93.5øF, 29.0% humidity, 4 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: smbutil
By: Digital Man to Accession on Wed Aug 30 2023 11:43 am

Use the '-f' (force save) option as well: 'scfg -f -a' and then upon exiting SCFG, it should automatically update the config files and all the message base headers.

That did the trick. Although it gave me an error that it couldn't save to sbbs.ini. Opened sbbs.ini with nano, put a space on a random empty line and saved as the same user and it saved/exited, so not sure what's going on there. However, I didn't need to save anything to sbbs.ini at this point anyway. ;)

'scfg -f -a' should fix the message bases to align again with your configuration.

Definitely did, and smbutil mp100 *.shd worked it's magic afterwards.

I start sbbs on boot through systemd. In sbbs.ini under 'User/group
name to run as' I have my user and group (not root). I don't seem to
have any permissions conflicts whatsoever. 'top -c' says
/home/axisd/sbbs/sbbs d is being run by my user, not root.

Remove the user/group settings in the [unix] section of sbbs.ini in that case.

I actually tried a different route, but similar. Instead, I took a look at the latest sbbs.service on the wiki and noticed I wasn't specifying a user and group in mine, so I added my user and group to that, restarted sbbs and haven't seen the error since. *shrug*

Is it still safe to remove the user/group setting from the [unix] section of sbbs.ini? Or should I leave it the hell alone now that it's working? ;)

Thanks for the help!

Regards,
Nick

... He who laughs last probably didn't get the joke.
---
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: smbutil
By: Accession to Digital Man on Wed Aug 30 2023 05:06 pm

Re: smbutil
By: Digital Man to Accession on Wed Aug 30 2023 11:43 am

Use the '-f' (force save) option as well: 'scfg -f -a' and then upon exiting SCFG, it should automatically update the config files and all the message base headers.

That did the trick. Although it gave me an error that it couldn't save to sbbs.ini.

Ah, thanks for the report. That's now fixed.

Opened sbbs.ini with nano, put a space on a random empty line and
saved as the same user and it saved/exited, so not sure what's going on there. However, I didn't need to save anything to sbbs.ini at this point anyway. ;)

'scfg -f -a' should fix the message bases to align again with your configuration.

Definitely did, and smbutil mp100 *.shd worked it's magic afterwards.

I start sbbs on boot through systemd. In sbbs.ini under 'User/group
name to run as' I have my user and group (not root). I don't seem to
have any permissions conflicts whatsoever. 'top -c' says
/home/axisd/sbbs/sbbs d is being run by my user, not root.

Remove the user/group settings in the [unix] section of sbbs.ini in that case.

I actually tried a different route, but similar. Instead, I took a look at the latest sbbs.service on the wiki and noticed I wasn't specifying a user and group in mine, so I added my user and group to that, restarted sbbs and haven't seen the error since. *shrug*

Is it still safe to remove the user/group setting from the [unix] section of sbbs.ini? Or should I leave it the hell alone now that it's working? ;)

I'd remove the user/group settings from sbbs.ini - they were only for use in scenarios where you need sbbs to change the effective user/group. Since you're using Linux capabilities (I assume), you don't need to start sbbs as root, so you don't need sbbs to change identities.
--
digital man (rob)

This Is Spinal Tap quote #42:
What day the Lord created Spinal Tap and couldn't he have rested on that day? Norco, CA WX: 90.4øF, 40.0% humidity, 8 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)