[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 |
|
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: — {{ [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 ] |
| Comment by Githook User [ 15/Dec/17 ] |
|
Author: {'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}Message:
|