[Bug]: Upgrade 4.0.0-beta-364 completely broke setup - rollback not working
on3iro opened this issue · 8 comments
Error Message and Logs
I just pressed the upgrade button and suddenly received a 500 from the3 system. If I interpret the logs correctly there seems to be an issue with redis. Though I don't find a way to directly interact with coolifies stack.
When trying to rollback I receive an error because coolify tries to write the /data/coolify-directory. I don't want to delete this directory, because it looks like this is, where all my data is stored.
What's the best way to move forward here?
Steps to Reproduce
- Just started the new upgrade
- System was no longer reachable
- Downgrade didn't work due to existing
/data/coolifydirectory
Example Repository URL
No response
Coolify Version
v4.0.0-beta-364
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response
Some mor} logs I found when checking coolifies container logs:
ERROR The [public/storage] link already exists.
[09-Nov-2024 15:07:00] NOTICE: fpm is running, pid 100
[09-Nov-2024 15:07:00] NOTICE: ready to handle connections
[09-Nov-2024 15:07:00] NOTICE: systemd monitor interval set to 10000ms
In PhpRedisConnector.php line 159:
php_network_getaddresses: getaddrinfo for coolify-redis failed: Temporary f
ailure in name resolution
In PhpRedisConnector.php line 159:
Redis::connect(): php_network_getaddresses: getaddrinfo for coolify-redis f
ailed: Temporary failure in name resolution
s6-rc: warning: unable to start service db-migration: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
prog: fatal: stopping the container.
[09-Nov-2024 15:05:48] NOTICE: Terminating ...
[09-Nov-2024 15:05:48] NOTICE: exiting, bye-bye!
I found the docker-compose setup of coolify in /data/coolify/source and was able to up -d the whole stack. At first glance it seems to be working again and the missing services are up again
Was able to re-run the upgrade script in /data/coolify/source/upgrade.sh and got everything working again.
Running the script worked for me as well. Thanks!
Didn't break anything for me but upgrade got stuck with this in the logs:
Container coolify-redis Recreate
Container coolify-db Recreate
Error response from daemon: Conflict. The container name "/81247cc4cdea_coolify-db" is already in use by container "1cac127...". You have to remove (or rename) that container to be able to reuse that name.
Didn't break anything for me but upgrade got stuck with this in the logs:
Container coolify-redis Recreate Container coolify-db Recreate Error response from daemon: Conflict. The container name "/81247cc4cdea_coolify-db" is already in use by container "1cac127...". You have to remove (or rename) that container to be able to reuse that name.
Make sure to create a backup for
coolify-dbbefore proceeding.
Maybe you could try running a command like docker rm 81247cc4cdea_coolify-db, though I'm not sure if the attached volume would also be removed.
Had the same problem.
Upgrading from v4.0.0-beta.360 to v4.0.0-beta.364 and I got an timeout.
After I refreshed the page, I always got an gateway timeout and a reboot also didn't helped.
Running the mentioned script /data/coolify/source/upgrade.sh worked for me too.
Webinterface is reachable again.
Running under Ubuntu 22.04.5 LTS
Same problem, going from 362 to 364, clicked Upgrade, now it's a permanent 500 Internal Error trying to access Coolify.
This fixed it for me too: sh /data/coolify/source/upgrade.sh