error: 'bad marshal data' when starting roscore
When I used roscore, I got these feedback:
am-26@zyz:~$ roscore
Traceback (most recent call last):
File "/opt/ros/kinetic/bin/roscore", line 69, in <module>
import roslaunch
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/__init__.py", line 61, in <module>
from .scriptapi import ROSLaunch
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/scriptapi.py", line 42, in <module>
import roslaunch.parent
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/parent.py", line 54, in <module>
import roslaunch.server
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/server.py", line 78, in <module>
from rosgraph_msgs.msg import Log
File "/opt/ros/kinetic/lib/python2.7/dist-packages/rosgraph_msgs/msg/__init__.py", line 3, in <module>
from ._TopicStatistics import *
ValueError: bad marshal data (unknown type code)
Anyone has a clue? Thanks in advance.
ps. I installed ubuntu 16.04 and ROS kinetic in a portable SSD, boot from the SSD through usb. The installation of ROS follows wiki's instruction and I completed wike's tutorials successfuly until the roscore step.
Please tell us how you installed ROS, which platform (ie: Linux version, CPU architecture) this is.
Thank you for replying. I just added those above.
what is the file system that this SSD is formatted with? Fat/ExFat/Fat32/NTFS or one of the Linux FS?
Reading around a bit it could just be that some files got corrupted. Never a good sign, but you could try and see whether reinstalling the affected packages/files fixes things.
I chose the SSD format during ubuntu installation. The "/" category and the "/home" category are ext4 and the rest is used for swap. Just these three categories, no "/boot" or anything else. the "/" category got about 30g and the swap got 10g. The rest(totally 240g) belong to "/home" .Thank you
I had the same issue, same ubuntu version and ROS-kinectic. apt-get update showed broken packages in ros-kinetic. After an apt-get remove ros-* followed by apt-get install ros-desktop-full, the problem went away. Hope this helps.