You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #60 was fixed I tried to update the stored binary and ran into a similar error:
Updating stored default for /ground_hog/model
/usr/local/lib/python2.7/dist-packages/pymongo/collection.py:487: RuntimeWarning: couldn't encode - reloading python modules and trying again. if you see this without getting an InvalidDocument exception please see http://api.mongodb.org/python/current/faq.html#does-pymongo-work-with-mod-wsgi
check_keys, self.__uuid_subtype), safe)
Traceback (most recent call last):
File "/home/cdondrup/ros-ws/src/ros_datacentre/ros_datacentre/scripts/config_manager.py", line 225, in <module>
server = ConfigManager()
File "/home/cdondrup/ros-ws/src/ros_datacentre/ros_datacentre/scripts/config_manager.py", line 117, in __init__
defaults_collection.update(existing,{"$set":{"value":val}})
File "/usr/local/lib/python2.7/dist-packages/pymongo/collection.py", line 487, in update
check_keys, self.__uuid_subtype), safe)
bson.errors.InvalidDocument: Cannot encode object: <xmlrpclib.Binary instance at 0x21ab8c0>
[INFO] [WallTime: 1405590963.002627] Thu Jul 17 10:56:02 [conn1] end connection 127.0.0.1:58556
[config_manager-3] process has died [pid 20484, exit code 1, cmd /home/cdondrup/ros-ws/src/ros_datacentre/ros_datacentre/scripts/config_manager.py __name:=config_manager __log:=/home/cdondrup/.ros/log/8dd13814-0d98-11e4-9e7a-902b34d5fb37/config_manager-3.log].
log file: /home/cdondrup/.ros/log/8dd13814-0d98-11e4-9e7a-902b34d5fb37/config_manager-3*.log
Deleting the parameter from the config DB manually and reinserting it worked fine but the direct update via the config manager does yield above error. Do you have an idea what might cause this @cburbridge ?
The text was updated successfully, but these errors were encountered:
cburbridge
added a commit
to cburbridge/mongodb_store
that referenced
this issue
Jul 17, 2014
After #60 was fixed I tried to update the stored binary and ran into a similar error:
Deleting the parameter from the config DB manually and reinserting it worked fine but the direct update via the config manager does yield above error. Do you have an idea what might cause this @cburbridge ?
The text was updated successfully, but these errors were encountered: