Ubuntu Upgrade from 18.04 to 20.04 Lightsail

0

I see New release '20.04 LTS' available. I tried to do a 'do-release-upgrade' to upgrade my ubuntu lightsail from 18,04 to 20,04. It started and went through but got stuck when trying to start the mysql server 8.0. I think it upgraded from 5.7. ubuntu@ip-172-26-7-175:$ mysql -V mysql Ver 8.0.34-0ubuntu0.20.04.1 for Linux on x86_64 ((Ubuntu)) ubuntu@ip-172-26-7-175:$ sudo systemctl status mysql ● mysql.service Loaded: masked (Reason: Unit mysql.service is masked.) Active: failed (Result: exit-code) since Wed 2023-09-06 16:42:32 UTC; 40min ago Main PID: 947 (code=exited, status=0/SUCCESS)

Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Service hold-off time over, scheduling restart. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 6. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: Stopped MySQL Community Server. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Start request repeated too quickly. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Failed with result 'exit-code'. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: Failed to start MySQL Community Server. ubuntu@ip-172-26-7-175:$ sudo systemctl start mysql Failed to start mysql.service: Unit mysql.service is masked. ubuntu@ip-172-26-7-175:$ sudo systemctl status mysql ● mysql.service Loaded: masked (Reason: Unit mysql.service is masked.) Active: failed (Result: exit-code) since Wed 2023-09-06 16:42:32 UTC; 42min ago Main PID: 947 (code=exited, status=0/SUCCESS)

Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Service hold-off time over, scheduling restart. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 6. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: Stopped MySQL Community Server. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Start request repeated too quickly. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: mysql.service: Failed with result 'exit-code'. Sep 06 16:42:32 ip-172-26-7-175 systemd[1]: Failed to start MySQL Community Server. ubuntu@ip-172-26-7-175:$ ^C ubuntu@ip-172-26-7-175:$ sudo systemctl unmask mysql.service Removed /etc/systemd/system/mysql.service. ubuntu@ip-172-26-7-175:$ sudo systemctl start mysql Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. ubuntu@ip-172-26-7-175:$ sudo systemctl start mysql Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. ubuntu@ip-172-26-7-175:~$ sudo systemctl status mysql ● mysql.service - MySQL Community Server Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-06 17:32:53 UTC; 4s ago Process: 29759 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)

Sep 06 17:32:53 ip-172-26-7-175 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5. Sep 06 17:32:53 ip-172-26-7-175 systemd[1]: Stopped MySQL Community Server. Sep 06 17:32:53 ip-172-26-7-175 systemd[1]: mysql.service: Start request repeated too quickly. Sep 06 17:32:53 ip-172-26-7-175 systemd[1]: mysql.service: Failed with result 'exit-code'. Sep 06 17:32:53 ip-172-26-7-175 systemd[1]: Failed to start MySQL Community Server. ubuntu@ip-172-26-7-175:$ mysql -V mysql Ver 8.0.34-0ubuntu0.20.04.1 for Linux on x86_64 ((Ubuntu)) ubuntu@ip-172-26-7-175:$

I checked the ubuntu version and it has upgraded to 20.04

ubuntu@ip-172-26-7-175:$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal ubuntu@ip-172-26-7-175:$

I am on the lightsail 2GB RAM $10 version

gefragt vor 8 Monaten387 Aufrufe
1 Antwort
0

This post appears to be related: https://repost.aws/questions/QU6JgZRjHCTTOd2MIXxChDvA/lightsail-ubuntu-mysql-8

If you are running on a nano (512 MB RAM) the new software may now require a more powerful instance.

AWS
MODERATOR
beantwortet vor 8 Monaten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen