Open revansx opened 5 years ago
jamesmontalvo3
commented
5 years ago How significantly have you modified HAProxy and Apache config? Is HAProxy on a separate server? If it's on a separate server, was it installed with Meza or is it entirely independent?
revansx
commented
5 years ago A MONOLITH install of MEZA was performed on a fresh & pure enterprise RHEL7 image -- The only change to the MEZA's default monolith installation of HAProxy was changes to the haproxy.cfg file to pass all traffic on port 80 and 443 through to Apache effectively eliminating any purpose it servers since it's a monolith installation. -- The only change to the MEZA's default monolith installation of Apache was changes to the httpd.conf file to promote all external traffic to SSL on 443.
Since you and I are in the same organization I can show you if you wish, just let me know.
jamesmontalvo3
commented
5 years ago Can you not post your changes to the config files, anonymizing any specifics?
Environment
RHEL7, Meza 1.30, HAProxy changed from "SSL Termination" to "SSL Passthrough" Apache re-worked to handle all traffic as SSL MEZA deploy modified to never alter HAProxy config or Apache config
Issue details
visiting the page at ./ServerPerformance/space.php results in a message "No Data Available."
Not sure if it is a config issue on my system or a bug. regardless, meza documentation is lean on underlying requirements and troubleshooting for space.php feature. Please help diagnose.