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

Calling Ort Script returning 500 immediately #40

Closed
KevinMackenzie opened this issue Nov 15, 2017 · 4 comments
Closed

Calling Ort Script returning 500 immediately #40

KevinMackenzie opened this issue Nov 15, 2017 · 4 comments

Comments

@KevinMackenzie
Copy link
Owner

KevinMackenzie commented Nov 15, 2017

When calling the ort script now, it immediately returns a 500 error. The systemctl logs don't show any errors and the golang service is running. Started as late as f005650

@KevinMackenzie
Copy link
Owner Author

This seems to happen in both the slightly older version of the script and the current one at the master

@KevinMackenzie
Copy link
Owner Author

The ort script is now returning 401 errors for everything instead

@KevinMackenzie
Copy link
Owner Author

We're getting 500 errors again, but now it's because of invalid database access. These errors take the form of ERROR: servers_update_status.go:89: could not execute select server update status by hostname query: pq: column use_reval.value does not exist. I am not entirely sure why this is happening, but it doesn't seem to be happening in an installation with the upstream master.

@KevinMackenzie
Copy link
Owner Author

After updating from upstream/master and making commit 54fca931cb65d25fb982c472e3b916f4c2df8493 . Theses errors no longer show up in the log or in the ort script.

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

1 participant