2019-09-03 15:18:47 |
Patrik Kernstock |
bug |
|
|
added bug |
2019-09-03 15:18:47 |
Patrik Kernstock |
attachment added |
|
linux-image-4.15.0-60-generic.apport https://bugs.launchpad.net/bugs/1842447/+attachment/5286482/+files/linux-image-4.15.0-60-generic.apport |
|
2019-09-03 15:23:16 |
Patrik Kernstock |
description |
Hello,
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)
3. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
4. Wait a few minutes, then kernel crash appears
Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow-dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2
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,
Patrik |
Hello,
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: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
5. Wait a few minutes, then kernel crash appears
Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow-dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2
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,
Patrik |
|
2019-09-03 15:27:28 |
Timo Nowitzki |
bug |
|
|
added subscriber Timo Nowitzki |
2019-09-03 15:28:17 |
Launchpad Janitor |
linux (Ubuntu): status |
New |
Confirmed |
|
2019-09-03 16:03:21 |
Patrik Kernstock |
summary |
Kernel Panic with linux-image-4.15.0-60-generic when using docker-compose with dns setting |
Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose |
|
2019-09-03 16:20:21 |
jkrakenda |
bug task added |
|
linux |
|
2019-09-03 16:20:33 |
jkrakenda |
bug task deleted |
linux |
|
|
2019-09-03 16:21:53 |
Thomas Kopp |
bug |
|
|
added subscriber Thomas Kopp |
2019-09-03 16:52:12 |
Levin |
bug |
|
|
added subscriber Levin |
2019-09-03 17:45:50 |
Fingerless Gloves |
bug |
|
|
added subscriber Fingerless Gloves |
2019-09-03 18:01:52 |
Tim Koop |
bug |
|
|
added subscriber Tim Koop |
2019-09-03 19:12:44 |
Philipp |
bug |
|
|
added subscriber Philipp |
2019-09-04 09:55:05 |
Wouter Horré |
attachment added |
|
kernel logs of the crash https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+attachment/5286685/+files/kernel_log.txt |
|
2019-09-04 10:06:01 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Bionic |
|
2019-09-04 10:06:01 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu Bionic) |
|
2019-09-04 10:29:38 |
Patrik Kernstock |
linux (Ubuntu Bionic): status |
New |
Confirmed |
|
2019-09-04 10:42:11 |
Pascal Christen |
bug |
|
|
added subscriber Pascal Christen |
2019-09-04 10:48:28 |
do3meli |
bug |
|
|
added subscriber do3meli |
2019-09-04 11:16:09 |
Jan Ole Rundshagen |
bug |
|
|
added subscriber Jan Ole Rundshagen |
2019-09-04 18:27:02 |
Sven |
bug |
|
|
added subscriber Sven |
2019-09-04 19:27:43 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
2019-09-04 19:27:46 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): assignee |
|
Thadeu Lima de Souza Cascardo (cascardo) |
|
2019-09-04 19:27:50 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): importance |
Undecided |
Critical |
|
2019-09-04 19:33:36 |
Thadeu Lima de Souza Cascardo |
description |
Hello,
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: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
5. Wait a few minutes, then kernel crash appears
Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow-dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2
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,
Patrik |
[Impact]
Some fragmentation+NAT workloads will cause kernel BUG/Ooops.
[Test case]
sudo iptables -t nat -I POSTROUTING -j MASQUERADE
sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 60000
[Regression potential]
This could make fragmented packets stop flowing. So, make sure fragmented pings still work.
--------------------------------------------
Hello,
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: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
5. Wait a few minutes, then kernel crash appears
Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow-dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2
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,
Patrik |
|
2019-09-04 19:35:52 |
Thadeu Lima de Souza Cascardo |
description |
[Impact]
Some fragmentation+NAT workloads will cause kernel BUG/Ooops.
[Test case]
sudo iptables -t nat -I POSTROUTING -j MASQUERADE
sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 60000
[Regression potential]
This could make fragmented packets stop flowing. So, make sure fragmented pings still work.
--------------------------------------------
Hello,
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: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
5. Wait a few minutes, then kernel crash appears
Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow-dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2
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,
Patrik |
[Impact]
Some fragmentation+NAT workloads will cause kernel BUG/Ooops.
[Test case]
sudo iptables -t nat -I POSTROUTING -j MASQUERADE
sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 60000
[Regression potential]
This could make fragmented packets stop flowing. So, make sure fragmented pings still work.
ping 192.168.122.1 -s 60000 still works, even with the above nat rule.
--------------------------------------------
Hello,
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: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml)
5. Wait a few minutes, then kernel crash appears
Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow-dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2
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,
Patrik |
|
2019-09-05 07:35:39 |
Sven Gottwald |
bug |
|
|
added subscriber Sven Gottwald |
2019-09-05 08:55:11 |
tsilen |
bug |
|
|
added subscriber tsilen |
2019-09-05 09:50:36 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
2019-09-05 09:58:47 |
Andreas Perhab |
bug |
|
|
added subscriber Andreas Perhab |
2019-09-05 17:37:16 |
Ubuntu Kernel Bot |
tags |
|
verification-needed-bionic |
|
2019-09-05 18:04:56 |
Patrik Kernstock |
tags |
verification-needed-bionic |
verification-done-bionic |
|
2019-09-05 19:38:48 |
Joschua Kreimer |
linux (Ubuntu Bionic): status |
Fix Committed |
In Progress |
|
2019-09-05 19:38:52 |
Joschua Kreimer |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
2019-09-06 06:04:25 |
André Peters |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2019-09-06 13:46:36 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): status |
Fix Released |
Fix Committed |
|
2019-09-06 17:42:52 |
Ohad Lutzky |
bug |
|
|
added subscriber Ohad Lutzky |
2019-09-07 17:11:25 |
Roddie Hasan |
bug |
|
|
added subscriber Roddie Hasan |
2019-09-08 10:01:52 |
Oliver Mueller |
bug |
|
|
added subscriber Oliver Mueller |
2019-09-08 10:02:10 |
Oliver Mueller |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2019-09-08 10:28:47 |
Patrik Kernstock |
linux (Ubuntu Bionic): status |
Fix Released |
Fix Committed |
|
2019-09-08 22:27:47 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
2019-09-08 23:47:04 |
Ewen McNeill |
bug |
|
|
added subscriber Ewen McNeill |
2019-09-09 03:02:39 |
Matt C |
bug |
|
|
added subscriber Matt C |
2019-09-09 07:43:27 |
Dr. Jens Harbott |
bug |
|
|
added subscriber Dr. Jens Harbott |
2019-09-09 12:24:01 |
Christopher Teutsch |
bug |
|
|
added subscriber Christopher Teutsch |
2019-09-09 13:48:54 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2019-09-09 19:46:13 |
mouse256 |
bug |
|
|
added subscriber mouse256 |
2019-09-10 12:00:57 |
Magnus Bergman |
bug |
|
|
added subscriber Magnus Bergman |
2019-09-10 14:15:39 |
Km olsen |
bug |
|
|
added subscriber Km olsen |
2019-09-10 18:31:33 |
Charles Schweizer |
bug |
|
|
added subscriber Charles Schweizer |