[Bug 1794169] SystemdDelta.txt

Wed Sep 26 16:36:17 UTC 2018

apport information

** Attachment added: "SystemdDelta.txt"
   https://bugs.launchpad.net/bugs/1794169/+attachment/5193229/+files/SystemdDelta.txt

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1794169

Title:
  AWS ubuntu became unreachable after ssh login

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  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 block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0      0     0 ?        Z    02:56   0:00  \_ [(sd-pam)] <defunct>
  apetren+ 26855  0.0  0.0  76636  7816 ?        Ds   02:57   0:00 /lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0      0     0 ?        Z    02:57   0:00  \_ [(sd-pam)] <defunct>
  apetren+ 26954  0.0  0.0      0     0 ?        Zs   02:57   0:00  \_ [kill] <defunct>
  apetren+ 27053  0.0  0.0  76636  7496 ?        Ss   02:58   0:00 /lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?        S    02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubuntu at your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid

  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware                           N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions