microsoft / OMS-Agent-for-Linux

http://www.microsoft.com/oms
Other
411 stars 309 forks source link

all log collector output files and directories removed under /tmp/omslogs even before it is archived #757

Closed habtamua closed 1 month ago

habtamua commented 6 years ago

While i execute this python script, omslinux_agentlog.py all log collector output files and directories removed temporary files under /tmp/omslogs even before it is archived

these are the two command been executed at the end even before log file archived. rm -R -rf /tmp/omslogs rm -rf /tmp/oms.status

Here, I deliberately removed the primary key from here.... 😄 partial output of the execution ....

ps -e -o pid,ppid,user,etime,time,pcpu,nlwp,vsz,rss,pmem,args | grep -i omsagent | grep -v grep
/opt/microsoft/omsagent/bin/omsadmin.sh -l > /tmp/oms.status
bash ./dscDiagnostics.sh /tmp/omslogs/dscdiagnostics-2018-07-26T19:41:04.568851
tar: Removing leading `/' from member names
tar (child): /tmp/omslinuxagentlog-***************************w==-2018-07-26T19\:41\:03.678084.tgz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: /tmp/omslinuxagentlog-***********************************w==-2018-07-26T19\:41\:03.678084.tgz: Cannot write: Broken pipe
tar: Error is not recoverable: exiting now
2
tar -cvzf /tmp/omslinuxagentlog-*******************************w==-2018-07-26T19:41:03.678084.tgz /tmp/omslogs
2
rm -R -rf /tmp/omslogs

rm -rf /tmp/oms.status
hestolz commented 1 month ago

Thank you for your submission. As previously announced, the Log Analytics agent has been deprecated and has no support as of August 31, 2024. If you use the Log Analytics agent to ingest data to Azure Monitor, migrate now to the new Azure Monitor agent. As part of repo archival, open issues and pull requests will be closed.