VHosts on Router are not listening after updating Edge from 4.17.01 to 4.18.01

oyamatakuro
Participant IV

Hello,

I have updated an all-in-one Edge OPDK environment from 4.17.01 to 4.18.01 following the steps in the below page.

https://docs.apigee.com/private-cloud/latest/update-apigee-edge-4170x-41801

The update itself ended successfully, but after that, the virtual hosts on Router are not listening on the ports.All the edge components status check with "apigee-all status" is OK.

The error.log of nginx outputs the error below.

[emerg] 12694#12694: zero size shared memory zone "perclient"

I found an community info on the error and tried the solution as below, but could not resolve this issue.

https://community.apigee.com/questions/44178/nginx-doesnt-listen-the-vhost-port-1.html

$ /opt/apigee/apigee-service/bin/apigee-service edge-router stop
$ sudo rm /opt/nginx/conf.d/*
$ /opt/apigee/apigee-service/bin/apigee-service edge-router restart

The attached is the error.log of nginx with debug mode at that time.

nginx-errorlog.txt

Any help would be appreciated.

Thanks in advance.

Solved Solved
0 10 811
2 ACCEPTED SOLUTIONS

The attached nginx error log says "nginx/1.10.1"

OPDK 4.18 comes with nginx/1.12.x. Are you sure you upgraded? Can you try manually do: sudo yum update apigee-nginx ?

View solution in original post

We released an update to Edge, version 4.18.01.01, that fixes this issue. See the release notes for more information:

https://docs.apigee.com/release/notes/4180101-edge-private-cloud-release-notes

Stephen

View solution in original post

10 REPLIES 10

can you check /opt/nginx/conf.d/ directory after restart for any bad conf files? Please also check the ownership of that directory?. All ownership should be apigee user.

@Rajesh Mishra,

Thanks for your answer.

Yes, after the restart, I can still see many bad conf files in /opt/nginx/conf.d/ directory as attached.

confd.png

The ownership of conf.d directory is also apigee user.


Best regards,

Takuro

I suggest you should talk to Apigee support to further debug the issue. @Frank Liu - Any thoughts.

The attached nginx error log says "nginx/1.10.1"

OPDK 4.18 comes with nginx/1.12.x. Are you sure you upgraded? Can you try manually do: sudo yum update apigee-nginx ?

@fliu, @Rajesh Mishra,

Thanks for you answer.

You are correct. The VHosts are now working after I updated apigee-nginx.

I am sure that I followed the steps for updating Edge described in "For a 1-host standalone installation" on the following doc.
https://docs.apigee.com/private-cloud/latest/update-apigee-edge-4170x-41801

If updating nginx is necessary for 4.18.01 and that is not automatically performed by the current procedure written in the doc, could you rectify it?

Hi All, @fliu

Just ran into this same issue for a different customer with a 9 node configuration. NGINX was not updated during the upgrade. Not sure where it is falling apart (in the docs or scripts) but hopefully we can get it addressed so more customers aren't impacted.

We should either add that step in the docs or fix the upgrade scripts to address it.

We ended up running: yum update apigee-nginx

Please raise a support ticket to the OPDK team.

This is the exact issue and fix for us. We had upgraded from 4.17.09 to 4.18.01. Support was suggesting to remove the /opt/nginx/conf.d/* files but that was not helping. I ran across this answer and it was our exact case, meaning apigee-nginx was not upgraded as part of Apigee's upgrade scripts or docs.

Spread the word because support was not aware of this issue yet and I'm guessing you'll get this a-lot. Would be very helpful that Apigee would just upgrade the apigee-nginx component as part of the upgrade.

robert
Participant V

just want to add a bit more details as we received this same issue during an upgrade. In addition we were seeing 502 Bad Gateway across all proxies. NGINX was also having many .bad files. The answer below ended up resolving it.

We released an update to Edge, version 4.18.01.01, that fixes this issue. See the release notes for more information:

https://docs.apigee.com/release/notes/4180101-edge-private-cloud-release-notes

Stephen