I'm also seeing this on 16.04 on an AWS nano (~0.5GB RAM). More than
happy to help troubleshoot this if people let me know what info is
needed.
Here's some basic info from my machine:
$ uname -a
4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64
x86_64 GNU/Linux
$ free -m
Thank you so much Rasmus!
Your solution worked for me:
sudo touch /etc/udev/rules.d/40-vm-hotadd.rules
reboot
I could always trigger the CPU usage bug with this:
stress --cpu 8 --io 4 --vm 7 --vm-bytes 128M --vm-hang 3 --timeout 60s
If running it once didn't work, a second run would do it. Now I
Did you try this from Rasmussen up above?
sudo touch /etc/udev/rules.d/40-vm-hotadd.rules
reboot
That fixed it for me on EC2
On Saturday, 3 September 2016, Andy Robertson
wrote:
> All of my t2.micro & nano instances are affected by this in AWS EC2
> after upgrading to Ubuntu16.
>
> doing "echo
I've had the issue mostly when running with no swap. I added 1GB swap
file and it fixed it on the machine with less memory usage, but the
machine with the database (using more memory most of the time) still has
the bug occur about once a day.
Ubuntu 16.04 for both, not happening on 14.04.
Sent fr
4 matches
Mail list logo
