Log file Viewer

[00:26:45] <falcom> When explaining an aggregated query (i'm grouping by the document field), are there any query plan for it?

[00:27:21] <falcom> First stage is the usual matching explaination, Second stage just reiterates my $group

[02:05:01] <Jonno_FTW> hello

[02:05:21] <Jonno_FTW> can anyone help with my aggregate across?

[02:46:57] <Jonno_FTW> actually nbm

[02:46:59] <Jonno_FTW> nvm

[02:50:05] <Sammitch> hey all. I'm trying to start mongod via systemctl and keep getting "Attempted to create a lock file on a read-only directory" but if I start it manually via `sudo -u mongod /usr/bin/mongod -f /etc/mongod.conf` it starts up just fine. what's the deal?

[09:55:48] <Derick> Sammitch: which lock file is it trying to create?

[17:33:13] <Sammitch> Derick: pretty sure it's $ddPath/mongod.lock

[17:40:44] <Derick> I don't know what $ddPath is

[17:45:51] <Sammitch> err, dbPath

[17:47:05] <Derick> does the service file not override the location?

[17:47:40] <Sammitch> nope

[17:55:37] <Sammitch> if start/stop manually, which works, and then try to start again with systemd without clearing the data dir I get '28596 Unable to determine status of lock file in the data directory /dbDir: boost::filesystem::status: Permission denied: "/dbDir/mongod.lock"'

[17:56:13] <Derick> right, with servicectl, it will likely run as the "mongodb" user, and not *your* user (root?)

[18:29:02] <Sammitch> yep. here's all the relevant config: https://hastebin.com/ocusuyojap.makefile

[19:12:10] <Derick> so who owns /dbPath and /dbPath/mongodb (use ls -l )

[19:32:29] <Sammitch> /dbPath 0755 mongod:mongod, /dbPath 0775 mongod:mongod

[19:33:03] <Sammitch> err that second one is /dbPath/mongodb

[19:33:38] <Derick> Sammitch: your error message says /dbDir, not /dbPath/mongodb

[19:34:34] <Sammitch> dbDir, dbPath, etc is actually my company name that I am editing out

[19:34:40] <Sammitch> apparently inconsistently

[19:35:07] <Sammitch> but I've repeatedly checked that it is correct

[19:36:03] <Sammitch> my predecessors have a habit of mounting data partitions at /companyName for whatever reason. :/

[19:36:29] <Derick> is that an NFS drive or something?

[19:36:45] <Sammitch> EBS volume for this one

[19:37:02] <Derick> I remember some issues with that, but quite a while in the past

[19:37:51] <Sammitch> issues with NFS or EBS?

[19:38:13] <Derick> I don't recall, it's more than a year ago

[19:39:16] <Sammitch> well EBS should look like a regular disk as far as anything above the OS is concerned

[19:39:28] <Derick> yeah

[19:41:50] <Sammitch> it's driving me nuts that this *only* happens when its launched with systemd, and I can't get any relevant debug info out of it

[19:42:02] <Derick> it must be a simple permissions issue...

[19:42:09] <Derick> is there nothing in the system's log either?

[19:44:22] <Sammitch> *facedesk* I've been wondering why there's not been ANY selinux info logged

[19:44:54] <Sammitch> because I keep looking at /var/log/secure and not audit =_=

[19:47:01] <Derick> so... it was selinux? :-/

[19:53:37] <Sammitch> in some manner, it would seem. I'm porting this ansible play from something based on Ubuntu 16.04 which apparently doesn't even have selinux installed, to a proper Centos 7 that actually matches the rest of our environment =_=

[19:55:08] <Sammitch> WARNING

[19:55:10] <Sammitch> On RHEL 7.0, if you change the data path, the default SELinux policies will prevent mongod from having write access on the new data path if you do not change the security context.

[19:55:30] <Sammitch> (ノಠ益ಠ)ノ彡┻━┻

[19:56:42] <Sammitch> such helpful docs that I didn't scroll down far enough to read T_T

[19:56:47] <Derick> :)

[19:56:52] <Derick> well, glad you found it.

[20:47:33] <Sammitch> Derick: thanks for the rubber ducking :D

[21:15:08] <Derick> Sammitch: no prob!

[22:16:34] <quarters> hello. I was wondering if anyone can offer advice on migrating sql data to mongodb. I'm currently using Ruby on Rails as my backend but am open to running the conversion through python or nodejs as well unless there's a direct means to do so. I was thinking that it can simply be a matter of leveraging the fact that my backend queries the sql database and responds with json objects to simply store the json objects

[22:16:34] <quarters> directly into mongodb