|
Discussion Forums
|
Thread: Massive (500) Internal Server Error.outage started 35 minutes ago
|
|
|
Replies:
116
-
Pages:
8
[
1
2
3
4
5
| Next
]
-
Last Post:
Feb 21, 2008 1:43 PM
by: sequoyan
|
|
|
Posts:
57
Registered:
3/14/07
|
|
|
|
Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 5:00 AM PST
|
|
|
Massive (500) Internal Server Error.outage started 35 minutes ago. Sample response:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InternalError</Code>
<Message>We encountered an internal error. Please try again.</Message>
<RequestId>A2A7E5395E27DFBB</RequestId>
<HostId>f691zulHNsUqonsZkjhILnvWwD3ZnmOM4ObM1wXTc6xuS3GzPmjArp8QC/sGsn6K</HostId>
</Error>---> System.Net.WebException: The remote server returned an error:(500) Internal Server Error.
|
|
Posts:
94
Registered:
6/6/06
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 5:04 AM PST
in response to: maxcc
|
|
|
Seems to apply to other services like SQS and SimpleDB also.
I wonder if it has anything to do with the EC2 Nat migration scheduled for today?
Hopefully we will soon get som answers from Amazon...
|
|
Posts:
163
Registered:
2/8/06
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 5:11 AM PST
in response to: Mikkel
|
|
|
We're investigating.
Thanks,
Kathrin
|
|
Posts:
5
Registered:
11/5/07
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 5:34 AM PST
in response to: maxcc
|
|
|
Hi, what is the dead line to fix this inssue, because i have many clients using the
S3
service.
Thanks
|
|
Posts:
25
Registered:
1/9/07
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:03 AM PST
in response to: maxcc
|
|
|
We are seeing the same thing with our website, which hosts all videos on Amazon S3. What is the ETA for getting this back up? Please keep us posted on the forums, since this is mission critical for some.
Thanks.
|
|
Posts:
163
Registered:
2/8/06
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:03 AM PST
in response to: gcaetano
|
|
|
We can confirm the high error rate you’re experiencing. While we don’t have an ETA at this point, we’re working as quickly as possible to restore performance.
We’ll provide updates as soon as we have them.
Thanks,
Kathrin
|
|
Posts:
5
Registered:
5/16/06
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:04 AM PST
in response to: maxcc
|
|
|
This is still a problem - since 7:30am Eastern Time, we've had these messages:
<Error><Code>InternalError</Code><Message>We encountered an internal error. Please try again.</Message><RequestId>2433D8D5AE03885A</RequestId><HostId>Zz1uFUDV5qGTp6lnvBDh2MZBBJx/N1ds5QSffwfSto5MStXJ9axNxsEtuClJNwOW</HostId></Error>
|
|
Posts:
17
Registered:
9/12/07
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:06 AM PST
in response to: emergentmusic
|
|
|
And this is why you have to setup a fail-safe. My new sites hosts over 25,000 images on Amazon and I wake up to notice major issues this morning. I switched over to using my local server and everything is back up...I really need to set something up so it does this automatically.
The s3 service is great but this just proves you can't rely on it, this is a major issue especially since it's been down for so long. Way to go Amazon.
|
|
Posts:
25
Registered:
1/9/07
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:11 AM PST
in response to: Kathrin@AWS
|
|
|
Unfortunately I think this is a 100% error rate for us - S3 is just inaccessible.
Please keep us posted - when you have an ETA (or figured out the problem/fix) please relay it to us. Given the SLA, etc. we are using S3 in a production environment.
|
|
Posts:
1
Registered:
2/15/08
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:11 AM PST
in response to: Ryan Robert Det...
|
|
|
I have to add a major ME TOO here. My business is effectively closed right now because Amazon did something wrong. I'll have to reconsider using the service now.
|
|
Posts:
63
Registered:
7/7/06
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:13 AM PST
in response to: Kathrin@AWS
|
|
|
Hello,
it might be also useful to know that for about an hour I couldn't sign in to this forum because clicking the Login link generated a 404 error.
now luckily I'm logged in and can post again.
this is really a widespred error error. I can't see manage any of my S3 accounts, all public objects can't be reached (500 Internal Server Error).
I have been told though that from Australia when switching from HTTP to HTTPS the objects can be retrieved though...
having an idea of the ETA to resume 'normal' service is essential.
best regards
andrea
|
|
Posts:
1
Registered:
2/15/08
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:15 AM PST
in response to: maxcc
|
|
|
Whine Whine Whine... could we be a bit more dramatic? This is the first outage I have experienced since I joined the service nearly a year ago. Yes it sucks, yes I hope they get it fixed very soon... but, the sky is not in fact falling at the moment.
If you rely on a single point of storage for mission critical data, well then, you've got bigger problems.
|
|
Posts:
31
Registered:
1/13/07
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:16 AM PST
in response to: A. Barbieri
|
|
|
We have the same issue here @ 14:16 GMT
Unable to login via transmit and problems requesting public images. Getting the following error:
Http/1.1 Service Unavailable
|
|
Posts:
9
Registered:
9/6/06
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:17 AM PST
in response to: A. Barbieri
|
|
|
yea this is extremely widespread,
all my s3 properties are experiencing it. Even twitter is too.
|
|
Posts:
63
Registered:
7/7/06
|
|
|
|
Re: Massive (500) Internal Server Error.outage started 35 minutes ago
Posted:
Feb 15, 2008 6:17 AM PST
in response to: Kathrin@AWS
|
|
|
it's a 100% error rate not just high. S3 service has stopped working about 2 hours ago. this is really a severe blow to confidence in trusting AWS services.
regards,
andrea
|
|
|
|
Sign in to the AWS Management Console
Create an AWS Account
