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

Internal Server Error - AZ Dems Nomad #734

Open
flynnwastaken opened this issue Oct 15, 2018 · 9 comments
Open

Internal Server Error - AZ Dems Nomad #734

flynnwastaken opened this issue Oct 15, 2018 · 9 comments
Labels

Comments

@flynnwastaken
Copy link
Contributor

On Chrome in Chromebook, clicking between homepage and Profile while logged into Admin account, both when selecting the homepage by clicking the logo in the upper left corner and when going to the Profile from the homepage using the dropdown user menu I've gotten "Internal Server Error"
screenshot 2018-10-15 at 4 07 08 pm

@jillh510
Copy link
Contributor

@flynnwastaken , any other steps to reproduce the bug? Is your profile complete, or are you on the profile page to fill it out?

I'm not seeing it on Chrome/MacOS fwiw.

@iandees
Copy link
Member

iandees commented Oct 16, 2018

This looks to be a transient error here: https://sentry.ragtag.org/ragtag/nomad-prod/issues/157/

@jillh510
Copy link
Contributor

@iandees this bug is fixed, right?

@iandees
Copy link
Member

iandees commented Oct 17, 2018

We didn't do anything to fix it, but I don't think it's reproducible.

@kcaffall
Copy link
Collaborator

I have not repro'd this, but wondering if it could be caused by bouncing around environments (something Flynn would do, but clients wouldn't)? Different tabs being in production, AZ Dems, NY, like that.

@dryan
Copy link
Contributor

dryan commented Oct 17, 2018

Yeah I agree with Ian that this is transient. I did come across https://stackoverflow.com/questions/31121948/flask-sqlalchemy-cant-reconnect-until-invalid-transaction-is-rolled-back looking up the error message. I wonder if it was a bad migration?

@iandees
Copy link
Member

iandees commented Oct 17, 2018

My guess is that it was an error that happened in another session on this Nomad instance. I poked through the logs quickly to see if there was something that stood out before this error but didn't see anything.

@dryan
Copy link
Contributor

dryan commented Oct 17, 2018

Yeah I agree. I think we're good to close this out (leave it to @jillh510 to decide for sure). If we see this error in production I would suggest re-deploying on Heroku to get a new session opened up.

@jillh510
Copy link
Contributor

I've taken it off the Priority list but would like to leave it open in case anyone sees it again in the next two weeks. If not, then we'll close as "can't reproduce".

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

No branches or pull requests

5 participants