[SERVER-24632] Mongotop not working Created: 17/Jun/16  Updated: 15/Nov/21  Resolved: 06/Sep/16

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 3.2.3
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Aayushi Mangal Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Participants:

 Description   

Hello Team,

I am getting error while using mongotop - having all the required roles.

Error:
Segmentation fault



 Comments   
Comment by Kelsey Schubert [ 06/Sep/16 ]

Hi aayushi,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,
Thomas

Comment by Kelsey Schubert [ 01/Aug/16 ]

Hi aayushi,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the complete output of the command you are executing?

Thank you,
Thomas

Comment by Kelsey Schubert [ 06/Jul/16 ]

Hi aayushi,

I'm a bit confused about the command you are using to start mongotop. When I try, I see

$ mongotop --discover --host hostname:port -u username -p pwd --authenticationDatabase whereuserExist
2016-07-06T14:41:01.948-0400	error parsing command line options: unknown option "discover"
2016-07-06T14:41:01.948-0400	try 'mongotop --help' for more information

Would you please provide the complete output including the execution of the command?

Thank you,
Thomas

Comment by Aayushi Mangal [ 18/Jun/16 ]

Hello Ramon,

Please find answers:

1) This is a three member replica set deployment
2) This is 3.2.3 version with wired tiger storage, or is there any way to check mongodb and mongotop version, but this is from same binaries
3) mongotop --discover --host hostname:port -u username -p pwd --authenticationDatabase whereuserExist
4)authentication used -SCRAM-SHA-1, should I provide all the user specific roles: - user have "clusteMonitor" role assigned to it
5) no any specific location to mongo log

Comment by Ramon Fernandez Marina [ 17/Jun/16 ]

aayushi, unfortunately there's not enough information on this ticket to know what could be the problem. I see 3.2.3 in the "Affects Version/s" field above, but can you add some more details about this issue? For example:

  • What kind of deployment do you have? Stand-alone? Replica set?
  • What version(s) of MongoDB and mongotop are you running (if ay of them is different than 3.2.3)
  • How are you running mongotop? Can you paste the exact command line you're using in this ticket?
  • How did you set up authentication? What are the contents of the system.users collection in the admin database? (Please redact passwords if any)
  • Is there any information in the mongod logs or the output of mongotop that may be relevant and can give us additional hints?

Thanks,
Ramón.

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