Apigee Install Validation Test fails

Hello,

I have a 7 node install of Apigee on a private cloud. I have two nodes running the edge-router and the message processor.

Here are some basic details about the install:

Details of our installation:

OS Version: Red Hat Enterprise Linux Server release 7.3 (Maipo)

Apigee Version: 4.17.01

1. /opt/apigee is owned by the apigee:apigee user and group
2. /opt/nginx is owned by apigee:apigee user and group
3. apigee-edge-router is running as apigee
4. nginx is running as apigee
5. SELinux is set to Permissive

Description of our problem:

1. The problem was diagnosed when we were testing our install, using the information @ http://docs.apigee.com/private-cloud/latest/test-install . All the validation was successful EXCEPT curl -H "Host: VALIDATE.apigee.com" http://10.45.8.66:59001/v1/apigee/healthCheck....FAILED!
2. Upon analysis, we realized that this happens because a VHOST is not being created on Nginx when the validation script runs. The .conf files in conf.d get marked as .conf.bad and the Nginx Error logs show

2017/05/22 16:27:26 [warn] 69826#69826: the "user" directive makes sense only if the master process runs with super  -user privileges, ignored in /opt/nginx/conf/nginx-configtest-69814.conf:
22017/05/22 16:27:26 [alert] 69844#69844: setrlimit(RLIMIT_NOFILE, 400000) failed (1: Operation not permitted)2017/05/22 16:27:26 [alert] 69845#69845: setrlimit(RLIMIT_NOFILE, 400000) failed (1: Operation not permitted)
2017/05/22 16:27:26 [alert] 63949#63949: worker process 68228 exited on signal 11 (core dumped)
2017/05/22 16:27:27 [alert] 63949#63949: worker process 68229 exited on signal 11 (core dumped)

3..The error around setrlimit goes away when i manually raise the number of limit for apigee user and the user directive error goes away when i comment out the user directive on nginx.conf. But we can't find out why the nginx worker process is exiting (moreover, do we really have to make the other changes manually?)

Summary of the problem: I can't figure out why nginx is creating a core dump and exiting.

I see the same "nginx worker exiting" error when i try to provision an org, the org gets created, the environment gets created, the management server ui shows the virtual host but nginx does not listen on that port. Furthermore, it renames the conf.d files to conf.bad

Any pointers towards resolving this problem will be appreciated

Regards,

Rahul

Note:Typing questions and comments in all caps and using unnecessary punctuation (!!1! / ???) will not increase the likelihood of your question being answered.