Would you know where I can find the logs ? I don't find anything except this "502".
2014-05-07 10:46 GMT+02:00 LEDUQUE Mickaël <[email protected]>: > First attempt to solve it on my side, I tried to answer "abandon" then > downgrade to 1.11. > Now I get HTTP 502 (bad gateway, it's served by nginx) on every request. > > 2014-05-07 1:39 GMT+02:00 Sebastian Reichel <[email protected]>: >> On Tue, May 06, 2014 at 11:37:40PM +0200, LEDUQUE Mickaël wrote: >>> Hi, >>> I'm the same person that reported this bug. >>> I never had your last answer, sorry. I don't remember using this email >>> address. It's not valid. >> >> ok. >> >>> I fixed the problem at some point, but I don't remember how, probably >>> with some SQL voodoo. >> >> should be fixable by reversing the database update, so that it >> can be applied cleanly. >> >>> One thing I'm sure : I had neither touched the database nor done >>> "upstream migration" before apt upgrade that caused this. >> >> that's weird, because for some reason you already had the updated >> database schema when apt tried to update it. >> >>> I only found I had reported this bug because I was looking for the >>> reason of a similar upgrade failure, with a diferent column, >>> resetpass_token this time. >>> This bug is definitely unreproducible now, but I'll open a new one for >>> resetpass_token. >> >> That seems to be the same bug. I can't reproduce it, though. >> >>> BTW, is the database upgrade fragile ? >> >> not that I'm aware of. I have my own instance of tt-rss and upgrade >> it using the same package, which is uploaded to Debian. Actually I >> only upload it after testing it on my instance for 1-2 days. >> >> P.S.: I removed upstream's upgrade plugin from the 1.12 release, >> which I uploaded to unstable some hours ago. >> >> -- Sebastian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
