Hi all,
After the usual apt update && apt upgrade -y
I started a do-release-upgrade
. Only to find it stalls at this point:
[...]
Setting up gsettings-desktop-schemas (3.36.0-1ubuntu1) ...
Setting up php-pspell (2:7.4+75) ...
Setting up gcc-9 (9.4.0-1ubuntu1~20.04.1) ...
Setting up mysql-server-8.0 (8.0.31-0ubuntu0.20.04.2) ...
Installing new version of config file /etc/apparmor.d/usr.sbin.mysqld ...
Installing new version of config file /etc/mysql/mysql.conf.d/mysqld.cnf ...
update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode
Renaming removed key_buffer and myisam-recover options (if present)
mysqld will log errors to /var/log/mysql/error.log
This eventually results in an inaccessible system, so there are no logs I can consult as I need to restore the snapshot.
Are there any steps I could take?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello @emiljacobs
The recovery console will give you access to the droplet in case an ssh-client is unable to connect to your droplet (e.g timeout errors and etc).
If you’re unable to access the droplet via the console as well, poke us here, or don’t hesitate to get in touch with our support team.
Regards
Hi @emiljacobs,
What do you mean by an inaccessible system? Is there no network or does the Droplet completely break down? Additionally, have you tried using the Recovery Console and if yes what was the outcome?
https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/
My best advice would be before trying to restore from a snapshot to use the Recovery Console, get access to your Droplet and trouble shoot the issues that are preventing it form being reached.