- Le plus récent
- Le plus de votes
- La plupart des commentaires
davidg50,
Thanks for using Lightsail. I am sorry to hear that you are having trouble with this setup. With problems like these the first thing I do is see if I can't easily reproduce the issue by trying what you did. I started up a Nano sized instance running Ubuntu 20.04 LTS and then issued the same command you mention below once it had come up.
On the Nano instance my installation also failed and I experienced some CPU throttling as well. /var/log/syslog had this to say:
Sep 28 23:49:48 ip-172-26-10-28 kernel: [ 1677.033109] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/mysql.service,task=mysqld,pid=5995,uid=113
Sep 28 23:49:48 ip-172-26-10-28 kernel: [ 1677.033132] Out of memory: Killed process 5995 (mysqld) total-vm:731884kB, anon-rss:270104kB, file-rss:2012kB, shmem-rss:0kB, UID:113 pgtables:772kB oom_score_adj:0
Sep 28 23:49:48 ip-172-26-10-28 kernel: [ 1677.064135] oom_reaper: reaped process 5995 (mysqld), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
So it seems the server daemon ran out of memory during startup.
I tried this on the next size up (Micro) and it worked without problems.
If you are using our smallest size instance to do this, you may consider bumping that up to the Micro size. If you are not using the Nano, please provide any snippets from your syslog or mysql error.log files to help diagnose the issue.
I hope this helps!
Donley
Hello,
It seems mysql-server uses so much memory these days but yea that fixed my issue. I selected the 1GB ram lightsail instance and it went away.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans