Azure WebJobs - no longer working. No route registered for

1
votes

From 4am this morning. Two of my webjobs that have been running quite happily for months every 2 minutes are now broken. The error is:

Http Action - Response from host '*******************.scm.azurewebsites.net': 'NotFound' Response Headers: Pragma: no-cache x-ms-request-id: d719e8d0-429d-4ba3-86de-a732e54dbd4f Cache-Control: no-cache Date: Wed, 21 Sep 2016 21:20:01 GMT Set-Cookie: ARRAffinity=8f119d7b3e71f6a6a4d78b9eebbac59d8f13ae47ad9ddc5efdc9151826e5ad57;Path=/;Domain=********************.scm.azurewebsites.net Server: Microsoft-IIS/8.0 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Body: "No route registered for '/api/triggeredwebjobs/batch/run%3Farguments=job-steve'"

https://github.com/projectkudu/kudu/wiki/WebJobs-API#invoke-a-triggered-job http://blog.davidebbo.com/2015/05/scheduled-webjob.html

I am using David Ebbo's solution in the above link and also adding parameters as outlined on the project website.

3
azure-webjobs
Can you share your web app name, either directly or indirectly? This will help us investigate. Thanks! – David Ebbo
Also, can you specify what timezone '4am' refers to? – David Ebbo
Thanks David, good article BTW. pyramiswebjobs.azurewebsites.net. 4am was European time on Wednesday morn, so 5am in London. I have deleted and republished to this test site and added a new scheduler. Both Production and this have the same issue, so must be some kind of update? – Steve Newton
What happens if you go to the Azure Portal and try to manually run the WebJobs? Right now, logs show that this PyramisBatch WebJob has never run at all in this WebApp. – David Ebbo
Just run it, works fine. It complains about no parameters but that is correct. The errors I see are in the scheduler. – Steve Newton

3 Answers

0
votes

It looks like you have a mismatch between the name of the WebJob that your scheduler is trying to invoke (batch), and the actual name of your WebJob in your Web App (PyramisBatch). So the error is expected.

Can you change you scheduler to hit the right WebJob?

0
votes

As we discovered, the root issue was that the '?' in the URL was encoded as %3F, instead of just being ?. Fixing the URL in the scheduler addressed the issue.

What's not clear is what caused it to be that way if it used to work. That could be some kind of scheduler or portal issue. But at least we know it's not something related to WebJob itself.

0
votes

I had the same issue with my web api app. Restarting the app fixed it.