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

On creating new site get Server Error (500) #537

Closed
neilh10 opened this issue Dec 15, 2021 · 4 comments
Closed

On creating new site get Server Error (500) #537

neilh10 opened this issue Dec 15, 2021 · 4 comments
Assignees

Comments

@neilh10
Copy link

neilh10 commented Dec 15, 2021

On creating a new site, I get a Server Error (500)

image

however it is created.
Initially I created it with no notifications, but then went in and edited the site and change to Notifications, and saved and got the 500
I tried updating Site information with "Edit", and changed the "Notes" to slightly different text
then Save edits
I again get Server Error (500)

It appears to be repeatable.
I tried creating a new site https://monitormywatershed.org/sites/tu_rc_xx99/ and the same result - Server Error (500)

@neilh10
Copy link
Author

neilh10 commented Dec 15, 2021

On creating a sensor, adding the details, and pressing "Add New Sensor", the window never says its complete,
image

however if the CANCEL is pressed, and then browser refreshed, the sensor has been created.

image

@aufdenkampe
Copy link
Member

@neilh10, thanks for this report. We'll look into it.

We were doing some hot-fixes to the database yesterday, but those would have only resulted in momentary issues an it seems that your observations were repeatable. Thanks!

ptomasula added a commit that referenced this issue Dec 16, 2021
There is was code running that still referenced the now removed TSA catalog database. This results in a 500 response being return for certain operations and indicated in #537 and #538
@ptomasula
Copy link
Collaborator

ptomasula commented Dec 16, 2021

@neilh10, thanks for the testing and reporting this issue. This looks to have been caused by some old TSA related syncing code that was still running on the application. Because we're removed TSA, the end point for that code was not available and it produced the 500 response that you reported.

@aufdenkampe as a hot fix, I've commended out that code and pushed an update to the production server. Longer term we'll go through the code base and do a proper refactoring and clean up. I'm sure this isn't the only piece of code in there. Looking forward to milestone 19

@neilh10
Copy link
Author

neilh10 commented Dec 16, 2021

great, I created a test site
https://monitormywatershed.org/sites/nhtest2112161440/
and it worked.
Now deleted.

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

No branches or pull requests

3 participants