502 Bad Gateway | tcpdump Apigee X - Page 2

shrenikkumar-s · 08-14-2023 02:04 PM

Hi All

We're getting 502 Bad Gateway error on our production at particular time regularly (say around midnight everyday) and this was not seen nonprod.

Error:

{"fault":{"faultstring":"Unexpected EOF at target","detail":{"errorcode":"messaging.adaptors.http.flow.UnexpectedEOFAtTarget","reason":"TARGET_READ_UNEXPECTED_EOF"}}}

We've gone through https://docs.apigee.com/api-platform/troubleshoot/runtime/502-bad-gateway and Appendix A section of links on this community and also raised a support ticket.

Looking at all this couple of things can help us at looking at this issue closely & hopefully resolving it:

1. Is this documentation applicable for Apigee X? I believe part of it should be such as diagnosis

2. Check the Message Processor logs: Apigee X is managed by Google and we can't check that I believe, am I right? If yes, can we ask Google on the support ticket? I mean can they get it?

3. (Most important) Collect the tcpdump output on the Message Processors: Again, I believe we do not have access to get the tcpdump on Apigee X. If I'm wrong, could somebody please help with the procedure to get them?

4. (Most important) Collect the tcpdump on the backend server. We've requested for it.

5. "reason":"TARGET_READ_UNEXPECTED_EOF" in the JSON error, can it help to point at the exact problem? In my understanding, it means the similar things explained in documentation that the Message Processor received an EOF while it was still waiting to read a response from the backend server

@kurtkanaskie @dchiesa1 @Sai Saran Vaidyanathan
@dknezic @ganadurai @Harish123 @Manisha_Chennu @Peeyush_Singhai @markjkelly