After upgrade from Ubuntu 22.04 to 24.04: rush suddenly throws error "/etc/rush.rc:9: Unbekannte Begrenzung: 10r20"

Support and Help
1

After upgrade from Ubuntu 22.04 LTS to 24.04 LTS we suddenly see the following rush error:

Mar 11 13:46:04 ra rush[3128]: Veraltete eingebaute Konfigurationsdatei /etc/rush.rc wird eingelesen
Mar 11 13:46:04 ra rush[3128]: Debug-Level auf 1 gesetzt
Mar 11 13:46:04 ra rush[3128]: /etc/rush.rc:9: Unbekannte Begrenzung: 10r20

The “/etc/rush.rc” file looks like this, which I think is okay:

# Set verbosity level.
debug 1

#
# Default settings
#
rule default
  acct on
  limits t10r20
  umask 002
  env - USER LOGNAME HOME PATH
  fall-through

For reference:
https://manpages.ubuntu.com/manpages/noble/man5/rush.rc.5.html

So, it would seem that rush suddenly discards the first charfacter of the limits parameter? :thinking:

Note: We use rush to limit a specific remote SSH user to just be able to use SFTP but not do anything else on the machine; as part of our security policy. The “problematic” line in the rush.rc is from the default rush configuration file, and has not been changed by us at all.

The exactly same configuration has been working fine in Ubuntu 22.04.

How do I fix this, please? :sweat_smile:

2

For reference:

3

Maybe it is related to :thinking:
https://git.gnu.org.ua/rush.git/commit/?id=109ecb1df4bac34e7fdeb97e38e18e48d3ee2da3

4

Any opinions on this issue?

It all seems that this is a serious regression in Ubuntu 24.04. How can we get this fixed ASAP?

5

Almost two weeks later we are still waiting for a regession fix! :face_with_raised_eyebrow:

(or at least for the regession to be acknowledged)

6

You are aware that this is a community of volunteers giving you support here ?

If you want SLAs for issues, you should rather move to paid support by Canonical to get such type of service…

7

In addition to what @ogra wrote, discussion about bugs needs to happen in the bug reports. A support site is no place for discussion about bug reports except under a certain set of circumstances. Posting the bug report here, with the intent of attracting more attention to it, does nothing to fix it.

If anybody has the same bug, they can go to the linked bug and click the yellow circle next to “Does this bug affect you?”

Since this is a bug (more than one person affected), I’m closing this topic to encourage discussion about the bug (troubleshooting, etc.) to happen in the bug tracker.