Running stand_it_up.py with RHEL9 host does not work

[alanking]

The following message appears after the testing environment attempts to start rsyslog:

    rsyslog startup failure, child did not respond within startup timeout (60 seconds)

The process is running, it just fails to start up the iRODS server. Please investigate

[trel]

'equivalent' to Rocky9 or AlmaLinux9, yes?

[alanking]

As far as I know, yes

[alanking]

A workaround has been merged.

Please see irods/irods_development_environment#74 for a potential solution that can be used here that involves pre-configuring rsyslog.

[SwooshyCueb]

Sorry, I think there's been a miscommunication. My PR does not solve this particular problem.

I may have a solution, but I'm still investigating.

[alanking]

@SwooshyCueb - My bad. Carry on. :)

[SwooshyCueb]

I have been able to work around this issue on Arch by setting custom LimitNOFILE values in the systemd service units for docker, buildkit, and containerd.
I created /etc/systemd/system/docker.service.d/ulimit.conf, /etc/systemd/system/containerd.service.d/ulimit.conf, and /etc/systemd/system/buildkit.service.d/ulimit.conf with the contents:

[Service]
LimitNOFILE=1024:1048576

I then did systemctl daemon-reload and restarted all three services.

I'm not sure if this will work in EL9, and I can't test it currently. (I was unable to reproduce the issue in a RockyLinux 9 VPS I briefly spun up on Hetzner.) My understanding is that docker has been replaced with podman in EL9, so the unit filenames will almost certainly be different.

[trel]

podman!

need moar abstraction!