We are using this specific version of the core to maintain the kernel compatibility with the other softwares.
The problem being faced is that the device is restating itself. I guess it is due to memory issue as we are logging our application data as bin files in our ROS environment inside the docker container
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, it seems that the device is restarting due to memory constraints, likely caused by excessive logging within your ROS environment inside a Docker container. Here are the steps you can take to address this issue:
Access the Docker Container: Use the command docker exec -it <container_id> /bin/bash to enter the Docker container. Replace <container_id> with the actual ID of your running container. This will allow you to access the shell of the container and manage files.
Monitor Memory Usage: Use the command docker stats to monitor the memory usage of your Docker containers. This will help you identify if the memory usage is indeed the cause of the restarts.
Optimize Logging: Implement log rotation or limit the size of log files generated by your application to prevent memory overflow. This can help in managing the memory usage more effectively.
Alternative Access Methods: If you are unable to maintain a stable connection to execute commands, consider using a serial console or SSH to access the device directly. This might provide a more reliable connection for managing Docker containers and recovering logs.
Recovery Mode: If the device is unresponsive, you may need to reboot it in a safe mode or use recovery tools to access the container and manage the logs.
By following these steps, you should be able to mitigate the memory issue and stabilize your device. If the problem persists, further investigation into your logging practices and memory management strategies may be necessary.
Please, also check if these links can help you solve your problem:
