Reputation: 1411
My Azure continuous webjob stopped giving reason "WebJob is stopping due to website shutting down"
Logs from Kudu log
[12/09/2016 17:11:49 > 2e7853: WARN] Reached maximum allowed output lines for this run, to see all of the job's logs you can enable website application diagnostics
[12/09/2016 17:12:42 > 2e7853: SYS INFO] WebJob is stopping due to website shutting down
[12/09/2016 17:12:42 > 2e7853: SYS INFO] Status changed to Stopping
[12/09/2016 17:12:47 > 2e7853: SYS INFO] WebJob process was aborted
[12/09/2016 17:12:47 > 2e7853: SYS INFO] Status changed to Stopped
[12/09/2016 17:12:55 > 2e7853: SYS INFO] Status changed to Starting
[12/09/2016 17:12:55 > 2e7853: SYS INFO] WebJob singleton setting is False
[12/09/2016 17:12:57 > 2e7853: SYS INFO] Run script 'VimsProcessHistoryData.exe' with script host - 'WindowsScriptHost'
[12/09/2016 17:12:57 > 2e7853: SYS INFO] Status changed to Running
It already Always On.
Can some one help to resolve this
Upvotes: 2
Views: 2609
Reputation: 112
We had this issue at work and identified that it was due to automatic scaling operations being performed in Azure. You can find these in the activity logs of any app service plan, simply filter for:
You can edit the columns in Azure Portal to display just the time stamp and resource ID:
Then ensure that the corresponding App Service is a member of the affected service plan:
You can also drill into a specific result to confirm it's an autoscaling operation and look at how the number of workers had changed around that timeframe via the "Change history" panel:
Upvotes: 1
Reputation: 1411
I changed my job to continuous web job.. and It worked.
It tried couple of options with triggered webjob like keep it Always On.. but that didn't work.
I enable diagnostic logging n all .. but it didn't give me any clue.
When checked with Microsoft support they responded that the VM is moved mistakenly so it cause job to stop.
Upvotes: 0
Reputation: 18465
[12/09/2016 17:12:42 > 2e7853: SYS INFO] WebJob is stopping due to website shutting down
[12/09/2016 17:12:42 > 2e7853: SYS INFO] Status changed to Stopping
[12/09/2016 17:12:55 > 2e7853: SYS INFO] Status changed to Starting
As I known, if something causes your web app to restart, then your WebJob would quickly restart as long as your web app restarts. If this happens frequently, I assumed that you need to Enable diagnostics logging for your web app and check the Process Explorer in the SCM. If this hanppens infrequently, you could try to re-deply your WebJob. Also you could deploy your WebJob to a new empty web app for isolating this issue. Here is a similar issue, you could refer to it.
Upvotes: 1