Error when "Checking for updates"

[shadowninja108]

When init of the CIA version, it shows this error slightly after "Checking for updates". The data and time are set correctly (might be a minute off). Not sure what other variables I can list.

[Wolvan]

This seems to be a problem with TitleDB right now, if you go to https://api.titledb.com/v0/ it should give you an app list in json format but it only gives error 502 Bad Gateway for me.

@ksanislo did you break something?

[ksanislo]

Looks like the new WSGI backend ran the server out of memory and it started OOM-killing processes. I've got a bug that is forcing me to keep titledb running in debug mode for the moment actually, which is most likely a big part of the problem. If I can't find a solution soon I'm going to have to switch back to the v0 codebase until I can figure out why running under production settings is causing database transaction problems that don't appear when set as devel.

Anyway, it should be back for now. Sorry about the downtime. On Wed, Dec 7, 2016 at 12:51 AM Wolvan notifications@github.com wrote:

This seems to be a problem with TitleDB right now, if you go to https://api.titledb.com/v0/ it should give you an app list in json format but it only gives error 502 Bad Gateway for me.

@ksanislo https://github.com/ksanislo did you break something?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Wolvan/Homebr3w/issues/28#issuecomment-265390717, or mute the thread https://github.com/notifications/unsubscribe-auth/AECriAwSsa2jBSMqXMQr8oX1H8OSZTgAks5rFnOTgaJpZM4LGMnw .

[Wolvan]

Thx k, good to know

[Wolvan]

Just checked, now the site doesn't send a reply at all it seems Edit: Nvm, all of a sudden it works

[ksanislo]

I've rolled back to the v0 code... I don't have time to troubleshoot the db locking issue at the moment, so I'll let the old stuff run a few more days until I can figure out the real root cause.

[Wolvan]

Closing this since it seems fixed