2 Answers
- Newest
- Most votes
- Most comments
0
Have you checked the CPU and Memory metrics? t3.small only has 2GB RAM. I suspect the instances are running low on Memory since you mentioned reboot helps for a while.
0
Thank you alantam. Nie to have a quick response!!
I have it running now on the serial port:
% free -h
total used free shared buff/cache available
Mem: 1.9Gi 389Mi 1.0Gi 2.7Mi 639Mi 1.5Gi
Swap: 0B 0B 0B
I cannot access it currently on the public if with ssh :shrug:
top - 20:07:35 up 33 min, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 107 total, 1 running, 106 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 95.5 id, 0.0 wa, 0.0 hi, 0.0 si, 4.5
MiB Mem : 1910.7 total, 1040.7 free, 387.7 used, 642.5 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1523.0 avail Mem
I cannot afford much time, so yes, I will upgrade the type just to see. But there is something weird going on and I do not think it is related to common resources.
Strange ...
answered 5 months ago
Relevant content
- asked 2 years ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago