• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login
ModalAI Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
    • Register
    • Login

    Sentinel shutdowns when using dockers

    Sentinel
    2
    3
    289
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      stevedan
      last edited by 7 Jul 2023, 06:10

      @Eric-Katzfey, for more context, look at this link https://forum.modalai.com/topic/2197/sentinel-flips-during-takeoff/39?_=1688709638550. Basically, We are using the sentinel drone with the new beta image we received(more explanation of this on the previous link). So basically, we run multiple dockers on the sentinel. In this docker, we do reset of multiple nodes, after doing 2 or 3 resets, the whole sentinel shuts down. It blocks access to the drone and it seem the sentinel Ubuntu part shuts down because I loose access to it. This did not happen on the rb5, m500 nor in my pc. Do you know what could possible be the problem to this. I monitored the dockers stats and the cpu usage is 80% of one core and the memory usage is like 1.16%, which is not that high.

      E 1 Reply Last reply 7 Jul 2023, 23:01 Reply Quote 0
      • E
        Eric Katzfey ModalAI Team @stevedan
        last edited by 7 Jul 2023, 23:01

        @stevedan We have not encountered anything like that. What is the node doing? Is it accessing any IO directly?

        S 1 Reply Last reply 10 Jul 2023, 06:51 Reply Quote 0
        • S
          stevedan @Eric Katzfey
          last edited by stevedan 10 Jul 2023, 07:48 10 Jul 2023, 06:51

          @Eric-Katzfey we are connected to the gpio pin but don't activate it during this reset. We also have a privileged access from the docker so we can change the gpio pin state to on and off from software. We use the pin 1153. The node on this docker runs our autonomy stack but does not interact with the hardware besides the gpio. i also tried removing the privileged access to the docker but still got the problem. We have 2 more dockers that gives us the ros2 mavros messages. Those one never gets resets and works fine.

          1 Reply Last reply Reply Quote 0
          1 out of 3
          • First post
            1/3
            Last post
          Powered by NodeBB | Contributors