Post by @ai6yr@m.ai6yr.org

Random #MastoAdmin question...

Going from v4.4 to v4.5 branch, migrations fail to run. (prior attempt to upgrade failed and I rolled back... not sure if that caused this).

~/live$ RAILS_ENV=production DB_PORT=5432 bundle exec rails db:migrate

"...ActiveRecord::ConcurrentMigrationError: (ActiveRecord::ConcurrentMigrationError)

Cannot run migrations because another migration process is currently running.
."

Last migration processes in status

Any thoughts on next steps (aside from manually removing the ExclusiveLock 😬 )

#mastoadmin

0 Boosts

0 Likes

Hey Gus

@elebertus@eigenmagic.net 2 hr. ago

@ai6yr pre-coffee but can you check the active connects on the db from the host running the migrations?

AI6YR Ben

@ai6yr@m.ai6yr.org 2 hr. ago

@elebertus Hmm, good question, I'll go look at that. I started the migration many days ago, lol.

AI6YR Ben

@ai6yr@m.ai6yr.org 2 hr. ago

So digging into the code... does this status indicate all these migrations are these still running?!?

AI6YR Ben

@ai6yr@m.ai6yr.org 2 hr. ago

Well, started up a new push/pull/default worker using the new v4.5.20 while not touching the old v4.4.27 workers, lol...

AI6YR Ben

@ai6yr@m.ai6yr.org 2 hr. ago

Well, no errors at least from that process being upgraded... May restart some of the other workers, before attempting to restart the web processes.

Zelda

@Zelda@m.ai6yr.org 1 hr. ago

@ai6yr

You're not using the docker version?

I'd particularly avoid restarting Puma until Sidekiq is confirmed healthy. That gives you a cleaner upgrade and troubleshooting sequence.

1+ more replies

Krampus 🌰

@castanea_jo@ni.hil.ist 2 hr. ago

@ai6yr no, they have probably executed before. the timestamps are when they were generated

Krampus 🌰

@castanea_jo@ni.hil.ist 2 hr. ago

@ai6yr there should be a table in your database called schema_migrations that would show you everything that has been run in the past

AI6YR Ben

@ai6yr@m.ai6yr.org 2 hr. ago

@castanea_jo Thanks, will look at that. Perhaps the last try worked and it did not update the lock. (the one I rolled back all the code... presumably the DB ready for the new code versions, lol).

1 more reply