Getting 500 error post deploying microservices on app service on the Azure
I ran across this same error today, for me the source of the problem occurred during startup. My application was trying to create a file, and this is not allowed.
"Running from package makes wwwroot read-only, so you will receive an error when writing files to this directory."
Source:
https://learn.microsoft.com/en-us/azure/app-service/deploy-run-package
Generally 500 comes due to application error on the server.
When "Server Error in '/' Application" comes , did you observe anything in "Diagnose and Solve Problem" under 5xx errors.
3) You can enable FREB logs . Follow this blog how to do it https://blogs.msdn.microsoft.com/benjaminperkins/2017/01/27/enable-failed-reuqest-tracing-for-an-azure-app-service-web-app/
4) See Events Logs in Kudu https://azure.microsoft.com/en-in/resources/videos/what-is-kudu-with-david-ebbo/
Related
We've upgraded our application to Laravel 9 last week and noticed a large amount of failed jobs appearing as soon as we deployed the build in production.
Those errors were all email related with the following error message:
Expected response code "250" but got code "451", with message "451 4.4.2 Timeout waiting for data from client.".
We've reverted back to the previous build (which was using SwiftMailer) and the errors stopped. To clarify, we've been running the application for a few weeks and never had that error before.
On "Staging" we didn't have that issue. The only difference is we use SQS for queues in live and set :
APP_ENV=production
APP_DEBUG=false
that are the only differences.
Could you try adding 'ping_threshold' => 10, to your smtp or ses configuration in config/mail.php
If you are using a queue worker/manager, remember to restart the process for the new configuration to come into effect.
This seems to have resolved the issue for me. Could be coincidental, but will report back if the issue returns.
This used to be working perfectly until a couple of days back exactly 4 days back. When i run gcloud app deploy now it complete the build and then straight after completing the build it hangs on Updating Service
Here is the output:
Updating service [default] (this may take several minutes)...failed.
ERROR: (gcloud.app.deploy) Error Response: [13] Flex operation projects/just-sleek/regions/us-central1/operations/8260bef8-b882-4313-bf97-efff8d603c5f error [INTERNAL]: An internal error occurred while processing task /appengine-flex-v1/insert_flex_deployment/flex_create_resources>2020-05-26T05:20:44.032Z4316.jc.11: Deployment Manager operation just-sleek/operation-1590470444486-5a68641de8da1-5dfcfe5c-b041c398 errors: [
code: "RESOURCE_ERROR"
location: "/deployments/aef-default-20200526t070946/resources/aef-default-20200526t070946"
message: {
\"ResourceType\":\"compute.beta.regionAutoscaler\",
\"ResourceErrorCode\":\"403\",
\"ResourceErrorMessage\":{
\"code\":403,
\"errors\":[{
\"domain\":\"usageLimits\",
\"message\":\"Exceeded limit \'QUOTA_FOR_INSTANCES\' on resource \'aef-default-20200526t070946\'. Limit: 8.0\",
\"reason\":\"limitExceeded\"
}],
\"message\":\"Exceeded limit \'QUOTA_FOR_INSTANCES\' on resource \'aef-default-20200526t070946\'. Limit: 8.0\",
\"statusMessage\":\"Forbidden\",
\"requestPath\":\"https://compute.googleapis.com/compute/beta/projects/just-sleek/regions/us-central1/autoscalers\",
\"httpMethod\":\"POST\"
}
}"]
I tried the following the ways to resolve the error:
I deleted all my previous version and left the running version
I ran gcloud components update still fails.
I create a new project, changed the region from [REGION1] to [REGION2] and deployed and m still getting the same error.
Also ran gcloud app deploy --verbosity=debug, does not give me any different result
I have no clue what is causing this issue and how to solve it please assist.
Google is already aware of this issue and it is currently being investigated.
There is a Public Issue Tracker, you may 'star' and follow so that you can receive any further updates on this. In addition, you may see some workarounds posted that could be performed temporarily if agreed with your preferences.
Currently, there is no ETA yet for the resolution but there will be an update provided as soon as the team progresses on the issue.
I resolved this by adding this into my app.yaml
automatic_scaling:
min_num_instances: 1
max_num_instances: 7
I found the solution here:
https://issuetracker.google.com/issues/157449521
And I was also redirected to:
gcloud app deploy - updating service default fails with code 13 Quota for instances limit exceeded, and 401 unathorizeed
I'm doing a Proxy Service with Messaging transportation for Any XML and defining the stage, archive and error folders for a xml processing when configuring the proxy service.
I had included an error handler and when reading the file and an error happens, the file must be moved for error folder.
Currently when doing my test and an error happens, the file is moved to archive instead of error folder.
Are there something that I need to add and get this working?
Basically the complete scenario is a Proxy Service polling a folder, reading the XML and sending to Business Services as a XML messaging.
Could you give me directions to make this working or tips that I need to check?
Thanks
Edson
A wild guess - Is it because you have an error handler and you may be doing a success reply from the handler. Have you tested removing the error handler or reply-with-failure from the handler ?
I have developed a small accounting application which running fine in xampp in windows machine and also it is working fine in my development server (linux based).
But, when i migrate the total application to client linux server I got the following error:
Parse error: syntax error, unexpected T_STRING in /home/orcilia/public_html/cfm/application/models/sm_main.php on line 1
I have checked it several times but unable to found an error ...
But, I think in the client server there is some issue in case of loading model from controller..
PLEASE HELP ME REGARDING THIS..i have spent a lot of time but unable to get rid of this error...
Thanks,
TANAY GHOSH
If you use <? as an opening tag (check at the very start of your file), change it to
<?php. The server might not allow the shorthand style.
I am so close to getting my TeamCity setup complete, but am stumped by this error:
(12/22/2011 2:30:15 PM) An error occurred when the request was processed on the remote computer.
An error was encountered when processing 'Web.zip'.
The error code was 0x80070020.
The process cannot access 'C:\Inetpub\wwwroot\Deneb\Website\obj\Deploy\Package\Web.zip' because it is being used by another process.
I tried deleting that file myself, and didn't have any problems. I am able to deploy this site from another server, also without any problems. I set the Team City build agent service to run as administrator, and restarted the service.
Any help would be greatly appreciated - thanks!
Realized that the checkout directory shouldn't be set the same as the web directory