[SERVER-26805] Unauthorized: not authorized on admin to execute command { replSetGetStatus: 1.0 } log every two minutes in log Created: 27/Oct/16  Updated: 28/Oct/16  Resolved: 28/Oct/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.10
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Pierre-Alban DEWITTE Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Docker and Linux debian


Operating System: ALL
Steps To Reproduce:

mongod --replSet test --auth
mongo
rs.initiate()
db.getSiblingDB("admin").createUser(

{ user: "admin", pwd: "admin", roles: [ "root" ] }

)

Participants:

 Description   

We configure a fresh new 3.2.10 instance alone (but configured as a replicaset and with auth activated). We created a root user and two other that can only authenticated against our app db (let call it myappdb)

Every 2 minutes we see a log like that :
Oct 27 13:04:01 ip-172-17-0-1.us-west-2.compute.internal docker/0ab472e5c4e3[375]: 2016-10-27T13:04:01.531+0000 I ACCESS [conn250] Unauthorized: not authorized on admin to execute command

{ replSetGetStatus: 1.0 }

We have also a three members replicaset also deployed in 3.2.10 and see the exact same info message every two minutes.

We closed all our client connected to the db and did not see any change.

Even after a restart this log is always write at second 0,1,2 or 3 every two minutes.

Do you have any clue where does this annoying log come from ?



 Comments   
Comment by Pierre-Alban DEWITTE [ 28/Oct/16 ]

Ticket could be close. Thank you for your time.

Comment by Pierre-Alban DEWITTE [ 28/Oct/16 ]

OK my bad. A self made supervision check was launch in the crontab every two minutes without authentication causing the log.

Comment by Daniel Pasette (Inactive) [ 28/Oct/16 ]

You can check where the connection making the request is coming from by looking in the logs for the ip address which is logged at connection establishment. For the example error message you provided, the connection is "[conn250]" The log line will look like this:

2016-10-24T02:48:59.232+0000 I NETWORK  [initandlisten] connection accepted from 10.20.0.230:42132 #250 (25 connections now open)

Comment by Pierre-Alban DEWITTE [ 27/Oct/16 ]

No
We deploy using the mongdb docker image on EC2 instances

Comment by Daniel Pasette (Inactive) [ 27/Oct/16 ]

Are you using automation or monitoring?

Generated at Thu Feb 08 04:13:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.