Log file Viewer

[03:31:44] <ekaj> trying to understand how our prod mongodb is set up, it seems everything is listening on different ports besides 27017.. is this a common practice? All the guide I've followed (so far) keep it on 27017

[06:14:36] <ekaj> Ok, i'm looking at this link, but I'm having trouble finding the syntax to put this in mongod.conf.. it looks like it should be net.tls.CAFile; is that correct?

[06:14:37] <ekaj> https://docs.mongodb.com/manual/reference/program/mongo/#cmdoption-mongo-tlscafile

[06:15:35] <ekaj> yeah ok I think that's right

[10:00:01] <arteomp> hey, what do you think about general approach to create new indexes for mongo collections? Inside application code on the start of application or with migration tools like https://www.npmjs.com/package/migrate-mongo (or create own migration tool)

[10:04:19] <arteomp> we have a little holywar inside the team about the best approach for it) from app code or from infrastucure side

[10:14:21] <arteomp> from my point of view its safe enough just to check inside application on the start that all needed indexes exist and create it if some doesn't exist. And then you doesn't need to manage migration tool and migrations scripts for mongo. But is it still ok if you have thousands containers with micro-services and every of it will check own needed indexes on its start/restart/scaling? Look likes discussable...

[14:12:05] <ekaj> if you're starting a node with --tlsMode allowTLS, is there a way to see if it's actually doing TLS besides a pcap?

[18:08:05] <escanor> Hello all i am using node and mongodb

[18:08:30] <escanor> My Model.save function is giving an exception

[18:09:01] <escanor> I am using the following library

[18:09:04] <escanor> "express": "^4.17.1",

[18:09:04] <escanor> "mongodb": "^3.5.6",

[18:09:04] <escanor> "mongoose": "^5.9.9",