please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794169
Title:
AWS ubuntu became unreachable
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794169
Title:
AWS ubuntu became unreachable after ssh login
To manage notifications about this bug go to:
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794169
Title:
AWS ubuntu became unreachable after ssh login
To manage notifications about
information attached and status changed.
i'm using linux-image-4.15.0-1021-aws. based on
https://packages.ubuntu.com/bionic/linux-image-4.15.0-1021-aws it
maintained my Ubuntu Core.
Also i'm not 100% sure that issue in the kernel.
--
You received this bug notification because you are a member
apport information
** Tags added: apport-collected ec2-images
** Description changed:
I've reached strange situation with Ubuntu 18.04 LTS with latest kernel
on AWS m5.xlarge instance.
System became unreachable after series of successful ssh logins. systemd
-user became zombie and
Not sure whether the issue is a poor interaction with sd-pam and the
kernel or strictly a kernel issue.
Kernel timeout backtrace:
Sep 21 03:00:33 mainframe01 kernel: [292411.276266] Not tainted
4.15.0-1021-aws #21-Ubuntu
Sep 21 03:00:33 mainframe01 kernel: [292411.277931] "echo 0 >
