[DOCS-1873] Installing Mongo DB Enterprise in Red Hat Linux 6.4 Created: 30/Aug/13  Updated: 11/Jan/17  Resolved: 31/Aug/13

Status: Closed
Project: Documentation
Component/s: production
Affects Version/s: mongodb-2.4
Fix Version/s: 01112017-cleanup

Type: Task Priority: Blocker - P1
Reporter: Srikanth Srinivasan Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat Linux 6.4 (Production)


Attachments: Text File Production - installation Notes.txt    
Participants:
Days since reply: 10 years, 24 weeks, 5 days ago

 Description   

We followed the below steps for installing mongo DB enterprise version
1. root access (SUDO) is available for SS208y
2. downloaded the TAR file from www.10gen.com/products/mongodbenterprise
3. TAR file - mongodb-linux-x86_64-subscription-rhel62-2.4.6.tar
4. placed the TAR file under /opt/app/p3tdac1/installables directory
5. tar -zxvf mongodb-linux-x86_64-subscription-rhel62-2.4.6.tar
6. cp -R -n mongodb-linux-x86_64-subscription-rhel62-2.4.6.tar/ mongodb

Question
--------------------------------

1) why is "service mongod start" and "service mongod stop" not working?

2) root access will be revoked after 7 days. how should we manage the process after that?



 Comments   
Comment by Sam Kleinman (Inactive) [ 31/Aug/13 ]

This is not the most appropriate forum for questions like this. Please address questions like this in one of our support channels: http://www.mongodb.org/about/support/

1. The package you installed did not include or create the appropriate system control scripts. You will need to create your own scripts or install from the RPM packages which include these scripts.

2. You will not need/sudo root access to run mongod processes as a user account that you have access to. sudo is only needed to run control scripts or if your user account does not have access the user that MongoDB will run as.

Regards,
sam

Generated at Thu Feb 08 07:42:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.