Project

General

Profile

Actions

Bug #24406

closed

Rudder doesn't start on AlmaLinux 8

Added by Nicolas CHARLES 8 months ago. Updated 8 months ago.

Status:
Rejected
Priority:
1 (highest)
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

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

Actions #1

Updated by Nicolas CHARLES 8 months ago

  • 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 (highest)
  • 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

Actions #2

Updated by Alexis Mousset 8 months ago

  • Assignee set to Alexis Mousset
Actions #3

Updated by Alexis Mousset 8 months ago

  • 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.

Actions

Also available in: Atom PDF