I'm getting a 504 Gateway Timeout error for last 2 hours or so. I'm pretty sure nothing has changed on my side.
I'm not getting it on any of my other sites.
I'm getting a 504 Gateway Timeout error for last 2 hours or so. I'm pretty sure nothing has changed on my side.
I'm not getting it on any of my other sites.
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by Jaykul on 31 Mar, 2011 07:59 PM
Me Too! HELP!
Not sure if this helps, but it's only affecting https://2011sg.poshcode.org/ and not http://2011sg.poshcode.org/
#2 Posted by friism Support staff on 31 Mar, 2011 08:27 PM
As of right now (13:26 PDT), I'm not seeing timeouts for either http or https. We're investigating further.
#3 Posted by jacob.gable on 31 Mar, 2011 08:57 PM
When you go to http://mvcnews.apphb.com/, you don't get a timeout? Because I am. Can you try from somewhere not on your network? Or have someone else outside your network give that url a try?
I get a page saying
504 Gateway Time-out
nginx/0.8.54
#4 Posted by friism Support staff on 31 Mar, 2011 09:07 PM
This is not caused by end-user networking problems.
For mvcnews, I'm seeing errors like
Cannot open database "db1636" requested by the login. The login failed. Login failed for user 'db1636'.. It might be that your app is timing out, trying to connect to the database. Could you check your connectionstring?We're still investigating this.
#5 Posted by jacob.gable on 31 Mar, 2011 09:09 PM
Those errors are from yesterday and related to my other earlier discussion that was resolved last night.
I had the site running this morning with no database errors. Plus, before, I was getting an actual error page with stacktrace when I had a database error. Now I get nothing for about 30 seconds, then the 504 message.
#6 Posted by friism Support staff on 31 Mar, 2011 09:14 PM
The event errors I'm referring to are current. Also, if I circumvent the loadbalancer (nginx), I get a yellow-screen-of-death with
System.Data.SqlClient.SqlException: Cannot open database "db1636" requested by the login. The login failed.#7 Posted by jacob.gable on 31 Mar, 2011 09:15 PM
Alright, let me drop and recreate the database.
#8 Posted by jacob.gable on 31 Mar, 2011 09:48 PM
I've deleted and re-created the DB a couple times now. I don't know why the database would be getting dropped, but evidently it is.
It's probably a code first, entity framework thing, but I am using the DontDropDBJustDropTables... Initializer and it was working for me this morning.
I'm also able to connect with Management Studio using the credentials for my db connection. I can even create tables and drop them through management studio.
Is there some way my code could have been rolled back to a previous version? I've clicked the deploy next to a previous version from this morning when it was working and it doesn't seem to be doing anything different.
#9 Posted by friism Support staff on 31 Mar, 2011 09:53 PM
If you click deploy on a previous version, AppHarbor will immediately start deployng the old version, although it usually takes a few seconds. If you refresh the application page after clicking deploy, you should be able to confirm the the
activebuild changes.Let us know if you have more questions.
#10 Posted by jacob.gable on 31 Mar, 2011 09:58 PM
Looks like it's back up now. I think I had to send up a commit with something touched to get a rebuild kicked off with my updated connection string.
http://mvcnews.apphb.com
jacob.gable closed this discussion on 31 Mar, 2011 09:58 PM.