database issue after updating

[AntouanK]

• Gitea version (or commit ref):
• Git version:
• Operating system: Linux arch (using docker containers)
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

After updating the docker images, I get this in the docker-compose logs

gitea_1     | 2017/09/21 15:13:08 [T] Custom path: /data/gitea
gitea_1     | 2017/09/21 15:13:08 [T] Log path: /data/gitea/log
postgres_1  | ERROR:  column "can_push" of relation "protected_branch" does not exist at character 31
postgres_1  | STATEMENT:  UPDATE "protected_branch" SET "can_push" = $1, "updated_unix" = $2 
...

It keeps repeating those 4 lines, and the web interface won't load.
Any ideas what's wrong?

Thanks

[daviian]

Unfortunately introduced with #2560

@lafriks PR #2451 dropped column can_push

[lafriks]

Oh, I thought it did not drop column. I will fix my migration just then to add it back

[AntouanK]

So how can I fix it?

[daviian]

@AntouanK @lafriks said he will change his migration to fix this.

As you updated to current master, I guess it isn't a productive system?

[AntouanK]

It's a server at home for my personal projects. But it's blocking all my repos now!
Should I revert to an older docker image manually?

I don't think that reverting to an older docker image will fix your issue. The can_push column in the protected_branch table has been deleted. I recreated the column in the database and now I have gitea running again with the latest docker image.

[AntouanK]

I just pulled the latest, and I still get those lines. ( and the web interface is not working )

gitea_1     | 2017/09/22 08:26:21 [T] Custom path: /data/gitea
gitea_1     | 2017/09/22 08:26:21 [T] Log path: /data/gitea/log
postgres_1  | ERROR:  column "can_push" of relation "protected_branch" does not exist at character 31
postgres_1  | STATEMENT:  UPDATE "protected_branch" SET "can_push" = $1, "updated_unix" = $2 

[daviian]

Like @nellonican said you have to create the can_push column manually afterwards as a temporary fix

@AntouanK What I did was:

Log in to my postgres database and give the following commands:

gitea-# \c gitea
gitea-# alter table protected_branch add column "can_push" boolean;
gitea-# \q

After that i had to do a docker-compose down and docker-compose up -d

[daviian]

@nellonican @AntouanK You should set the column to NOT NULL DEFAULT false as well

@daviian Thx. Will do.

[AntouanK]

I never used postgres, can you tell me how to log in?
I guess I can do docker exec on the running postgres container somehow to run those commands?