SPLX web console cannot be accessed after installation in RHEL 8.3.
The following shows splxhttpd service status:
# /etc/init.d/splxhttpd status
Splxhttpd (pid 2352) is running.
When checking the status using Perl command:
# perl /etc/init.d/splxhttpd status
Splxhttpd is dead, but the subsys is locked. The subsys path is '/var/lock/subsys/splxhttpd'.
After this, splxhttpd is able to start, and the problem is resolved.
# perl /etc/init.d/splxhttpd start
Starting splxhttpd: [ OK ]
ServerProtect for Linux httpd started.
# rpm -qa | grep procps-ng
procps-ng-3.3.15-3.el8.x86_64
This issue is caused by the 'pidof' command being included in 'procps-ng' package in version 3.3.15-3 which acts differently with other older versions.
Normally, when the splxhttpd calls "pidof splxhttpd", it will not return the PID itself. After upgrading 'procps-ng', it shows that the system recognizes the httpd being called, so it will not continue to execute /opt/TrendMicro/SProtectLinux/SPLX.httpd/bin/splxhttpd.
However, when you execute "perl /etc/init.d/splxhttpd start", the system will not get the PID of the process, because "perl" runs the script, and not "splxhttpd". As a result, it will continue to execute /opt/TrendMicro/SProtectLinux/SPLX.httpd/bin/splxhttpd.
Since the upgrade of RHEL 8.3 to 'procps-ng 3.3.15-3' by default, customers easily encounter this issue when installing SPLX normally.
If customers upgrade 'procps-ng' to version 3.3.15-3 on other Red Hat later themselves, they may also encounter this problem.
To resolve this issue choose between these two methods
- Roll back the 'procps-ng' package to the version 3.3.15-1.
- Apply Hot Fix Build 1639.
