This means that when you next try to start the launch file, you will get something like
[ERROR] [1602235526.494954]: MongoDB process stopped!
[ERROR] [1602235526.495783]: Mongo process error! Exit code=100
[WARN] [1602235526.497455]: It looks like Mongo already died. Watch out as the DB might need recovery time at next run.
Traceback (most recent call last):
File "/opt/ros/melodic/lib/mongodb_store/message_store_node.py", line 316, in <module>
store = MessageStore()
File "/opt/ros/melodic/lib/mongodb_store/message_store_node.py", line 51, in __init__
have_dc = dc_util.wait_for_mongo(local_timeout)
File "/opt/ros/melodic/lib/python2.7/dist-packages/mongodb_store/util.py", line 67, in wait_for_mongo
wait()
File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 442, in __call__
return self.call(*args, **kwds)
File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 532, in call
raise ServiceException("transport error completing service call: %s"%(str(e)))
rospy.service.ServiceException: transport error completing service call: unable to receive data from sender, check sender's logs for details
[mongo_server-1] process has finished cleanly
log file: /home/ori/.ros/log/d72692aa-0a0f-11eb-a2d9-1c697a005041/mongo_server-1*.log
[message_store-3] process has died [pid 7629, exit code 1, cmd /opt/ros/melodic/lib/mongodb_store/message_store_node.py __name:=message_store __log:=/home/ori/.ros/log/d72692aa-0a0f-11eb-a2d9-1c697a005041/message_store-3.log].
log file: /home/ori/.ros/log/d72692aa-0a0f-11eb-a2d9-1c697a005041/message_store-3*.log
When using a basic setup, sending C-c to the terminal window will kill mongo properly
If using bind_to_host, this is not the case.
This means that when you next try to start the launch file, you will get something like