PMXBOT Log file Viewer

Help | Karma | Search:

#mongodb logs for Wednesday the 6th of June, 2018

(Back to #mongodb overview) (Back to channel listing) (Animate logs)
[08:50:42] <reie> hello. When one contacts the sales team of MongoDB Inc. throught the 'Contact Us' web form on their site, what's the mean time to responce?
[08:56:37] <Derick> it should be pretty quick - how long ago did you fill it in?
[09:00:46] <reie> Derick: almost 24h ago
[09:02:32] <reie> I am not saying that they are slow or something.
[09:08:25] <Derick> I'd wait until tomorrow - ping me tomorrow morning if you haven't heard back?
[09:08:35] <Derick> I'll see whether I can chase it then
[09:08:49] <reie> Derick: ok, thanks
[09:53:02] <Veejay> Hello everyone, I've been trying to find a compatibilty table for the ODM / Ruby driver and the different versions of MongoDB (for example, if I were to use version 3.2.18, what version of Mongoid and associated Ruby driver would I need to use). If anyone knows of such a thing, I'm all ears
[09:54:51] <Derick> Veejay: https://docs.mongodb.com/ruby-driver/master/reference/driver-compatibility/
[09:58:26] <Veejay> Ah thanks, so basically if I use Mongoid 5, which depends on version 2.2.5 of the ruby driver, I should be OK to use version 3.2.x of the Mongo server, correct?
[09:58:54] <Veejay> Yeah seems so
[09:59:01] <Veejay> Thank you very much Derick
[13:40:29] <shayla> Hi all, i'm having a problem with a pipeline. https://pastebin.com/kKHej8M2 I got : "A pipeline stage specification object must contain exactly one field."
[13:40:31] <shayla> Where i'm wrong?
[13:42:13] <Derick> db.Collection.aggregate( [ { $group: { _id: {$week: 'issue.createdAt'}, "count": {$sum: 1} } } ])
[13:42:15] <Derick> is correct
[13:42:28] <Derick> you shouldn't use positional arguments, but an array of pipeline stages
[13:45:08] <shayla> Thank you so much, such an idiot question. Thanks
[13:45:57] <Derick> that's ok
[13:46:03] <shayla> I've got my field issue.createdAt that is a ISODate type. Is there any way to convert to Date so that $week works good with it?
[13:46:24] <shayla> Cause if I do something like {$week: '$issue.createdAt'}
[13:46:31] <shayla> It seems not correct the result
[13:46:37] <Derick> you can use $week with ISODate
[13:48:16] <shayla> Uh. Thanks. Just got confused by the $isoWeek
[13:48:44] <shayla> But why I have to do {$week: '$issue.createdAt'} instead of simply {$week: 'issue.createdAt'} ($)
[13:49:45] <Derick> because otherwise it uses it as a string ("issue.createdAt") and not a date/ISODate
[13:50:05] <Derick> the '$' in '$issue...' notifies that a field path is following
[13:50:37] <shayla> Just another idiot question :D Thank you so much Derick
[18:59:33] <dantti> I tried to build mongocxx driver on ubuntu18.04 but had issues with finding stuff, is there some guide to build it only with deps from distro packages?
[19:00:07] <dantti> afaik ubuntu pkg is the legacy one
[19:07:22] <deathanchor> I setup my replicaSet with net.ssl.mode: requireSSL how do I get my mms agent to use a pem file to connct?
[19:07:54] <deathanchor> i'm using a self-signed cert
[19:57:48] <deathanchor> i think i found it nowhttps://docs.opsmanager.mongodb.com/current/reference/monitoring-agent/#monitoring-agent-ssl-settings
[23:03:50] <markizano> Hello, we just had a clock skew in our db cluster this morning and wondering how this can be reset.
[23:04:13] <markizano> The clock skew was a major fault of the recent rdate command that syncs the time every night at 02:00 local time.
[23:04:42] <markizano> It set the year of the server to 2036 somehow, and then about 30mins later, when it reached it's next 02:00, it reset the time again to the most appropriate record.
[23:04:58] <markizano> While we're still trying to figure out how this happened - I am reaching out to this channel to understand what can be done about the oplog:
[23:05:34] <markizano> Is it in my best interests to just take an outage tonight to stop the app, stop the node, destroy the replset config, redo the rs.initialize() to replace the cluster config, and re-clone the data back to the secondary to reset the replset config?
[23:05:50] <markizano> or is there a way to trigger mongo to reset the "lastOplogDate" field in the replset config ?