Created on 10-17-2016 07:05 AM Edited on 03-30-2022 05:06 PM By Anonymous
Description
Issue:
After updating a new worker via yum command, Cloud Health shows HTTPD is not working. However, the worker is running and can be verified on the back end.
Solution:
To properly have the UI represent the correct health label for the worker, check for the following things:
Check permission on the following:
/var/run/httpd
It should be 775, like example
drwxrwxrwx 2 root apache 4.0K Apr 19 15:51 httpd
If the permissions are different than drwxrwxrwx, chown that directory to 775.
Customer may also update using a “yum update” on the new workers. Instead, use phUpdateSystem.sh script to update the packages. This last step may or may not clear the HTTPD down status.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.