Bug #24406
closed
Rudder doesn't start on AlmaLinux 8
Added by Nicolas CHARLES 2 months ago.
Updated 2 months ago.
Category:
System integration
Description
Server installed correctly, there is no error in Jetty logs, but the httpd logs say
[Mon Mar 11 12:21:36.587478 2024] [proxy:error] [pid 39936:tid 140100751058688] (13)Permission denied: AH00957: HTTP: attempt to connect to 127.0.0.1:8080 (localhost) failed
rudder API through localhost:8080 does work, but not throught https://localhost
Disabling selinux solves the issue
- Subject changed from Rudder 8.1 doesn't start on AlmaLinux 8 to Rudder doesn't start on AlmaLinux 8
- Priority changed from N/A to 1
- Target version changed from 8.1.0~beta2 to 7.3.14
Happens with Alma 8.8 and 8.9; on Rudder 7.3, 8.0 and 8.1
With a box totally up to date, and one with a bit older packages
even upgrading and rebooting it don't solve the issue
- Assignee set to Alexis Mousset
- Status changed from New to Rejected
The problem was that the rudder-webapp SELinux module was not loaded due to insufficient RAM:
libsepol.sepol_set_policydb_from_file: can't read binary policy: Cannot allocate memory
Error reading policy /var/lib/selinux/final/targeted/policy/policy.31: Cannot allocate memory
libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned error code 255.
Adding RAM and loading the modules solves the issue. Closing.
Also available in: Atom
PDF
Updated by 
Updated by