Bizarre log and restarting behaviour #32
Comments
|
this looks like it could be a hardware problem. To verify that the hardware works, 1) stop the duckiebot-interface 2) ssh into the robot 3) run |
|
Thanks for your response. Like you suggested, the camera is not functional. Here's the output from the command you suggested I try Should I disassemble my duckie and verify that everything is well connected together like the message says? Also, do you believe the camera not being detected is the source of the ROS master not being up then? |
|
I have disassembled and reassembled the duckiebot. I found no problem in how the camera was connected. Reassembled the duckie with the propperly connected camera and repeated the procedure above, but sudo raspistill -o out.jpg still does not work. There is however a small red LED light on on the camera panel, so the connection is correct to some extent. |
|
make sure that you are not already reading from the camera with one of the docker containers that is running. If something else is already reading from the camera you will also get this output. Safest is to stop all the running containers and then do the ssh/raspistill thing. |
|
Ok I did and indeed raspistill works, gives a good photograph with no issues. But does that mean that some of the containers are trying to simultaneously use the camera? Anytime that the container "duckiebot-interface" is up (no other container influences the camera), the camera will be inaccessible through raspistill since it's "in use" by duckiebot-interface. However the container will fail then restart, and examining its logs shows the cyclic error message I posted earlier. Additionally near the end of the logs the cyclical message will change for a set amount of times: One of the two red error messages -this one- disappears. The rest of the cyclical log message remains the same: |
|
Hi, just wondering if you found a solution to your problem in the end? I am having a similar issue :) |
So as noted in another issue, my LEDs flicker ocassionally. On top of that I cannot initiate remote control of the duckie due to the script being unable to connect to the ROS Master at 11311, an error that is repeated in the docker logs of some of the containers running in my duckie (car-interface).
Upon checking the logs of duckiebot-interface, I've come to believe that it's it responsibility to start said ros Master node. On top of that, the container restarts periodically, albeit with error code 0 so presumedly without faulty behaviour. However the logs reveal at least 2 problems ocurring:
This seems to be the cause of the container restarting:
This is another red message that occurs repeatedly
[ERROR] [1589558887.278684679]: Couldn't open joystick /dev/input/js0. Will retry every second.Here is the full message that keeps on being repeated inside the docker log on every restart:
NOTE: Since the error is ended by a "Keyboard Interrupt" (that is not me on my keyboard), the traceback error will vary depending on where on the code the program was when said interrupt was activated. The rest of the message will be identical between failures
The text was updated successfully, but these errors were encountered: