Azure / Azure/azure-linux-extensions
Installing Linux Diagnostic 3.0 failed by extention in azure
- Dominant language
- Python
- Stars
- 333
- Forks
- 278
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Description
Installing Linux Diagnostic 3.0 failed by extention in azure
Linux is red hat 7.7
here is output error:
2021/09/23 05:28:23 ERROR:CalledProcessError. Error Code is 1
2021/09/23 05:28:23 ERROR:CalledProcessError. Command string was /opt/microsoft/omsagent/bin/service_control restart LAD
2021/09/23 05:28:23 ERROR:CalledProcessError. Command result was
2021/09/23 05:28:23 [Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.135] Return 1:
2021/09/23 05:28:23 ERROR:[Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.135] Failed to set up mdsd dependencies: setup_omsagent(): Failed at restarting omsagent (fluentd). Exit code=1, Output=control_omsagent(restart) failed. Output:
2021/09/23 05:28:23 [Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.135] Enable,error,1,Failed to set up mdsd dependencies: setup_omsagent(): Failed at restarting omsagent (fluentd). Exit code=1, Output=control_omsagent(restart) failed. Output:
2021/09/23 05:28:23 [Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.135] Enable,error,-1,Enabled failed
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Linux Diagnostic 3.0 extension enable output on Red Hat 7.7, especially the service_control restart LAD command and the setup_omsagent/control_omsagent failure. Trace why fluentd or omsagent returns exit code 1 during dependency setup. Done means identifying a reproducible cause and confirming that the extension installs and enables successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, linux
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100