Enabling the OMS Linux Agent fails with Enable failed with exit code 53 Installation failed due to incorrect workspace key
See original GitHub issueI completely removed and reinstalled the OMS for Linux Agent, but after the extension still fails with the following error:
Enable failed with exit code 53 Installation failed due to incorrect workspace key. Please check if the workspace key is correct. For details, check logs in /var/log/azure/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux/extension.log
Please help
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Enable failed with exit code 53 Installation failed due to ...
I was trying to enable a log analytic workspace in a VM, but i received the error " Enable failed with exit code...
Read more >incorrect workspace key while installing Log Analytics Agent ...
I just figured out, the reason why it got error above. For installing log analytics agent in linux machine ,we should enble access...
Read more >How To Re-Install Oms Agent For Linux On Azure - TekNeed
3. Check the OMS extension. If it has failed, disconnect and uninstall. ... NB: sometimes, you may not be able to disconnect or...
Read more >Troubleshoot the Ops Agent - Monitoring - Google Cloud
To fix the error, correct the invalid configuration and restart the agent. For reference, refer to the Configure the Ops Agent guide. Agent...
Read more >Troubleshooting Enterprise Manager - Oracle Help Center
While installing a Management Agent, the installation can fail on the product-specific prerequisite page with a host name error. This happens when the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@joshuawaddell thanks for the details. I was just experimenting a bit and found that since I already have an LB with Public IP I could add an outbound rule to the LB that allows Internet connectivity, my NSG already allowed outbound Internet access. It seems to work, but I’m not sure if this is the correct approach.
Have the same error, the message says:
Enable failed with exit code 53 Installation failed due to incorrect workspace key. Please check if the workspace key is correct. For details, check logs in /var/log/azure/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux/extension.log
but the error was as well because my load balancer didn’t have any way out from my vNet…Just adding rules for 443 port worked for me.