Open shubhammishra9 opened 2 years ago
Please check SElinux config or disable it temporary.
Issue resolved after disabling SELinux
We may have to add this step as prerequisite in documentation.
@464d41 and @yoctoserge please check and close this if no action needed.
Observed if we download and keep same policy file in app protect config path and use it, nginx service will not come up. Tried Work arounds:
Error Message:
Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal nginx[9246]: { Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal nginx[9246]: "completed_successfully" : false, Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal nginx[9246]: "error_message" : "Failed to read /etc/app_protect/conf/waf-1632197961021.json (Permission denied) at /opt/app_protect/bin/../lib/perl/F5/Utils/File.pm line 238.\n", Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal nginx[9246]: "error_line_number" : 23 Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal nginx[9246]: } Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal nginx[9246]: nginx: [error] APP_PROTECT { "event": "configuration_load_failure", "software_version": "3.639.0", "error_message":"Failed to read /etc/app_protect/conf/waf-1632197961021.json (Permission denied) at /opt/app_protect/bin/../lib/perl/F5/Utils/File.pm line 238.\n","completed_successfully":false,"error_line_number":23} Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal systemd[1]: nginx.service: control process exited, code=exited status=1 Sep 21 04:32:30 ip-172-31-21-251.ap-south-1.compute.internal systemd[1]: Failed to start NGINX Plus - high performance web server.