Yesterday around 21:30 GMT, my server on AWS Lightsail crashed. I cannot connect to it through SSH. I am also unable to connect to a separate small server, which checked the uptime of the first. I can connect through browser SSH, but not with SSH, even after restarting the instances.
Since these are two separate servers with no public connection to each other, I wonder if Lightsail may have some technical issues. But as I am on the Basic plan, support is not included.
How can I investigate the problem?
update
I checked four of the logs in /var/log: auth.log, apport.log, kern.log and syslog on the Lightsail instance running a bitnami image and a NodeJS server.
kern-log showed the culprit. Usually it has very few entries, about 5. Around this date, it has 500 lines, starting with:
Jan 29 21:39:41 ip-172-26-9-252 kernel: [ 0.000000] Initializing cgroup subsys cpuset
and ending with:
Jan 29 21:39:41 ip-172-26-9-252 kernel: [ 20.435952] audit: type=1400 audit(1643492358.140:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lxd/lxd-bridge-proxy" pid=708 comm="apparmor_parser"
The other Lightsail instance, running a different image on a different region, and not set up as a web server, shows similar entries around that time. The first line is:
Jan 30 07:27:17 ip-172-26-5-35 kernel: [ 0.000000] Initializing cgroup subsys cpuset
and the last is:
Jan 30 07:27:17 ip-172-26-5-35 kernel: [ 9.476419] cgroup: new mount options do not match the existing superblock, will be ignored
So this seems to have been a Lightsail issue, since it affected two separate instances at about the same time. How can I confirm that?
0 Answers