You’re viewing Apigee advantage documentation, view Apigee X records.

Videos

See listed here clips for more information on solving 500 interior Server mistakes.

Symptom

The consumer software becomes an HTTP position laws of 500 using information “interior servers mistake” as a response for API telephone calls. The 500 inside Server error might be caused by an error throughout the execution of every plan within Edge or by an error on target/backend server.

The HTTP updates code 500 are a simple error reaction. This means that host experienced an unexpected situation that avoided they from fulfilling the consult. This error is usually came back because of the server whenever not one error code is suitable.

Mistake Communications

You may get the subsequent error message:

In some instances, you’ll notice another mistake message which has more information. Let me reveal a sample error information:

Feasible Reasons

The 500 interior Server Error maybe cast due to a number of different forces. In side, the causes could be classified into two major kinds predicated on where error happened:

Delivery Error in a benefit Policy

An insurance policy inside the API proxy may do not succeed for reasons uknown. This section clarifies just how to diagnose the condition in the event that 500 inner servers mistake happens while in the performance of a policy.

Diagnosis

Diagnostic Steps for Personal and Public Cloud Users

If you have the trace UI treatment for any error, after that:

1. Verify the mistake was due to the performance of an insurance policy. Discover identifying the origin of the complications for facts.
2. In the event that mistake happened during plan delivery, remain.. In the event the mistake was actually brought on by the backend server, head to Error during the Backend servers.
3. Select the API request definitely weak with 500 Internal machine Error for the trace.
4. Examine the consult and select the particular policy that has had were not successful or the flow called “Error” which immediately following the failed rules for the trace.
5. Acquire more facts about the error either by examining the “error” area within the land section or perhaps the Error content material.
6. Making use of the facts you have built-up towards mistake, try to set their influence.

Diagnostic Actions for Professional Affect Consumers Best

Without having the trace UI treatment, next:

1. Check your error happened throughout execution of an insurance policy. Read Deciding the origin of the complications for information.
2. When the mistake was brought on by coverage delivery, carry on. In the event that error taken place during coverage performance, continue. If error had been as a result of the backend machine, head to Error when you look at the Backend servers.
3. Use the Nginx access logs as described in identifying the foundation associated with the difficulties to discover the failing rules inside API proxy and also the unique consult information id
4. Check out the information Processor logs ( /opt/apigee/var/log/edge-message-processor/logs/system.log ) and seek out exclusive request message id inside it.
5. If you do discover special demand content ID, see if you can get more information on the source when it comes to breakdown.

Solution

When you have determined the main cause of the challenge aided by the coverage, just be sure to ideal the problem by repairing the policy and redeploying the proxy.

The next instances illustrate how to decide the main cause and quality for different types of problems.

If you would like more assistance in problem solving 500 interior host Error or you think that it is an issue within side, call Apigee assistance.

Example 1: troubles in Service Callout coverage considering an error from inside the backend servers

In the event the call with the backend server fails in the services Callout rules with any error such as 4XX or 5XX, it can be treated as 500 interior servers Error.

1. Here’s an illustration in which the backend provider fails with a 404 error inside the Service Callout rules. The subsequent mistake content is distributed on consumer:
2. These trace UI program shows 500 condition laws triggered due to an error operating Callout policy:

Contained in this example, the “error” property details the explanation for this service membership Callout coverage failure as “ResponseCode 404 is handled as error”. This mistake may possibly occur when the site becoming accessed via the backend servers URL from inside the services Callout rules is certainly not readily available.

Look into the accessibility to the site regarding backend machine. It might never be available temporarily/permanently or it might happen relocated to a different sort of area.

Instance 1 Quality

1. Check the accessibility to the source regarding backend host. It could not readily available temporarily/permanently or this may happen moved to an alternate location.
2. Fix the backend servers URL for the services Callout policy to suggest a valid and current resource.
3. When the site is only temporarily unavailable, after that sample putting some API consult as soon as reference is present.

Example 2: Breakdown in Plant Factors Plan

Let us now check another instance, in which 500 Internal host Error are caused considering an error for the Extract factors policy and find out how to diagnose and resolve the matter.

This amazing trace in UI period shows 500 standing laws as a result of one in Extract Variables rules:

Find the a failure herb factors coverage, scroll straight down and check out the “Error information” section for lots more facts:

The Error contents suggests that the”serviceCallout.oamCookieValidationResponse” changeable just isn’t for sale in the herb factors policy. As term of the varying indicates, it must be keeping the feedback of preceding provider Callout plan.

Choose the provider Callout policy within the trace therefore will discover the “serviceCallout.oamCookieValidationResponse” diverse was not ready. This indicates that the label to your backend solution unsuccessful, generating a clear feedback changeable.

Although the Service Callout coverage has hit a brick wall, the delivery in the procedures after solution Callout policy carry on because the “continueOnError” banner for the Service Callout coverage is defined to correct, as revealed below: