Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft.WindowsAzure.Storage.StorageException: 'The specified queue does not exist.' #1483

Closed
symlynk opened this issue Dec 29, 2017 · 9 comments

Comments

@symlynk
Copy link

symlynk commented Dec 29, 2017

I am seeing the following exception continuously being thrown and displayed in the output window:

Exception thrown: 'Microsoft.WindowsAzure.Storage.StorageException' in System.Private.CoreLib.dll

When running this code as a .NET Core 2.0 console app with no other classes apart from the following:

    class Program
    {
        static void Main( string[] args )
        {
            var config = new JobHostConfiguration();

            config.DashboardConnectionString = "..."; // replace ... with storage connection string
            config.StorageConnectionString = "..."; // replace ... with storage connection string

            var host = new JobHost( config );

            host.RunAndBlock();
        }
    }

The exception is being thrown from StorageQueue.cs with the message:

"Microsoft.WindowsAzure.Storage.StorageException: 'The specified queue does not exist.'"

Microsoft.Azure.WebJobs (3.0.0-beta4)

@erick-thompson
Copy link

I'm running into this issue as well. Any update on what it might be?

@brettsam
Copy link
Member

Are you able to catch and inspect the queue name? WebJobs attempts to monitor a 'host' queue for requests to shutodown -- but that queue doesn't always exist. It's likely this is just a background exception that we're already handling, but if you can track down the queue name, that would confirm it.

@brettsam brettsam added this to the Active Questions milestone Jan 19, 2018
@brettsam
Copy link
Member

FYI -- here's a related issue: #1215

@erick-thompson
Copy link

I am able to catch the StorageException, but I can't figure out how to get the queue name from the exception. I've poked around inside the StorageException, but no luck. I have the ServiceRequestId, but nothing else that looks promising. Any suggestions on how to get the queue name?

@erick-thompson
Copy link

erick-thompson commented Jan 23, 2018

I just fired up Fiddler. It appears to be hitting a queue named "azure-webjobs-host-[machinename]".

@erick-thompson
Copy link

After digging into the code, I see where and how it is used. However, I can't find any documentation for it. Is this queue to be used by the SDK only, or is it something that can be used by developers?

@brettsam
Copy link
Member

See #770 for an explanation of what those queues are for.

@mathewc
Copy link
Member

mathewc commented Feb 13, 2018

Closing this issue since #1572 addresses it. #1215 remains open to track potential improvements to AppInsights to correctly handle non-error logs.

@mathewc mathewc closed this as completed Feb 13, 2018
@ggirard07
Copy link

same issue here while running on the storage emulator. But that behavior is happening only on my machine, not on the ones of my coworker.

The name of the queues involved are:

  • azure-webjobs-host-[heartbeatsId] where heartbeatsId is a Guid I found in http://127.0.0.1:10000/devstoreaccount1/azure-webjobs-hosts/heartbeats/
  • azure-webjobs-host-[heartbeatsBlobId] where heartbeatsBlobId is the Guid of the latest blob in http://127.0.0.1:10000/devstoreaccount1/azure-webjobs-hosts/heartbeats/09cadd1626424a3b8c52a7f0e985dfd0/

Is #1572 going to address my case too (no AppInsight here)?
That fix is still not included in v2.2.0 release, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants