![]()
Invalid package architecture or there was a 200 error returned during onboarding. The shell bundle must be executed as root or there was a 403 error returned during onboarding. Also review to verify your proxy settings. We recommend that you use the universal installer from the latest release. The omsagent- deb.sh packages can only be installed on Debian-based systems. The omsagent- rpm.sh packages can only be installed on RPM-based systems. Invalid package type or invalid proxy settings. omsagent-*.universal*.sh -help for usage. Invalid option provided to the shell bundle. Sudo /opt/microsoft/omsconfig/Scripts/OMS_MetaConfigHelper.py -disable & sudo rm /etc/opt/omi/conf/omsconfig/configuration/Current.mof* /etc/opt/omi/conf/omsconfig/configuration/Pending.mof* Installation error codes Error codeīecause the necessary dependencies aren't installed, the auoms auditd plug-in won't be installed. For a single agent, run the following script: To disable configuration for all agents, disable collection from Agents configuration. etc/opt/microsoft/omsagent//conf/omsagent.d/*.confĮditing configuration files for performance counters and Syslog is overwritten if the collection is configured from the agent's configuration in the Azure portal for your workspace. Performance, Nagios, Zabbix, Log Analytics output and general agent etc/syslog-ng/nf or /etc/nf or /etc/rsyslog.d/nf #DOWNLOAD WORKSPACE MANAGER TOOLS FOR LINUX HOW TO#For more information about the tool and how to run it, see OMS Linux Agent Log Collector. We recommend that you use the Log Collector tool to retrieve important logs for troubleshooting or before you submit a GitHub issue. var/opt/microsoft/omsconfig/omsconfig.log Log Analytics agent configuration log file var/opt/microsoft/omsagent//log/omsagent.log Important log locations and the Log Collector tool File Run the purge script (with sudo permissions): Running the Troubleshooting Tool and Log Collector tool and attempting a clean reinstall helps to solve issues more quickly. ![]() This task might be the first suggestion from our support team to get the agent into an uncorrupted state. ![]() Purge and reinstall the Linux agentĪ clean reinstall of the agent fixes most issues. Having the logs initially will help our support team troubleshoot your issue faster. Run the Log Collector tool when you experience an issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |