|
Discussion Forums
|
Thread: Frequent (almost 50%) 503 errors
 |
This question is answered.
Helpful answers available: 2.
Correct answers available: 1.
|
|
|
|
Replies:
12
-
Pages:
1
-
Last Post:
Mar 11, 2009 4:20 PM
by: ymarkel
|
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Frequent (almost 50%) 503 errors
Posted:
Jun 2, 2008 7:25 AM PDT
|
|
|
|
|
The site happens to be on GoDaddy.com and in .NET
The page is a simple list of my bucket--
http://tracymooreproductions.com/s3/showlist.aspx
If you use the retry button more than a few times (especially if you wait a few minutes between), you should see the error.
I've attached the .aspx, .aspx.vb and utils.* file (with the private key removed). I used the VB 2008 function to map the Web References.
Why am I getting so many 503 errors? Should I be doing something different in my code to recover more gracefully from them?
|
|
Posts:
913
Registered:
12/13/06
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 2, 2008 12:53 PM PDT
in response to: William Moore
|
|
|
Hi William,
I'd like to get some additional information from you regarding the errors you are seeing. Are you able to reproduce these results when you run your code from a local machine?
We'd really like to see the HTTP headers for the request you are sending, as well as the response you are receiving. You should be able to log them with one of the many free tools available for download on the Internet, such as wireshark or tcpmon.
Thanks,
Justin
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 2, 2008 1:52 PM PDT
in response to: Justin@AWS
|
|
|
I typically don't run a webserver on my machine, and when running as a VB application I have never seen the issue
 . I'll see if GoDaddy can run a trace.
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 3, 2008 1:15 PM PDT
in response to: William Moore
|
|
|
One clarification. I built my web references by pointing to:
http://doc.s3.amazonaws.com/2006-03-01/AmazonS3.wsdl . That caused the namespace to be com.amazonaws.s3.doc . The examples I've seen are in the namespace com.amazonaws.s3. It seems like either it would completely work or completely not work if that was the problem, but I'm clueless. I let VB 2008 build my Web Reference assuming it knows what it's doing.
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 5, 2008 9:07 AM PDT
in response to: Justin@AWS
|
|
|
I found this on GoDaddy in relationship to another webservice:
Note:
On our shared hosting, any CURL applicationsthat make secure HTTP connections (HTTPS over port 443) need to passthrough a proxy server. The address for this proxy server isproxy.shr.secureserver.net and connections must specify the use of port3128. The code below already includes this information.
I haven't specifically asked to use https--and this doesn't sound consistent with intermittent problems but does it shed any light on the situation? If so, how do you implement a proxy connection using the .NET libraries. Or does that question even make sense?
|
|
Posts:
913
Registered:
12/13/06
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 5, 2008 9:27 AM PDT
in response to: William Moore
|
|
|
William,
If you imported the Amazon S3 wsdl file in to your .NET solution as a web reference, you will probably find a reference to the Amazon S3 endpoint in your web.config file. I believe you will find that requests are being made over https.
Here is another thread (different service though) that talks about some options when trying to set a proxy for GoDaddy.
http://developer.amazonwebservices.com/connect/thread.jspa?messageID=73499𑼛
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 5, 2008 12:06 PM PDT
in response to: Justin@AWS
|
|
|
OK, so I'm confused. How do you implement this when (at least from what I see) the actual WebRequest objects are not exposed? What object do I connect the proxy to?
I'm looking at the following:
// 2.0
WebProxy proxyObject = new WebProxy("
http://64.202.165.130:3128");
proxyObject.Credentials = new NetworkCredential("ProxyUser", "ProxyPassword"); // might not need this
WebRequest.DefaultWebProxy = proxyObject;
from:
http://developer.amazonwebservices.com/connect/thread.jspa?messageID=73499𑼛
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 5, 2008 12:50 PM PDT
in response to: Justin@AWS
|
|
|
Well, I see where a proxy object is exposed, but now I have another (non-intermittent) error:
Dim objS3 As New com.amazonaws.s3.doc.AmazonS3
Dim gdProxy As New System.Net.WebProxy("
http://64.202.165.130:3128")
gdProxy.Credentials = New System.Net.NetworkCredential("mygodaddyusername", "mygodaddypw")
objS3.proxy = gdProxy
I now get the error (with or without the credentials):
Error trying to read bucket:
Requestfor the permission of type 'System.Net.WebPermission, System,Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'failed.
My code generates the Error trying to read bucket:<br/>. The rest is exception.message.
|
|
Posts:
691
Registered:
3/27/07
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 5, 2008 9:19 PM PDT
in response to: William Moore
|
|
|
Hi William,
I am consistently getting the following error when clicked the 'Initialize' button -
Error trying to read bucket:
Requestfor the permission of type 'System.Net.WebPermission, System,Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'failed.
So I am wondering whether your application was able to make successful S3 request. I could try a sample VB.Net application, but did you take a look at our S3 Resource Center and try the following sample -
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=836&categoryID=47
I would suggest to try it first on your localhost and see if you can make a successful call to Amazon S3 - if you are still having issues, please do let us know.
Thanks - Satyen
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 6, 2008 8:05 AM PDT
in response to: Satyen@AWS
|
|
|
That solid error started when I put the proxy statement in. I've taken it out now and it's intermittent again. I was hoping someone could tell me what was wrong with the proxy statement if that is really an issue.
Once 'initialize' works, 'Check Podcast Variables' works most of the time. Then, 'Build Podcast' often works through some but usually fails before the end and reports 'I=' whichever value it was working on. Right now I'm getting an object undefined on that button so I'm seeing if other changes may have triggered something.
In any case, you shouldn't need to try many times to see some good results on the initialize and some 503's.
I'll create a separate button for proxy activity.
|
|
Posts:
132
Registered:
7/19/07
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 7, 2008 12:58 AM PDT
in response to: William Moore
|
|
|
I've done a bunch of tracing and trying to use your application (both with and without the proxy), and I've determined that the requests that return 503s or web permissions errors are never getting to S3 - these errors are being generated server-side, at the GoDaddy server or proxy. All the requests that did make it to the S3 service were served successfully.
Windows hosting at GoDaddy seems to require all calls made outside the hosted environment to go through a proxy, either for HTTP or HTTPS. For normal HTTP requests, this proxy setup is handled through your site's default web.config, which is provided automatically as described here:
http://help.godaddy.com/article/1072
So, it would seem that all your requests are going through this proxy, regardless of HTTP or HTTPS - it's only automatic for HTTP, though (so the proxy code you added should be able to be removed, it isn't buying you anything since proxying is automatic and not controllable by the end-user at GoDaddy, per this article - I suspect specifying the proxy makes your code ask the proxy to connect through itself, which is likely what's causing the WebPermissions hard error).
This also explains your comment that your normal VB apps work fine - they are directly connecting to S3 and getting results; not going through GoDaddy's default built-in web proxy. I would suggest following up with GoDaddy about use of this proxy - some quick Googling shows a number of developer issues with other types of applications that use the proxy (I couldn't find a reference to S3). Apologies that we cannot be more help here, but since we can't see what the requests look like on the wire (since they are not reaching us) it is difficult to provide more focused assistance.
We'd also be happy to talk to the GoDaddy technical staff directly if they believe their proxy is attempting to communicate with any S3 endpoint and it is not succeeding for some reason. You can refer us in this thread to your support case ID should they need to speak with us and we'll contact them directly.
|
|
Posts:
10
Registered:
5/18/08
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Jun 12, 2008 11:21 AM PDT
in response to: Doug@AWS
|
|
|
As of yesterday (6/12/08), this page *never* has failed for me. I didn't change any code. I just got off the phone with GoDaddy to try to get them to admit that they changed something--but they won't. So, I'm closing the question here on S3. If anyone else is having problems with a GoDaddy site, I'd be happy to compare notes and see if there is anything we can figure out. The combination of GoDaddy for Web Hosting and S3 for data storage is *very* attractive and low-cost for low volume sites and I'd be happy to help make it work for other folks if I just knew what happened.
Thanks for all of your assistance.
|
|
Posts:
1
Registered:
3/11/09
|
|
|
|
Re: Frequent (almost 50%) 503 errors
Posted:
Mar 11, 2009 4:20 PM PDT
in response to: William Moore
|
|
|
Hello,
I saw you are experienced the problem with GoDaddy.
I just hosted my application with GoDaddy.
I have similar problem they cannot resolve.
Did you get your site working?
If yes would like you share the solution?
Thanks a lot,
Jacob
|
|
|
|
Sign in to the AWS Management Console
Create an AWS Account
