$ curl https://apps.fedoraproject.org/koschei/package/rubygem-slim <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>500 Internal Server Error</title> <h1>Internal Server Error</h1> <p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>
$ date Wed Jul 4 18:57:02 CEST 2018
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Problem seems to have started when koschei packages were updated last night. TIme stamp of errors happens when
2018-07-03T21:18:28Z INFO Upgraded: koschei-common-2.4.0-1.fc28.noarch 2018-07-03T21:18:29Z INFO Upgraded: koschei-frontend-2.4.0-1.fc28.noarch 2018-07-03T21:18:29Z INFO Upgraded: koschei-common-fedora-2.4.0-1.fc28.noarch 2018-07-03T21:18:31Z INFO Upgraded: koschei-common-copr-2.4.0-1.fc28.noarch
The previous version was koschei-common-copr-2.3.1-1.fc28.noarch
I have backed it down to 2.3.1 and it seems like the app is running. However I am still seeing a lot of 500's in the logs so I am not sure what is happening.
I will let @mizdebsk take over on this.
Metadata Update from @kevin: - Issue assigned to mizdebsk - Issue priority set to: Waiting on Assignee (was: Needs Review)
Backwards-incompatible update was pushed to Fedora 28 stable and it was installed during infra maintenance. Thanks @smooge for reverting this. I consider the issue resolved for now, but I will need to upgrade Koschei to latest version available in stable update repos, so this doesn't happen in future.
Metadata Update from @mizdebsk: - Issue close_status updated to: Fixed - Issue priority set to: None (was: Waiting on Assignee) - Issue status updated to: Closed (was: Open)
I've upgraded Koschei to latest available version, so this problem should not happen again (unless incompatible updates are pushed to stable again...)