-
-
Notifications
You must be signed in to change notification settings - Fork 377
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
API returns HTTP status 500 after a few days #431
Comments
I'm experiencing the same problems. I'm using Aptly 0.9.7 on Ubuntu Xenial. The problem showed up after a few days. It was still possible to go to the version endpoint, /api/version. Things that did not work was e.g /api/publish or /api/snapshots.
Any progress or ideas about this? |
We're still seeing the same problem here and have resorted to just restarting aptly whenever /api/publish requests fail. It's far from ideal but that's the only reasonable thing we managed to come up with, short of learning Go and debugging this ourselves. :) |
I wonder if that got fixed in the latest nightly build (https://www.aptly.info/download/). We have bumped goleveldb version since then. |
We are also experiencing this problem with version 1.0.1: 2017/05/15 08:49:15 PANIC: runtime error: invalid memory address or nil pointer dereference |
Looks like some kind of a race here, I'll take a look. Thanks for reporting it! |
When DB fails to be open, aptly was skipping "close" phase, so that next request considered database to be still open (while it's closed) leading to panic. Fixes: #431
After a few days of running just fine I'm getting HTTP status code 500 when trying to update a repository:
While trying to analyze the problem I've noticed that the thread that's used to handle the request is getting a SEGV signal:
Here's a stacktrace for that signal:
I've been unable to easily reproduce this issue. It just tends to start happening after a few days. However, once it does happen all further POST requests for repos will fail in the same manner.
The text was updated successfully, but these errors were encountered: