unable to restart sim

Issue #155 resolved
dan created an issue

With the latest update, when I shut down the simulation with Ctrl-C, I am unable to restart it unless I reboot my machine. In the past this happened sometimes and it just required killing gzserver which tended to persist. However, that is not the case here.

This is the error message when trying to restart:

Traceback (most recent call last):

  File "/home/dbarry/ariac_ws/src/ariac/osrf_gear/script/gazebo_unpauser.py", line 30, in <module>
    rospy.wait_for_service('/gazebo/unpause_physics')

  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 160, in wait_for_service

    rospy.core.logwarn_throttle(10, "wait_for_service(%s): failed to contact, will keep trying"%resolved_name)

  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/core.py", line 243, in logwarn_throttle
    _base_logger(msg, logger_throttle=period, logger_level='warn')

  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/core.py", line 184, in _base_logger

    if _logging_throttle(caller_id, throttle):
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/core.py", line 222, in __call__
    now = rospy.Time.now()

  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/rostime.py", line 155, in now
    return get_rostime()

  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/rostime.py", line 190, in get_rostime

    raise rospy.exceptions.ROSInitException("time is not initialized. Have you called init_node()?")

rospy.exceptions.ROSInitException: time is not initialized. Have you called init_node()?

Comments (3)

  1. Shane Loretz

    I haven't seen this personally. I do see gzserver persist, but everything shuts down fine after killing it.

    This error message looks like a consequence of gazebo not starting on the second run. Would you mind passing --verbose to gear.py and posting the output as a log file?

  2. Log in to comment