Log file Viewer

[19:19:37] <abonilla> moin - I've suddenly became unable to perform a basic query... :|

[19:20:52] <abonilla> my documents have a _id and then what I guess is an array of key values, but I cannot manage to perform this query correctly. db.meter.find({},{resource_metadata:[{"name":"mongoDB"},{"size":{$gt:3189}}]}, {name:1}).pretty()

[19:21:52] <abonilla> within the resource_metadata is the array of documents, and I want to get only those that have the mongo name and a size larger than the value. But I get all that have a name...!

[19:34:46] <rmt_> is it possible to pass a bind_ip arg when launching mongod? like: mongod --bind_ip x.x.x.x?

[19:35:36] <abonilla> rmt_: yes

[19:35:43] <abonilla> just like in the config file

[19:36:06] <rmt_> hmm, I'm having an issue with mongo binding to localhost

[19:36:42] <abonilla> rmt_: bind_ip = 127.0.0.1

[19:36:43] <rmt_> despite setting up the config file or passing the bind_ip arg it still appears to bind to localhost

[19:37:03] <rmt_> sorry, I'll clarify, I'd like to bind to another ip

[19:37:45] <rmt_> I receive the following error: MongoDB shell version: 2.4.6 connecting to: test Tue Oct 1 13:33:00.063 Error: couldn't connect to server 127.0.0.1:27017 at src/mongo/shell/mongo.js:145 exception: connect failed

[19:38:02] <rmt_> but I don't want it to try to connect to localhost

[19:38:28] <abonilla> rmt_: then run mongo my.new.ip.address/test

[19:38:41] <rmt_> okay, let me give it a try

[19:40:11] <rmt_> that worked

[19:40:37] <rmt_> but I ran mongo last night and had a few other dbs in there

[19:40:48] <rmt_> perhaps it did not connect to the proper ip?

[19:42:04] <abonilla> rmt_: show dbs and then show collections

[19:42:13] <rmt_> yes, only local shows

[19:42:34] <abonilla> if you switch back to localhost, can you see them?

[19:43:04] <rmt_> well, I can't connect to localhost

[19:43:04] <rmt_> :/

[19:43:51] <rmt_> so I suppose the try problem is, why can't I connect to localhost?

[19:43:54] <rmt_> true*

[19:44:16] <rmt_> I am running mongodb on bluehost, maybe they block localhost?

[19:44:34] <rmt_> but, it worked last night.. puzzled... ??!

[19:45:32] <rmt_> either way, at least I get on the proper i

[19:45:33] <rmt_> ip*

[19:45:40] <rmt_> thanks abonilla

[19:45:44] <abonilla> np

[19:50:56] <rmt_> abonilla, I do have another question- I tried to set up the mongodb.conf file but I receive an error when trying -f path/to/file ... does it matter where I put the file as long as I specify the path?

[19:51:49] <rmt_> or is the any special syntax I need to follow for it to read properly? current I have it so it reads logpath = "/path/to/log" etc..

[19:52:01] <rmt_> without quotes

[21:10:39] <zUriel_> Is somebody aware of project(s) aiming to provide mongodb-based Document Management Systems (with features like desktop integration) ?

[22:49:41] <drx_> yo

[22:50:03] <drx_> Why does MongoDB store ObjectID() string inside every UUID field ?

[23:05:53] <cheeser> what?

[23:07:02] <crudson> they are different types...not sure what the question is

[23:57:28] <ATX_123> i have 3 member replicaset. the primary has high IO and is in the middle of balancing. the two secondaries periodically get the following: SocketException: remote: x.x.x.x:27017 error: 9001 socket exception [3] server - then magically start working again later. ideas?