agent icon indicating copy to clipboard operation
agent copied to clipboard

Problem with kernel 5.9 or 5.10

Open rudnypc opened this issue 3 years ago • 2 comments

Bug description When I updated my debian 9 to kernel 5.9 or 5.10, the portainer agent doesn't work rigth.

Expected behavior Enable console option

Portainer Logs

BAD AGENT NODE: 2021/04/01 04:39:57 [INFO] [main] [message: Agent running on Docker platform] 2021/04/01 04:39:57 [INFO] [main] [message: Agent running on a Swarm cluster node. Running in cluster mode] 2021/04/01 04:40:00 [INFO] serf: EventMemberJoin: SRV-SWARM-INFRA-e6d6fc02c69e 192.168.233.65 2021/04/01 04:40:00 [INFO] [http] [server_addr: 0.0.0.0] [server_port: 9001] [secured: true] [api_version: 2.0.0] [message: Starting Agent API server]

GOOD AGENT NODE: 2021/04/01 04:09:59 [INFO] [main] [message: Agent running on Docker platform] 2021/04/01 04:09:59 [INFO] [main] [message: Agent running on a Swarm cluster node. Running in cluster mode] 2021/04/01 04:10:02 [INFO] serf: EventMemberJoin: SRV-SWARM-01-c37dadc14f9d 192.168.233.56 2021/04/01 04:10:12 [INFO] serf: EventMemberJoin: SRV-SWARM-03-d59a82336d39 192.168.233.54 2021/04/01 04:10:12 [INFO] serf: EventMemberJoin: SRV-SWARM-06-03c818fa41db 192.168.233.55 2021/04/01 04:10:12 [INFO] serf: EventMemberJoin: SRV-SWARM-02-eaee5f8ec185 192.168.233.53 2021/04/01 04:10:12 [INFO] serf: EventMemberJoin: SRV-SWARM-04-2fd6e8bfe284 192.168.233.37 2021/04/01 04:10:13 [INFO] [http] [server_addr: 0.0.0.0] [server_port: 9001] [secured: true] [api_version: 2.0.0] [message: Starting Agent API server] 2021/04/01 04:10:14 [INFO] serf: EventMemberJoin: SRV-SWARM-05-a8a4571d55fe 192.168.233.57

Steps to reproduce the issue:

Upgrade your kernel to 5.9+

Technical details:

  • Portainer version: 1.23.2 / agent latest
  • Docker version (managed by Portainer):
  • Client: Docker Engine - Community Version: 19.03.15 API version: 1.40 Go version: go1.13.15 Git commit: 99e3ed8919 Built: Sat Jan 30 03:17:11 2021 OS/Arch: linux/amd64 Experimental: false

Server: Docker Engine - Community Engine: Version: 19.03.15 API version: 1.40 (minimum version 1.12) Go version: go1.13.15 Git commit: 99e3ed8919 Built: Sat Jan 30 03:15:40 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.3 GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc: Version: 1.0.0-rc92 GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff docker-init: Version: 0.18.0 GitCommit: fec3683

  • Kubernetes version (managed by Portainer):
  • Platform (windows/linux): Linux
  • Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):
  • Browser: ALL
  • Use Case (delete as appropriate): Using Portainer at Home, Using Portainer in a Commerical setup.
  • Have you reviewed our technical documentation and knowledge base? Yes/No

Additional context Add any other context about the problem here. When a rollback to 4.9 kernel, the portainer agent works well.

Working: image image image

Not working: image image image

rudnypc avatar Apr 01 '21 05:04 rudnypc

I tried ubuntu with kernel 5.11, 5.14... the same problem happens. I have to downgrade to 5.4. agent doesn't communicate with each other, I don't see the EventMemberJoin message from all agents.

Portainer-ce is only able to have agent information on the same node.

You can download the ubuntu 20.04, and install the newest kernel with this tool: https://github.com/pimlie/ubuntu-mainline-kernel.sh

sh ubuntu-mainline-kernel.sh -i v5.14.0

rudnypc avatar Sep 02 '21 03:09 rudnypc

Could there be an issue with your overlay network?

huib-portainer avatar Sep 02 '21 20:09 huib-portainer