Disregard.  Looks like is installed but running uname -a
shows so the box just hasn't been rebooted since the update
and since it's an AWS ASG it's just reverting back to the 1047 version
from the AMI every time it panics and AWS re-creates the instance.  Time
to rebuild the AMI with the new kernel.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Kernel Panic with linux-image-4.15.0-60-generic when specifying
  nameserver in docker-compose

Status in linux package in Ubuntu:
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Some fragmentation+NAT workloads will cause kernel BUG/Ooops.

  [Test case]
  sudo iptables -t nat -I POSTROUTING -j MASQUERADE
  sudo hping3 -s 1000 -p 2000 -d 60000

  [Regression potential]
  This could make fragmented packets stop flowing. So, make sure fragmented 
pings still work.
  ping -s 60000 still works, even with the above nat rule.



  there are multiple inquries in the mailcow GitHub issues over at
  https://github.com/mailcow/mailcow-dockerized/issues/2904 that the
  latest kernel linux-image-4.15.0-60-generic causes kernel panics when
  "- dns" setting is used within the docker-compose.yml file, for yet
  some unclear reasons.

  Multiple users on different systems (e.g. virtualized ones on VMware
  ESXi and KVM) were able to reproduce the same issue. I was also able
  to reproduce this constantly on a completely new deployed Ubuntu 18.04
  VM (KVM) with a fresh mailcow installation.

  Steps to reproduce:
  1. Install a clean Ubuntu 18.04(.03) machine
  2. Upgrade the installation to linux-image-4.15.0-60-generic
  3. Setup mailcow as instructed at 
https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes 
less than a minute, easy to reproduce)
  4. Start mailcow with "dns"-settings specified in docker-compose file (Make 
sure using the older docker-compose version with dns settings: 
  5. Wait a few minutes, then kernel crash appears

  Using this workaround it appears to be stable again:

  I've attached the apport file to this bug. Please let me know if you
  need any kind of further information. (As this is my first bug report
  here, I hope I have included all required information helping you
  finding the cause.)

  Kind regards,

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to