Updated omsagent installation guide for post install onboarding #185
Conversation
… use service-control to register the omsagent svc
| 3. Restart the omsagent: | ||
| `sudo service omsagent restart` | ||
| 3. Register the omsagent service and restart: | ||
| `sudo ./service_control enable` |
There was a problem hiding this comment.
Maybe specify the full path of the script
There was a problem hiding this comment.
I think this is wrong. You still want to use the restart command.
The restart command will register the service, enable the service (or it should upon registration), and then start the service. This is what you want.
If you simply enable it, that will enable restarting the service at reboot time, which is a subset of what you want.
Another iteration please, or just throw this away since existing code should be fine. If not, then another iteration please.
|
Signed off |
|
NOT signed off, see my comments. |
|
As per discussion, this is a doc change to be in sync with the current design since it is used by end user and current steps do not work. The user gets "service does not exist " error. Once the product is changed, the user documentation would need to be updated to be in sync with the new changes. |
Updated oms agent installation guide for post install onboarding to use service_control enable to register omsagent and restart the service altogether. Per current design, oms agent service restart no longer works since at the time it is called (right after onboarding using cmdline or a file) the agent is not registered as a service.
@Microsoft/omsagent-devs