[ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_alloc

22 views
Skip to first unread message

retf

unread,
May 20, 2013, 4:23:17 PM5/20/13
to mongod...@googlegroups.com
Anyone knows what this mean?

Mon May 20 20:19:19 [ReplicaSetMonitorWatcher] starting
Mon May 20 20:19:29 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_alloc
Mon May 20 20:19:39 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_alloc
Mon May 20 20:19:49 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_alloc

When I use ScopedDbConnection, My app give this constantly, like a loop!

full log:

Mon May 20 20:19:19 warning: 2 commands with name: connPoolSync Mon May 20 20:19:19 warning: 2 commands with name: connPoolStats Mon May 20 20:19:19 starting new replica set monitor for replica set gridfs.rs1 with seed of 10.0.2.66:27017,10.0.2.67:27017 Mon May 20 20:19:19 successfully connected to seed 10.0.2.66:27017 for replica s et gridfs.rs1 Mon May 20 20:19:19 changing hosts to { 0: "10.0.2.66:27017", 1: "10.0.4.66:2701 7" } from gridfs.rs1/ Mon May 20 20:19:19 trying to add new host 10.0.2.66:27017 to replica set gridfs .rs1 Mon May 20 20:19:19 successfully connected to new host 10.0.2.66:27017 in replic a set gridfs.rs1 Mon May 20 20:19:19 trying to add new host 10.0.4.66:27017 to replica set gridfs .rs1 Mon May 20 20:19:19 successfully connected to new host 10.0.4.66:27017 in replic a set gridfs.rs1 Mon May 20 20:19:19 successfully connected to seed 10.0.2.67:27017 for replica s et gridfs.rs1 Mon May 20 20:19:19 replica set monitor for replica set gridfs.rs1 started, addr ess is gridfs.rs1/10.0.2.66:27017,10.0.4.66:27017 Mon May 20 20:19:19 [ReplicaSetMonitorWatcher] starting Mon May 20 20:19:29 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:19:39 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:19:49 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:19:59 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:20:09 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:20:19 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:20:29 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:20:39 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:20:49 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:20:59 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:21:09 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:21:19 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:21:29 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:21:39 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:21:49 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:21:59 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:22:09 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:22:19 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:22:29 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:22:39 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc Mon May 20 20:22:49 [ReplicaSetMonitorWatcher] ERROR: check failed: std::bad_all oc


Thanks

Benjamin Petrin

unread,
May 21, 2013, 2:11:44 PM5/21/13
to mongod...@googlegroups.com
Out of memory perhaps. Have you checked how much memory is available? Also, provide the output of ulimit -a
Reply all
Reply to author
Forward
0 new messages