[DOCS-11228] Automation agent page should make clear that the server will not auto-start Created: 18/Jan/18  Updated: 10/Mar/21  Resolved: 30/Jan/18

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: 3.6 Required
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Nic Cottrell Assignee: Robert Justice (Inactive)
Resolution: Won't Fix Votes: 1
Labels: automation-agent, install
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Issue Links:
Related
is related to DOCS-5299 Note the automation agent installer d... Closed
Participants:
Days since reply: 6 years, 1 week, 5 days ago
Story Points: 0.2

 Description   

See https://docs.opsmanager.mongodb.com/current/tutorial/install-automation-agent-with-rpm-package/

There should be a new section entitled "Enabling service on system start" or similar.

It should be made clear to the user that the service will not auto-start, but that a command like

sudo systemctl enable mongodb-mms-automation-agent

or

sudo chkconfig mongodb-mms-automation-agent on

needs to be run to enable the service on system start. This has caused confusion with users moving to Ops Manager.



 Comments   
Comment by Nic Cottrell [ 02/Feb/18 ]

tim.olsen I never meant that this replaces the "start the agent" step - simply that when a machine restarts the agent does not and this has caused confusion at customers and unnecessary load on support. I understand that how to enable start on boot will be different for different platforms, but don't understand why that means we shouldn't at least have a "Note: ..." that installing the agent with RPM etc. does not necessarily make it autostart and that it's the administrators job to do so.

Comment by Nic Cottrell [ 18/Jan/18 ]

Related to https://jira.mongodb.org/browse/DOCS-5299

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