• Bugs

  • High CPU in docker image after hibernate

Hello - I am trying out the new Docker image on my laptop. It is very easy to get running and it works great. But I would like to keep it running. When I close the laptop and resume the docker image the CPU is at 100% and no statistics are shown.

any idea ?

    Hi,

    We can confirm this behavior. After hibernation the Docker image runs properly but the CPU usage is pegged at 100% and new data isnt updated.

    I will investigate this and post an update here. Thanks Vlad for reporting this.

    • Vivek
      a month later

      Hi ,

      Thanks for reporting. Finally reproduced this int eh following manner.

      1. docker stop xx
      2. docker start x
      3. now the CPU is pegged.

      There seems to be a problem with resuming in this manner. No estimated time for a fix. Can you do the following until we figure out what the matter is

      Do not do stop/start docker instead remove the image and restart every time.

      docker stop trisul1a-or-your-name
      docker rm ..

      then
      docker run trisul1a-or-your-name

      Thanks for reporting this issue. Feel free to send any suggestions about the TrisulNSM docker image.

      Vivek

        7 days later

        Quick update.

        Switching capture mode to AF_PACKET seems to fix this. Can you try?

        1. Login as admin
        2. Context: default > Admin Tasks > Start / Stop Tasks
        3. Probe0 - select afpacket

        this setting will persist across docker run sessions.

          Write a Reply...