[DOCS-11126] Include 'Success' log output message in installation tutorials Created: 14/Dec/17  Updated: 30/Oct/23  Resolved: 15/Dec/17

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Ravind Kumar (Inactive) Assignee: Ravind Kumar (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 8 weeks, 6 days ago

 Description   

Source

The core issue is that the numerous warnings presented confuse the user into believing that the `mongod` is not running, or that there are errors that have to be resolved before moving forward.

The primary solution is to include the following snippet in each installation tutorial as a part of the 'run MongoDB' step:


Once you run MongoDB, monitor the terminal or log output. You may see warnings or other startup information related to your specific MongoDB instance. If you see the following output, or similar output, the MongoDB server started up successfully and is waiting for incoming connections:

{{ [initandlisten] waiting for connections on port 27017 }}

This could be a simple include. Already exists in Linux tutorials

It might be worth discussing the warnings users can expect to see when using the default config file - namely the access control and BindIP warnings.

We should ensure we always direct users to attempt to connect to the mongod after starting it up. For example, the MongoDB Windows service installation does not explicitly direct users to connect via mongo. Other pages may also have this issue, need to audit.

cc shannon.bradshaw@mongodb.com



 Comments   
Comment by Ravind Kumar (Inactive) [ 15/Dec/17 ]

merged

Comment by Githook User [ 15/Dec/17 ]

Author:

{'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}

Message: DOCS-11126: Improvements to Installation Tutorials

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