Thank you for reaching out! In reviewing the information you’ve provided I see you have questions about running Linux apps within an Azure Web App, and what updates have been made in this space.
Since the last post you linked we have made some major improvements to this area via our new ‘Deploy an Azure App Service’ step template (available in Octopus versions > 2021.1):
If you are currently using the legacy step template ‘Deploy an Azure Web App (Web Deploy)’, then this updated step template should help alleviate some of the pains of the old template, but let me know if you have any additional questions or concerns.
When deploying to a Linux Web App, I get a “Gateway Time-out”, “The remote script failed with exit code 100” error (with the new Deploy an Azure App Service step).
Deploying the same app to a Windows Web App completes successfully.
I’m sorry to hear you are having trouble with the new ‘Deploy an Azure App Service’ step template, but I’ll do my best to help get things sorted.
As an initial troubleshooting step would you be able to upload the raw output for both the working Windows app task as well as the broken Linux app task? Feel free to upload these logs at the following secure link.
While I continue to look into this on my side, can you also let me know if the package sizes vary between the Linux and Windows applications? I’d be curious to know the package sizes (on average) that are being uploaded in each process in order to rule this out as being the potential issue.
I did find this GitHub issue which sounds similar to what we are seeing here (slightly different error), but this should be addressed in the version of Octopus you are currently running so I am continuing to investigate what could be causing this in your case.
Thank you for clarifying and providing this additional information.
As a next step in troubleshooting, would you be able to upload the Tentacle logs for review as well? I’m curious to see what the Tentacle logs report in this case, so we can compare it against what is being reported by the Octopus server logs.
I’ve uploaded the tentacle and server logs from C:\Octopus\Logs on the Octopus server. I don’t believe it executed on a remote tentacle due to the step setting:
“Execution LocationThis step will run on the Octopus Server on behalf of each deployment target”
I’m sorry that changing this setting didn’t impact anything, but I’ve been doing some more experimenting on my side to try and troubleshoot this issue further.
In order to try and reveal some information on the underlying problem could you upload the relevant deployment logs for the problem application on the Azure side? On my side I was able to pull this information by going to My Web App > Deployment Center > ‘Logs’ tab in Azure:
You’re welcome, I’m glad you were able to identify the underlying problem. I haven’t used the auto-swap feature too heavily so I wasn’t initially aware this wasn’t supported for Linux apps, but definitely something I will keep in mind if this comes up in the future.