It was observed that the ec2 micro has reached it's memory limit, and Ashtam cleaned up few files and restarted to get it back online.
- I have made a local copy of logs (pm2) and removed from server
- journal service logs were flushed and capped at 200 MB now
- Cleaned up old snappd packages (script created fro the same)
However, even after all this, the size increase is because of general bloating of long running Ubuntu services.
Deepdive
Here is the current scenario now:
Filesystem Size Used Avail Use% Mounted on
udev 476M 0 476M 0% /dev
tmpfs 98M 776K 98M 1% /run
/dev/xvda1 7.7G 6.8G 909M 89% /
tmpfs 490M 0 490M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 490M 0 490M 0% /sys/fs/cgroup
tmpfs 98M 0 98M 0% /run/user/1000
/dev/loop6 100M 100M 0 100% /snap/core/11316
/dev/loop5 56M 56M 0 100% /snap/core18/2128
/dev/loop1 25M 25M 0 100% /snap/amazon-ssm-agent/4046
It was observed that the ec2 micro has reached it's memory limit, and Ashtam cleaned up few files and restarted to get it back online.
However, even after all this, the size increase is because of general bloating of long running Ubuntu services.
Deepdive
Here is the current scenario now: