Re: nonstop logging isMaster and buildInfo commands

Erez - any findings there?

I'm getting the same behavior on my 2.6.5. 

Can it be related to some sort of an attack?

Erez wrote:

I'm seeing these types of messages continuously hitting the mongodb.log file in the mongo directory at log level 1, quiet: 1, mongo v2.6.4.

2014-10-07T10:56:10.335-0400 [conn8827] command admin.$cmd command: isMaster { ismaster: 1 } keyUpdates:0 numYields:0  reslen:178 0ms

2014-10-07T10:56:10.357-0400 [conn8721] command admin.$cmd command: isMaster { ismaster: 1 } keyUpdates:0 numYields:0  reslen:178 0ms

2014-10-07T10:56:10.357-0400 [conn8721] command admin.$cmd command: buildInfo { buildinfo: 1 } keyUpdates:0 numYields:0  reslen:699 0ms

2014-10-07T10:56:10.359-0400 [conn8827] command admin.$cmd command: buildInfo { buildinfo: 1 } keyUpdates:0 numYields:0  reslen:699 0ms

2014-10-07T10:56:10.469-0400 [conn8716] command admin.$cmd command: isMaster { ismaster: 1 } keyUpdates:0 numYields:0  reslen:178 0ms

2014-10-07T10:56:10.469-0400 [conn8717] command admin.$cmd command: isMaster { ismaster: 1 } keyUpdates:0 numYields:0  reslen:178 0ms

2014-10-07T10:56:10.470-0400 [conn8717] command admin.$cmd command: buildInfo { buildinfo: 1 } keyUpdates:0 numYields:0  reslen:699 0ms

2014-10-07T10:56:10.471-0400 [conn8716] command admin.$cmd command: buildInfo { buildinfo: 1 } keyUpdates:0 numYields:0  reslen:699 0ms

I tried disabling profiling on all my databases.  Any clues what could be causing this?  I set the profiling level to 0 for now so that the log doesn't get out of control.  I recently upgraded from 2.6.2 to 2.6.4.  Is this a bug in the recent version?

You're at logLevel 1 which says you want to log every operation.

Go back to default verbose level (which is 0) and you won't see these
in the logs.