Container 'app_name' was terminated with exit code '132'

Sowndar kumaresan 21

Hi team, We have provisioned the container app and when we pushed the latest build, the revision was working fine until some time after some time system log showed the application crashed with "Container 'containerAppName' was terminated with exit code '132'"

Can anyone suggest the best way to debug and same container works well in lower environments and the CPU and memory usage also seem to be normal.

for a few minutes application works fine able to get the response after some time if fails. If it might be a memory issue how can we debug the same?

navba-MSFT 20,810 Microsoft Employee

@Sowndar kumaresan Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

I understand that your Azure Container App crashed with the error message Container 'containerAppName' was terminated with exit code '132'. You also mentioned that the container works well in lower environments, and the CPU and memory usage seem to be normal.

Exit code 132 indicates that the container was terminated by a SIGILL signal, which usually means that the container tried to execute an illegal instruction. This error can occur due to various reasons, such as a hardware issue, a bug in the application code, or a misconfiguration in the container environment. see here.

Azure Container Apps provides several built-in observability features that together give you a holistic view of your container app’s health throughout its application lifecycle. These features help you monitor and diagnose the state of your app to improve performance and respond to trends and critical problems.

So this issue needs to be isolated first. Lets start with the below available features which will help us in troubleshooting this issue:

Feature	Description
Log streaming	View streaming system and console logs from a container in near real-time.
Application logging	Monitor, analyze and debug your app using log data.
Azure Monitor metrics	View and analyze your application's compute and network usage through metric data.
Azure Monitor Log Analytics	Run queries to view and analyze your app's system and application logs.

Plan 1:
Start with checking the below 2 logs and see if you find any details about the error:

Container console logs: Log streams from your container console.
System logs: Logs generated by the Azure Container Apps service.

Plan 2:
The easiest way to query the above logs is through LogAnalytics, See the below article to query ContainerAppSystemlogs_CL and ContainerAppConsoleLogs_CL tables:

https://learn.microsoft.com/en-us/azure/container-apps/log-monitoring?tabs=bash#query-log-with-log-analytics

Plan 3:
If none of the above helps, Please share the below details over an email at AzCommunity@microsoft.com ( with subject "Attn: Naveen") and include the below details:

Azure Container App resource ID in below format: /subscriptions/XXXXXXX/resourceGroups/XXXXXXX/providers/Microsoft.App/containerApps/XXXXXXX
Region where ContainerApp is running
Most recent time of the issue in UTC

I will look at the backend logs to identify the root cause.

Awaiting your reply.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Sowndar kumaresan 21 Reputation points

2023-08-29T04:43:40.07+00:00
HI @navba-MSFT , thanks for your response we have found this issue from the system logs only and also need to add some more points

There is 2 difference between working(lower) and non- working(higher) env

When we use the env variable this issue continues and when we hard code the values issue is not happening, We are using the env variable only in lower env but it works fine there.

Lower env uses consumption plan, higher env uses consumption plan but still Consumption + Dedicated plan but we still haven't bought any individual dedicated plans still using consumption only.

The code hosted there is Python with Flask API and we interact with open API as well, The key-value pairs and URL were placed in the env variable.
navba-MSFT 20,810 Reputation points Microsoft Employee

2023-09-01T09:06:34.3766667+00:00

@Sowndar kumaresan Could you please let me know if you had a chance to follow the above suggestion? Awaiting your reply.
Sowndar kumaresan 21 Reputation points

2023-09-01T09:15:02.24+00:00

HI @navba-MSFT as you said seems like env variable URL mismatch thanks for your help, i will accept your ans
navba-MSFT 20,810 Reputation points Microsoft Employee

2023-09-01T09:26:41.09+00:00

@Sowndar kumaresan Thanks for your reply.

For the below answer, Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Accepted answer

navba-MSFT 20,810 Reputation points Microsoft Employee

2023-08-30T09:33:12.2966667+00:00
@Sowndar kumaresan Thanks for getting back and sharing the details. in the non-working ( higher) scenario, Could you please try to **list **the environment variables and check if it has been set correctly ?

Run the below command and then try to access the FQDN:

az containerapp revision list \ --name $CONTAINERAPPS_NAME \ --resource-group $RESOURCE_GROUP \ --query "[].{Name:name,DateCreated:createdTime,ProvisionStatus:provisioningState,Traffic:trafficWeight,Active:active,FQDN:fqdn}"

While accessing the FQDN from browser it should list the env variables and its value. See an example below:

Awaiting your reply.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Share via

Container 'app_name' was terminated with exit code '132'

0 additional answers