Open osrf-migration opened 11 years ago
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I've seen this once, when running a regression test on a feature branch off of default. The test still passed though.
[==========] Running 6 tests from 2 test cases.
[----------] Global test environment set-up.
[----------] 3 tests from TestODE/PhysicsMsgsTest
[ RUN ] TestODE/PhysicsMsgsTest.SetGravity/0
Msg Waiting for master
Msg Connected to gazebo master @ http://127.0.0.1:11345
Msg Publicized address: 192.168.1.183
Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
Error [Connection.hh:264] Header is empty
Error [Master.cc:124] Master got empty data message from[38085]
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp
[ OK ] TestODE/PhysicsMsgsTest.SetGravity/0 (1260 ms)
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I saw two instances of this test failure during heightmap tests in my overnight testing that seem similar. They were both preceded by the following:
C++ exception with description "OGRE EXCEPTION(7:InternalErrorException):
Cannot create GL vertex buffer in GLHardwareVertexBuffer::GLHardwareVertexBuffer
at /build/buildd/ogre-1.7.4/RenderSystems/GL/src/OgreGLHardwareVertexBuffer.cpp
(line 46)" thrown in the test body.
First failure:
65: Test command: /tmp/gazebo_build/source/build/gazebo/rendering/UNIT_Heightmap_TEST "--gtest_output=xml:/tmp/gazebo_build/source/build/test_results/UNIT_Heightmap_TEST.xml"
65: Test timeout computed to be: 240
65: [==========] Running 1 test from 1 test case.
65: [----------] Global test environment set-up.
65: [----------] 1 test from Heightmap_TEST
65: [ RUN ] Heightmap_TEST.splitTerrain
65:
65: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
65: Msg Publicized address: 192.168.1.187
65: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
65: unknown file: Failure
65: C++ exception with description "OGRE EXCEPTION(7:InternalErrorException): Cannot create GL vertex buffer in GLHardwareVertexBuffer::GLHardwareVertexBuffer at /build/buildd/ogre-1.7.4/RenderSystems/GL/src/OgreGLHardwareVertexBuffer.cpp (line 46)" thrown in the test body.
65: Error [Connection.hh:264] Header is empty
65: Error [Master.cc:124] Master got empty data message from[43463]
...
65: Master Unknown message type[] From[43463]
...
65: libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp, type, serialized_data
...
Second failure:
65: Test command: /tmp/gazebo_build/source/build/gazebo/rendering/UNIT_Heightmap_TEST "--gtest_output=xml:/tmp/gazebo_build/source/build/test_results/UNIT_Heightmap_TEST.xml"
65: Test timeout computed to be: 240
65: [==========] Running 1 test from 1 test case.
65: [----------] Global test environment set-up.
65: [----------] 1 test from Heightmap_TEST
65: [ RUN ] Heightmap_TEST.splitTerrain
65:
65: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
65: Msg Publicized address: 192.168.1.187
65: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
65: unknown file: Failure
65: C++ exception with description "OGRE EXCEPTION(7:InternalErrorException): Cannot create GL vertex buffer in GLHardwareVertexBuffer::GLHardwareVertexBuffer at /build/buildd/ogre-1.7.4/RenderSystems/GL/src/OgreGLHardwareVertexBuffer.cpp (line 46)" thrown in the test body.
65: Error [Connection.hh:264] Header is empty
65: Error [Master.cc:124] Master got empty data message from[44248]
...
65: Master Unknown message type[] From[44248]
65: libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp, type, serialized_data
...
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Speaking of pull request #768, I've been testing it in my overnight scripts, and I found an instance where these error messages occur towards the end of a multi-test sequence:
141: [==========] Running 15 tests from 1 test case.
141: [----------] Global test environment set-up.
141: [----------] 15 tests from PhysicsEngines/LaserTest
...
141: [ RUN ] PhysicsEngines/LaserTest.LaserNoise/2
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: Error [Connection.hh:264] Header is empty
141: Exception [msgs.cc:111] Can't serialize message of type[gazebo.msgs.Publish] because it is missing required fields
141:
141: terminate called after throwing an instance of 'gazebo::common::Exception'
Full console output
141: [==========] Running 15 tests from 1 test case.
141: [----------] Global test environment set-up.
141: [----------] 15 tests from PhysicsEngines/LaserTest
141: [ RUN ] PhysicsEngines/LaserTest.EmptyWorld/0
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.1 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.EmptyWorld/0 (3182 ms)
141: [ RUN ] PhysicsEngines/LaserTest.EmptyWorld/1
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.EmptyWorld/1 (2690 ms)
141: [ RUN ] PhysicsEngines/LaserTest.EmptyWorld/2
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.EmptyWorld/2 (2682 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserBox/0
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.LaserBox/0 (2359 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserBox/1
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.1 seconds, timeout after 60 seconds
141: Warning [laser.cc:185] Raising sensor for bullet as workaround for #934
141: [ OK ] PhysicsEngines/LaserTest.LaserBox/1 (2142 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserBox/2
141: Error [laser.cc:160] Abort test since simbody does not support ray sensor, Please see issue #867.
141: [ OK ] PhysicsEngines/LaserTest.LaserBox/2 (1 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserVertical/0
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.LaserVertical/0 (2962 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserVertical/1
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.LaserVertical/1 (1673 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserVertical/2
141: Error [laser.cc:261] Abort test since simbody does not support ray sensor, Please see issue #867.
141: [ OK ] PhysicsEngines/LaserTest.LaserVertical/2 (0 ms)
141: [ RUN ] PhysicsEngines/LaserTest.GroundPlane/0
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.GroundPlane/0 (3570 ms)
141: [ RUN ] PhysicsEngines/LaserTest.GroundPlane/1
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.GroundPlane/1 (1466 ms)
141: [ RUN ] PhysicsEngines/LaserTest.GroundPlane/2
141: [ OK ] PhysicsEngines/LaserTest.GroundPlane/2 (0 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserNoise/0
141: Error [laser.cc:357] Abort test since simbody does not support ray sensor, Please see issue #867.
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.LaserNoise/0 (1643 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserNoise/1
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: [ OK ] PhysicsEngines/LaserTest.LaserNoise/1 (1441 ms)
141: [ RUN ] PhysicsEngines/LaserTest.LaserNoise/2
141:
141: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
141: Msg Publicized address: 192.168.1.187
141: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
141: Error [Connection.hh:264] Header is empty
141: Exception [msgs.cc:111] Can't serialize message of type[gazebo.msgs.Publish] because it is missing required fields
141:
141: terminate called after throwing an instance of 'gazebo::common::Exception'
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Just got a backtrace from a test failure showing the following console message (see everything here):
Error [Connection.hh:264] Header is empty
Exception [msgs.cc:111] Can't serialize message of type[gazebo.msgs.Publish]
because it is missing required fields
Failing thread: gazebo::Master
Thread 1 (Thread 0x2b25bfbc1700 (LWP 19084)):
#0 0x00002b255091f425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00002b2550922b8b in __GI_abort () at abort.c:91
#2 0x00002b2550133e2d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x00002b2550131f26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4 0x00002b2550131f53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5 0x00002b255013217e in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x00002b254e660879 in gazebo::msgs::Package (type=..., message=...) at /tmp/gazebo_build/source/gazebo/msgs/msgs.cc:110
#7 0x00000000004a8475 in gazebo::Master::ProcessMessage (this=this@entry=0x2b257095f610, _connectionIndex=0, _data=...)
at /tmp/gazebo_build/source/gazebo/Master.cc:175
#8 0x00000000004a9327 in gazebo::Master::RunOnce (this=this@entry=0x2b257095f610) at /tmp/gazebo_build/source/gazebo/Master.cc:321
#9 0x00000000004a94f0 in gazebo::Master::Run (this=0x2b257095f610) at /tmp/gazebo_build/source/gazebo/Master.cc:299
---Type <return> to continue, or q <return> to quit---
#10 0x00002b254f8336c9 in ?? () from /usr/lib/libboost_thread.so.1.49.0
#11 0x00002b254eb98e9a in start_thread (arg=0x2b25bfbc1700) at pthread_create.c:308
#12 0x00002b25509dd3fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()
Testing thread is waiting for the world to load at ServerFixture.cc:171:
Thread 9 (Thread 0x2b25684df180 (LWP 19001)):
#0 clock_nanosleep (clock_id=<optimized out>, flags=<optimized out>, req=<optimized out>, rem=<optimized out>)
at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:51
#1 0x00002b254d623026 in gazebo::common::Time::Sleep (_time=...) at /tmp/gazebo_build/source/gazebo/common/Time.cc:195
#2 0x00002b254d623453 in gazebo::common::Time::MSleep (_ms=<optimized out>) at /tmp/gazebo_build/source/gazebo/common/Time.cc:214
#3 0x00000000004847a9 in ServerFixture::Load (this=this@entry=0x1790990, _worldFilename=..., _paused=_paused@entry=true, _physics=...)
at /tmp/gazebo_build/source/test/ServerFixture.cc:171
#4 0x0000000000458842 in ImuTest::Stationary_EmptyWorld_Noise (this=this@entry=0x1790990, _physicsEngine=...)
at /tmp/gazebo_build/source/test/integration/imu.cc:142
#5 0x00000000004598fc in ImuTest_EmptyWorldNoise_Test::TestBody (this=0x1790990) at /tmp/gazebo_build/source/test/integration/imu.cc:215
#6 0x00000000004803ca in HandleSehExceptionsInMethodIfSupported<testing::Test, void> (method=<optimized out>, object=<optimized out>,
location=<optimized out>) at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:2079
#7 testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void> (object=object@entry=0x1790990,
method=&virtual testing::Test::TestBody(), location=location@entry=0x4b1d01 "the test body")
at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:2115
#8 0x00000000004722b9 in testing::Test::Run (this=this@entry=0x1790990) at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:2152
#9 0x0000000000472397 in testing::TestInfo::Run (this=0x17895e0) at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:2327
#10 0x00000000004724d5 in testing::TestCase::Run (this=0x1788f30) at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:2445
#11 0x0000000000472845 in RunAllTests (this=0x1786bd0) at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:4316
#12 testing::internal::UnitTestImpl::RunAllTests (this=0x1786bd0) at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:4223
#13 0x000000000047ff4a in HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> (method=<optimized out>,
object=<optimized out>, location=<optimized out>) at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:2079
#14 testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> (object=0x1786bd0, method=
(bool (testing::internal::UnitTestImpl::*)(testing::internal::UnitTestImpl * const)) 0x472550 <testing::internal::UnitTestImpl::RunAllTests()>,
location=location@entry=0x4b2c78 "auxiliary test code (environments or event listeners)") at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:2115
#15 0x00000000004719dd in testing::UnitTest::Run (this=0x6df520 <testing::UnitTest::GetInstance()::instance>)
at /tmp/gazebo_build/source/test/gtest/src/gtest.cc:3930
#16 0x00000000004541c0 in RUN_ALL_TESTS () at /tmp/gazebo_build/source/test/gtest/include/gtest/gtest.h:2288
#17 main (argc=1, argv=0x7fff25a57da8) at /tmp/gazebo_build/source/test/integration/imu.cc:311
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Got another backtrace last night, which also failed during gazebo::Master::ProcessMessage
(full console output and backtrace here):
Console output:
187: [ RUN ] PhysicsEngines/SpeedPR2Test.PR2World/1
187:
187: Msg Waiting for masterMsg Connected to gazebo master @ http://127.0.0.1:11345
187: Msg Publicized address: 192.168.1.188
187: Dbg ServerFixture load in 0.09 seconds, timeout after 60 seconds
187: Error [Connection.hh:264] Header is empty
187: Error [Connection.hh:264] Header is empty
187: Error [Connection.hh:264] Header is empty
187: Error [Connection.hh:264] Header is empty
187: Exception [msgs.cc:111] Can't serialize message of type[gazebo.msgs.Publish] because it is missing required fields
187:
187: terminate called after throwing an instance of 'gazebo::common::Exception'
Backtrace from failing thread:
(gdb) bt
#0 0x00002af67376c425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00002af67376fb8b in __GI_abort () at abort.c:91
#2 0x00002af672f80e2d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x00002af672f7ef26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4 0x00002af672f7ef53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5 0x00002af672f7f17e in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x00002af6714ad879 in gazebo::msgs::Package (type=..., message=...) at /tmp/gazebo_build/source/gazebo/msgs/msgs.cc:110
#7 0x00000000004a1d75 in gazebo::Master::ProcessMessage (this=this@entry=0x2af74691e5c0, _connectionIndex=0, _data=...) at /tmp/gazebo_build/source/gazebo/Master.cc:175
#8 0x00000000004a2c27 in gazebo::Master::RunOnce (this=this@entry=0x2af74691e5c0) at /tmp/gazebo_build/source/gazebo/Master.cc:321
#9 0x00000000004a2df0 in gazebo::Master::Run (this=0x2af74691e5c0) at /tmp/gazebo_build/source/gazebo/Master.cc:299
#10 0x00002af6726806c9 in ?? () from /usr/lib/libboost_thread.so.1.49.0
#11 0x00002af6719e5e9a in start_thread (arg=0x2af694200700) at pthread_create.c:308
#12 0x00002af67382a3fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()
(gdb)
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I've added some console output to my overnight testing that indicates when message parsing fails:
diff -r 03d9a2c25cff12615f89a785ecf185e369dced88 gazebo/Master.cc
--- a/gazebo/Master.cc Tue Dec 17 19:02:34 2013 +0000
+++ b/gazebo/Master.cc Fri Dec 20 13:47:13 2013 -0800
@@ -166,7 +166,13 @@
{
boost::recursive_mutex::scoped_lock lock(this->connectionMutex);
msgs::Publish pub;
- pub.ParseFromString(packet.serialized_data());
+ if (!pub.ParseFromString(packet.serialized_data()))
+ {
+ gzerr << "ParseFromString failed:"
+ << " packet.type() " << packet.type()
+ << " packet.serialized_data() " << packet.serialized_data()
+ << std::endl;
+ }
Connection_M::iterator iter2;
for (iter2 = this->connections.begin();
Over the past few nights, I've noticed that there are many types of messages that can fail this way, which makes me think it's not related to a specific topic or message:
Failing topics:
/gazebo/default/factory
/gazebo/default/log/control
/gazebo/default/pr2/head_tilt_link
/gazebo/default/simple_gripper/joint_cmd
/gazebo/default/world_control
The list of failing message types is slightly attenuated because many of the messages are truncated:
gazebo.msgs.Factory
gazebo.msgs.Joi
gazebo.msgs.LogControl
gazebo.msgs.WorldControl
So I think these messages are getting truncated somewhere.
Original comment by Elte Hupkes (Bitbucket: ElteHupkes).
I have probably found the cause of this, reported issue #1720 since this one's so old...
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Issue #1720 was marked as a duplicate of this issue.
Original comment by Elte Hupkes (Bitbucket: ElteHupkes).
This patch should fix the race condition:
headerBuffer
inside the mutex lockthis->headerBuffer
rather than headerBuffer
so it is move obvious the buffer is a class variable.Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I've often seen these bugs, but it's always been hard to reproduce them. I have just found a way to reproduce a particular instance of this bug that is much better than I have seen before. It doesn't happen everytime, but as I said, it's the best I've seen so far.
The failures seem to occur when making repeated requests from separate processes (I noticed this while debugging some failures of UNIT_gz_TEST
). Prepare three separate terminal windows:
gzserver --verbose test/worlds/simple_arm.world
gz model -i -m simple_arm
gz model -i -m simple_arm
Each gz
instance creates an entity_info
request and waits for the response. Repeating those calls in a loop eventually leads to some familiar console errors from gzserver
or hanging of the gz
processes:
while gz model -i -m simple_arm | wc -l; do date; done
[Err] [Connection.hh:267] Header is empty
[Err] [Connection.hh:267] Header is empty
[Err] [Connection.hh:267] Header is empty
[Err] [Connection.hh:267] Header is empty
[Err] [Connection.hh:267] Header is empty
[Err] [Connection.hh:267] Header is empty
[Err] [Connection.hh:308] OnReadData got empty data!!!
Can someone else try this?
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Also, I tried applying the patch from @ElteHupkes but it doesn't fix this problem.
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I caught some of these errors in valgrind, which gave some extra info, but as it seems to be memory corruption, each error looks different:
https://gist.github.com/scpeters/f0517321f71f11dda0db4dec9e0eb4f6
Original comment by Dave Coleman (Bitbucket: Dave Coleman).
I can confirm I occasionally get these errors as well in my Gazebo7 setup:
[libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of type "gazebo.msgs.Packet" because it is missing required fields: stamp, type, serialized_data
Master Unknown message type[] From[60838]
Original report (archived issue) by Brian Gerkey (Bitbucket: Brian Gerkey, GitHub: gerkey).
The original report had attachments: connection-patch.diff
Using gazebo-1.9.1-2 from deb, I occasionally get console output like the following on startup (e.g., when running
roslaunch drcsim_gazebo atlas.launch
). It seems like everything still works (e.g., I can manipulate the world using the client and see an appropriate result).