Project

General

Profile

Actions
Copy link

Bug #10372

closed

On Centos 7.3, upgrading from 4.0 to 4.1 fail due to SELinux problem

Added by Nicolas CHARLES over 7 years ago. Updated over 7 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Packaging
Target version:
4.1.0
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

During upgrade from 4.0 to 4.1, I got the following errors

/etc/selinux/final/targeted/contexts/files/file_contexts: Multiple same specifications for /opt/rudder/etc/uuid.hive.
/etc/selinux/final/targeted/contexts/files/file_contexts: Multiple same specifications for /var/log/rudder/apache2(/.*)?.
/etc/selinux/final/targeted/contexts/files/file_contexts: Multiple same specifications for /var/rudder/inventories/incoming.
/etc/selinux/final/targeted/contexts/files/file_contexts: Multiple same specifications for /var/rudder/inventories/accepted-nodes-updates.
/etc/selinux/final/targeted/contexts/files/file_contexts: Invalid argument
libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned error code 1.
semodule:  Failed!

meanwhile, semodule was using 100% CPU

Then, https failed to start, cause is:

(13)Permission denied: AH00091: httpd: could not open error log file /var/log/rudder/apache2/error.log.
AH00015: Unable to open logs

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #9913: Add SELinux config to relay packageReleasedBenoît PECCATTEActions
Related to Rudder - Bug #10426: Apache not started on a fresh centos7 install (selinux problem)ReleasedBenoît PECCATTEActions
Actions
Copy link

Also available in: Atom PDF