Due to SELinux behavior change in RHEL 8.x, a system that enforce enforces SELinux policy might result in DPOD services not running after server rebootfailing to start.
The following log records (or similar) might be found in the system log (/var/log/messages):
| Code Block | ||||
|---|---|---|---|---|
| ||||
17:53:19 server1 MonTier[3159]: Starting MonTier in background: /etc/rc.d/init.d/MonTier: line 539: /app/MonTier_start.pid: Permission denied 17:53:19 server1 systemd[1]: Started LSB: This service manages MonTier products on the system. 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier: line 109: /logs/montier_server/montier.init.log: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier: line 110: /logs/montier_server/montier.init.log: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier: line 134: /logs/montier_server/montier.init.log: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier: line 140: /logs/montier_server/montier.init.log: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier_functions: line 270: /bin/su: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier: line 140: /logs/montier_server/montier.init.log: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier_functions: line 270: /bin/su: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier: line 140: /logs/montier_server/montier.init.log: Permission denied 17:53:19 server1 MonTier[3159]: /etc/rc.d/init.d/MonTier_functions: line 270: /bin/su: Permission denied |
Consult your RHEL System Administrator system administrator regarding needed changes in SELinux configuration.
Example of the SELinux behavior change could be found in the following following Red hat Hat tech note.