Troubleshooting the Edge Router

Edge for Private Cloud v4.18.01

The Edge Router is implemented by using the Nginx router. During the Edge upgrade process, or when changing the configuration of the Router, you might see Nginx configuration errors. When these errors occur, Edge writes the Nginx configuration files that caused the issue to /opt/nginx/conf.d. You can then use the Nginx configtest tool to determine the reason for the error.

For example, you examine the /opt/nginx/conf.d and see the following files:

-rw-r--r-- 1 apigee apigee 522 Jul 20 08:41 0-default.conf.bad 
-rw-r--r-- 1 apigee apigee 577 Jul 20 08:42 0-fallback.conf 
-rw-r--r-- 1 apigee apigee 1062 Jul 20 08:18 0-map.conf 
-rw-r--r-- 1 apigee apigee 1887 Jul 20 08:42 custorg_test_default.conf.bad

Notice how several files have the suffix .bad.

Typically these errors are caused because you made incorrect changes on the /opt/apigee/customer/application/ file or you made incorrect changes to a virtual host. For example, you added the following:


This value is not allowed.

To fix the error:

  1. Remove the .bad suffix from the file names in the /opt/nginx/conf.d folder so they end in .conf.
  2. Run the Nginx configtest tool to display the reason for the failure:
    > /opt/nginx/scripts/apigee-nginx configtest

    You see output in the form:
    nginx: [emerg] "proxy_busy_buffers_size" must be equal to or greater than the maximum of the value of "proxy_buffer_size" and one of the "proxy_buffers" in /opt/nginx/conf/nginx.conf:47
  3. Edit /opt/apigee/customer/application/ to set conf_load_balancing_load.balancing.driver.proxy.busy.buffer.size to 128k.
  4. Removed the /opt/nginx/conf.d folder:
    > rm -rf /opt/nginx/conf.d
  5. Restart the Router:
    > /opt/apigee/apigee-service/bin/apigee-service edge-router restart
  6. You should not longer see bad config files in the /opt/nginx/conf.d folder.