[SERVER-6539] Mongos crashed because of mongod cannot reach. Created: 20/Jul/12  Updated: 21/Sep/12  Resolved: 30/Jul/12

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 2.2.0-rc0
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: NOVALUE yangfenqiang Assignee: Randolph Tan
Resolution: Duplicate Votes: 0
Labels: crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 12.04 LTS
Linux yz-uc-core-a08 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux


Attachments: Text File mongos1.log    
Issue Links:
Duplicate
duplicates SERVER-7061 mongos can use invalid ptr to master ... Closed
Related
is related to SERVER-6538 Invalid access at address: 0x7f2e3402... Closed
Operating System: ALL
Participants:

 Description   

Mongos crashed! Because of 192.168.130.12:15002 connot reached.
192.168.130.12:15002 mongod crashed because of "SERVER-6538"

Fri Jul 20 17:32:47 [ReplicaSetMonitorWatcher] reconnect 192.168.130.18:15002 failed couldn't connect to server 192.168.130.18:15002
Fri Jul 20 17:32:47 [WriteBackListener-192.168.130.12:15002] DBClientCursor::init call() failed
Fri Jul 20 17:32:47 [WriteBackListener-192.168.130.12:15002] WriteBackListener exception : DBClientBase::findN: transport error: 192.168.130.12:15002 ns: admin.$cmd query: { writebacklisten: ObjectId('5008fe6b0e2a603cc3f9b46d'), $auth: { local:

{ __system: 2 }

} }
Fri Jul 20 17:32:48 [conn28] got not master for: 192.168.130.12:15002
Received signal 11
Backtrace: 0x69f2a5 0x7f5ef462f4c0 0x7f5ed005d928
/home/mongo/.bin/mongos(_ZN5mongo17printStackAndExitEi+0x75)[0x69f2a5]
/lib/x86_64-linux-gnu/libc.so.6(+0x364c0)[0x7f5ef462f4c0]
[0x7f5ed005d928]
===


Generated at Thu Feb 08 03:12:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.