[SERVER-23443] Executing logRotate on Aribiters Created: 31/Mar/16  Updated: 31/Mar/16  Resolved: 31/Mar/16

Status: Closed
Project: Core Server
Component/s: Admin, Security
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kingsly J Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-5479 Arbiter in authenticated replica set ... Backlog
Operating System: ALL
Participants:

 Description   

Hi Team,
we are having a sharded cluster with two replica sets as shards. Each replicaset has a primary, a secondary and an arbiter. Our problem is hat we are not able to execute logRotate command from arbiter even though we have created the admin user in primary. As the users are not getting replicated, we are facing authorization error. Aslo please note that, in Sharded cluster we are using key file with 600 permission. please provide a solution regarding the same.

Regards,
Kingsly J



 Comments   
Comment by Ramon Fernandez Marina [ 31/Mar/16 ]

jebas.kings@gmail.com, this issue was previously reported in SERVER-5479, so I'm closing this ticket as a duplicate.

As per the logRotate documentation, you can send the SIGUSR1 signal to the mongod process to trigger log rotation as a workaround.

Regards,
Ramón.

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