N8N not starting after new docker pull

Questions
#1

Describe the issue/error/question

N8N isn’t starting anymore. Stuck in migration if I look at the logs. It finds a duplicate column.

What is the error message (if any)?

Migration “CreateLdapEntities1674509946020” failed, error: Duplicate column name ‘disabled’

Information on your n8n setup

  • n8n version: docker:latest
  • Database you’re using (default: SQLite): mariadb 10.6
  • Running n8n with the execution process [own(default), main]:
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: docker

[edit]
I fixed it by adding a line to the ‘migrations’ table in the database, specifying that specific migration with a timestamp of now() …
It pushed through after that - but I don’t know if it broke something.
The migration itself kept adding the “disabled” column to the user table.

#2

Hi @cloudz, welcome to the community and sorry for the trouble.

It seems this particular issue was caused by an earlier image sent to a few users allowing them to test our LDAP functionality.

Perhaps @RicardoE105 or @netroy can confirm whether anything else is needed to fix the migration for good?

#3

Yeah. CreateLdapEntities1674509946020 was part of the LDAP test image, and is not included in any of the released images.

Generally when testing custom images, and then reverting back to a stable image, I highly recommend manually reverting any migrations using n8n db:revert to make sure that there are no invalid migrations in place.

#4

I simply did an docker:latest - so that was probably at the wrong time.
I’ve since moved away from MariaDB and moved everything over to Postgres. It’s running fine now.