-
Notifications
You must be signed in to change notification settings - Fork 655
WEBSITE_RUN_FROM_PACKAGE startup issues after platform maintenance #3123
Comments
We're seeing the exact same issue, see #3088 Even contacted Azure Support about this, but they were useless, asking me to "attach a profiler" and just ignored my explanation of the root cause 🤷♂ |
I'm seeing this issue now. Anyone have luck figuring this out? |
@jonarmstrong This is on AppService Environment and only happened to some instances, correct? Wonder if you have a more recent incident? Provide the UTC time, instance and error as you did above - we will take try to correlate with our log. |
@suwatch, Yes, this is on an ILB ASE and I don't have a more recent occurrence of this issue as it has not occurred again since then. Perhaps @katiep23 who just had this occur has a more recent log that she can pull for you to cross reference? |
@suwatch Hey, this issue happened again over the weekend and killed a node on two of my app service clusters. Both are I1 skus in an ILB ASE Errors started ~ @ 5/17/2020 09:40:00, a restart for a 'Platform File Server Upgrade' also occurred at the same time. The impacted instance name was RD501AC561EA94 Errors started ~ @ 5/18/2020 03:00:00 UTC, a restarted for a 'Platform File Server Upgrade' also occurred at the same time. The impacted instance name was RD501AC561D51E |
I suggest to open http://aka.ms/CRI-WebApps. Kudu is more about deployment and for runtime issue, it will be best served from App Service product team. |
@suwatch Do you have a publicly accessible location I can submit the issue to? That goes to an internal microsoft site which I can't sign into. |
This is a follow-up to my post on 11/23/2019. I've since dug a little deeper and realize I have the same problem was impacting @PaitoAnderson & @xt0rted. My apps are also using the
WEBSITE_RUN_FROM_PACKAGE
setting, which seems to be the root cause of this issue.Was there every a resolution to this? I have three apps which currently have bad instances because of this exact issue. The only way to resolve the issue is to restart the app and hope it comes back up. It has been plaguing my app reliability for months now. Below are stack traces from 2 of the 3 failing web sites
Instance - RD501AC561D51E
@ 2020-02-16T09:48:18
Instance - RD501AC56B00BE
@ 2020-02-16T07:20:21
Originally posted by @jonarmstrong in Azure/app-service-announcements-discussions#32 (comment)
The text was updated successfully, but these errors were encountered: