Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
buildbot V2.4 Linux 32-bit
buildbot V2.4 Linux 64-bit
buildbot-special V2.4 Linux 64-bit Subscription RHEL 5.7
-
ALL
Description
V2.4 Linux 32-bit Build #141 Aug 2
http://buildbot.mongodb.org/builders/V2.4%20Linux%2032-bit/builds/141/steps/test_6/logs/stdio
http://buildlogs.mongodb.org/V2.4%20Linux%2032-bit/builds/141/test/replica%20sets/chaining.js
ReplSetTest awaitReplication: checking secondaries against timestamp Timestamp(1374413621, 1)
|
ReplSetTest awaitReplication: checking secondary #1: bs-linux32.10gen.cc:31001
|
ReplSetTest awaitReplication: secondary #1, bs-linux32.10gen.cc:31001, is synced
|
ReplSetTest awaitReplication: checking secondary #2: bs-linux32.10gen.cc:31002
|
ReplSetTest awaitReplication: timestamp for secondary #2, bs-linux32.10gen.cc:31002, is Timestamp(1374413616, 1) but latest is Timestamp(1374413621, 1)
|
ReplSetTest awaitReplication: last oplog entry (of 2) for secondary #2, bs-linux32.10gen.cc:31002, is { "ts" : Timestamp(1374413616, 1), "h" : NumberLong("8118325673702981649"), "v" : 2, "op" : "i", "ns" : "chaining.foo", "o" : { "_id" : ObjectId("51ebe32fa63b195fb036f671"), "a" : 1 } }
|
ReplSetTest awaitReplication: secondary #2, bs-linux32.10gen.cc:31002, is NOT synced
|
m31002| Sun Jul 21 09:34:11.586 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31010: couldn't connect to server bs-linux32.10gen.cc:31010
|
m31002| Sun Jul 21 09:34:11.586 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31010: couldn't connect to server bs-linux32.10gen.cc:31010
|
m31002| Sun Jul 21 09:34:11.586 [rsHealthPoll] replset info bs-linux32.10gen.cc:31010 heartbeat failed, retrying
|
m31002| Sun Jul 21 09:34:11.587 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31010: couldn't connect to server bs-linux32.10gen.cc:31010
|
m31002| Sun Jul 21 09:34:11.587 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31010: couldn't connect to server bs-linux32.10gen.cc:31010
|
m31002| Sun Jul 21 09:34:11.587 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31010: couldn't connect to server bs-linux32.10gen.cc:31010
|
m31002| Sun Jul 21 09:34:11.625 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31009: couldn't connect to server bs-linux32.10gen.cc:31009
|
m31002| Sun Jul 21 09:34:11.626 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31009: couldn't connect to server bs-linux32.10gen.cc:31009
|
m31002| Sun Jul 21 09:34:11.629 [rsHealthPoll] replset info bs-linux32.10gen.cc:31009 heartbeat failed, retrying
|
m31002| Sun Jul 21 09:34:11.629 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31009: couldn't connect to server bs-linux32.10gen.cc:31009
|
m31002| Sun Jul 21 09:34:11.630 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31009: couldn't connect to server bs-linux32.10gen.cc:31009
|
m31002| Sun Jul 21 09:34:11.630 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31009: couldn't connect to server bs-linux32.10gen.cc:31009
|
m31000| Sun Jul 21 09:34:11.709 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31005: couldn't connect to server bs-linux32.10gen.cc:31005
|
m31000| Sun Jul 21 09:34:11.710 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31005: couldn't connect to server bs-linux32.10gen.cc:31005
|
2013-07-21 09:34:13 EDT
|
m31000| Sun Jul 21 09:34:11.710 [rsHealthPoll] replset info bs-linux32.10gen.cc:31005 heartbeat failed, retrying
|
m31000| Sun Jul 21 09:34:11.714 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31005: couldn't connect to server bs-linux32.10gen.cc:31005
|
m31000| Sun Jul 21 09:34:11.714 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31005: couldn't connect to server bs-linux32.10gen.cc:31005
|
m31000| Sun Jul 21 09:34:11.714 [rsHealthPoll] couldn't connect to bs-linux32.10gen.cc:31005: couldn't connect to server bs-linux32.10gen.cc:31005
|
Sun Jul 21 09:34:13.370 JavaScript execution failed: [awaiting replication] timed out after 30000ms ( 16 tries ) at src/mongo/shell/utils.js:L490
|
failed to load: /mnt/slaves/Linux_32bit_V2.4/mongo/jstests/replsets/chaining.js
|
This has been happening intermittently for a while:
Build #138 July 17
http://buildlogs.mongodb.org/V2.4%20Linux%2032-bit/builds/138/test/replica%20sets/chaining.js
Build #34 July 11
http://buildlogs.mongodb.org/V2.4%20Linux%2032-bit/builds/134/test/replica%20sets/chaining.js
Build #132 July 9
http://buildlogs.mongodb.org/V2.4%20Linux%2032-bit/builds/132/test/replica%20sets/chaining.js
Build #130 failed on chaining.js with a different error
Build #120
http://buildlogs.mongodb.org/V2.4%20Linux%2032-bit/builds/120/test/replica%20sets/chaining.js
Build #117 June 23
http://buildlogs.mongodb.org/V2.4%20Linux%2032-bit/builds/117/test/replica%20sets/chaining.js
Attachments
Issue Links
- is duplicated by
-
SERVER-10437 chaining.js failed on Linux 64-bit subscription, "error doing query"
-
- Closed
-