[CLOSED] Update from 1.8 to 1.8.1 failing

I have spent the past 2 hours trying to figure this out but I really dont know what to do. 1.8. was a fresh install because the upgrade from 1.7.4 was a total mess. I wanna get this production ready but its just a pain. 1.8.1. now again just reciving error 500 when trying to log into the console. Logs in the containers do not show much, I do not know where to look...

can anyone please help me find the right direction, I am really loosing my mind. Its just a simple upgrade from 1.8.0 to 1.8.1, it shouldnt be that messy no?

the logs just give 'unknown resource type' for everything...

I had to revert to 1.7.5, run the migration, install 1.8.0, run the migration again, and now it works, even the backups. I went straight to 1.8.1 and migration, it seems that caused the problem

So 1.8 to 1.8.1 caused the issue?

1.7.4 > 1.8.1

I didn't go back to upgrade to 1.8.1, but reverting to 1.8.0 solved the problem.

Or maybe it was because it was necessary to run the 1.8.0 migration and then 1.8.1. I only ran the 1.7.5 migration and went straight to 1.8.1 and migrated. And I had this timeout problem.

Yeah you always need to upgrade to major versions first you cannot upgrade from 1.7.4 to 1.8.1 in one step... I wanted to upgrade from 1.8.0 to 1.8.1 and it destroyed everything...

I actually realized that the problem was caused by the cron job I had for backups; for some reason in version 1.8 it causes MariaDB to freeze and time out.

`docker-compose exec mariadb sh -c
\ 'exec mysqldump
\ --single-transaction
\ --quick
\ --skip-lock-tables
\ -u"user" -p"password" appwrite' \

backupDaily/dump-$(date +%F).sql`

I edited it like this and the problem was solved

[SOLVED] Update from 1.8 to 1.8.1 failing

@Guille why did you close it? It’s not resolved? Hortigado is talking about a completely different issue that has nothing to do with my problem.

@hortigado this has nothing to do with my initial issue, why are you writing those things here? I don’t have cronjobs for backups.

I'm sorry I didn't realize it was a different user. I'll open it again

Update from 1.8 to 1.8.1 failing

That's correct, your migration is corrupted; you'll have to run a backup.

What was your appwrite version before 1.8?

1.8 was a fresh install

Please check the server logs with docker compose logs appwrite and paste the error here

I've upgrade to 1.8.1 recently and I didn't have any trouble

I did in the beginning already but I decided to trash everything and start from scratch and finally move away from coolify. Upgrading with coolify has been an absolute mess. And with Termix handling all of it is much easier anyway. So I guess we can now indeed close I dont know what went wrong.

but thanks <@365301924607557634> anyway, I appreciate it 🙂

[CLOSED] Update from 1.8 to 1.8.1 failing