So I have site that has been working fine for a while. Then today 6am onwards we have been alot of errors the stack is:
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxxx:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at ImageProcessor.Web.Plugins.AzureBlobCache.AzureBlobCache.<>cDisplayClass120.b0()
at ImageProcessor.Web.Plugins.AzureBlobCache.AzureBlobCache.TryFiveTimes(Action delegateAction, Action exceptionAction)
at ImageProcessor.Web.HttpModules.ImageProcessingModule.d_32.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
at System.Web.HttpApplication.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar)
Yeah you are getting an unhandled timeout communicating with the storage account. Update to the latest version and you should stop seeing the errors as I handle it better.
There's also a config value available for adjusting the timeout.
Cool have updated just testing before I roll out to live. One thing one of the new config values is name for cache blob which is set to default cache do I need to create that in azure?
One thing i dont understand is that the ip is moaning about it maps to my cdn url. I can hit that url no problem. There are no firewall rules on it so it should be able to hit it?
The other weird thing is this has all been working fine problem started around 6am yesterday, Seems to have calmed down around 3am this morning but that may be due to current server load.
Weird errors with Azure blob cache plugin
So I have site that has been working fine for a while. Then today 6am onwards we have been alot of errors the stack is:
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at ImageProcessor.Web.Plugins.AzureBlobCache.AzureBlobCache.<>cDisplayClass120.b0() at ImageProcessor.Web.Plugins.AzureBlobCache.AzureBlobCache.TryFiveTimes(Action delegateAction, Action exceptionAction) at ImageProcessor.Web.HttpModules.ImageProcessingModule.d_32.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) at System.Web.HttpApplication.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar)
Anyone seen this before
Hi Ismail,
Yeah you are getting an unhandled timeout communicating with the storage account. Update to the latest version and you should stop seeing the errors as I handle it better.
There's also a config value available for adjusting the timeout.
Cheers
James
James,
Cool have updated just testing before I roll out to live. One thing one of the new config values is name for cache blob which is set to default cache do I need to create that in azure?
Regards
Ismail
James,
One thing i dont understand is that the ip is moaning about it maps to my cdn url. I can hit that url no problem. There are no firewall rules on it so it should be able to hit it?
The other weird thing is this has all been working fine problem started around 6am yesterday, Seems to have calmed down around 3am this morning but that may be due to current server load.
Regards
Ismail
Is it working now?
I have no idea what you mean by that.
IP Azure Cache has a very short timeout by default and your browser will take much longer to timeout.
It was either increased traffic or a hiccup on Azure.
Oh and you don't need to create the container...
James,
Cool thanks for the help. We are just testing a bit more then we will deploy. Weird thing is the live site is all working now no more errors grrr.
Regards
Ismail
If I had a dollar every time that happened....
Happy to help chum 😄
is working on a reply...