Sentinel shutdowns when using dockers
-
@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.
-
@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.
@stevedan We have not encountered anything like that. What is the node doing? Is it accessing any IO directly?
-
@stevedan We have not encountered anything like that. What is the node doing? Is it accessing any IO directly?
@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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login