Closed insanemal closed 3 years ago
Please upgrade to a recent version so that we could know if it has been resolved.
I can't seem to get it to upgrade past 1.9
When I roll to 1.10 it takes too long doing the migration so k8's kills it.
It seems to resume when the pod gets started up again, however it went on like that for at least an hour without actually bringing gitea online.
Is that to be expected? If so I guess I can just leave it crank away and see how long it takes
Oh and to be clear when I attempted to go to 1.10, I did a database backup before
And when I aborted it, I restored the 1.9 database.
You can use the new gitea program and then migrate database via gitea migrate
manually.
This looks to be solved thanks
[x]
):When using gitea via web or via git, everything (repos/heatmaps) travel backwards and forwards in time. So for example if you are on the dashboard. It will show you the up to date status. Hit refresh and you get months ago. Hit refresh again you might get a 500 error. Hit refresh again and you will get one of the 3 above states.
The same thing happens with repos via both SSH or HTTP/s git. You go to push/pull you'll either not be able to because the repo doesn't exist or it works or something very strange happens.
The logs (which I currently have set to trace, show almost nothing unusual.
When there is a 500 error this can be seen in the logs
This is what I see when a repo works and then doesnt work,
Randomly I saw "Unexpected EOF" errors returned from the "[MYSQL]" logging entry. However they did not appear to be clearly linked to any events
This was running 1.7 and I upgraded to 1.8 and then 1.9 in the hopes of fixing it.
I have stopped upgrading it as things are clearly not in a good place ...
Screenshots