camera-realsense2_camera-3-stdout.log grows to 51GB

[fiorano10]

For some reason realsense logs in ~/.ros/log folder can grow up to 51GB. Probably need to change ROS_WARN to ROS_WARN_THROTTLE?

du -sh * | sort -hr                                                                                                                                                           
51G     9559afba-f479-11eb-a5d9-024212010e20

They are full of

 03/08 12:43:26,194 WARNING [140272893687552] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,194 WARNING [140273388594944] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,194 WARNING [140272893687552] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140273380202240] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140272893687552] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140273388594944] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140272893687552] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140273380202240] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140272893687552] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140273380202240] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140272893687552] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10
 03/08 12:43:26,195 WARNING [140273380202240] (backend-v4l2.cpp:1775) Invalid md size: bytes used =  0 ,start offset=10

[MartyG-RealSense]

Hi @fiorano10 These are the messages that were being generated in your recent #2008 case.

This error is relatively rare except for the period around the time of librealsense 2.41.0 when there was a change in the librealsense SDK that was reverted in 2.42.0. So there may not currently be justification for changing the logging status of this error.

Were you able to test with 2.48.0 and wrapper 2.3.1 as suggested in #2008 to see whether the error still occurs, please?

[MartyG-RealSense]

Hi @fiorano10 Do you require further assistance with this case, please? Thanks!

[MartyG-RealSense]

Case closed due to no further comments received.