search

microsoft / PowerShell-DSC-for-Linux

PowerShell Desired State Configuration - for Linux
Other
338 stars 131 forks source link

I think it's a problem with the rights to a custom log #258

Open AndreasKarz opened 7 years ago

AndreasKarz commented 7 years ago

4/21/2017 7:05:28.257 PM | Operation ...TimeGenerated:4/21/2017 7:05:28.257 PM ...Computer:ECDL0101 ...Detail:Two successive configuration applications from OMS Settings failed – please report issue to github.com/Microsoft/PowerShell-DSC-for-Linux/issues ...OperationCategory:OMS Agent for Linux issue ...Solution:Log Management ...SourceSystem:OpsManager ...SourceComputerId:4d6189c4-4bd0-41f9-812a-035825404c8b ...OperationStatus:Warning

lagalbra commented 7 years ago

Can you provide the file permissions of a log that you are trying to tail through our CustomLog feature?

If this is the issue, the temporary workaround would be to give omsagent permissions on that file and its containing folder:

Identify the file group for the log files, and add the user omsagent to the file group:

ls -l <MySQL-file-path-for-slow-query-logs>
usermod -aG <file-group> omsagent

We are still in progress for a fix to allow the CustomLog feature to tail any read-protected file.

drivard commented 6 years ago

I tried the fix of adding the omsagent user to the group creating the log file, but I am still getting the same error. I also tried running the app creating the log file as omsagent and I was able to run my app, see the logs being generated, but I was still getting the error Two successive configuration applications from OMS Settings failed. I tried with the latest agent omsagent-1.4.2-124.universal.x64.sh and the previous omsagent-1.4.1-45.universal.x64.sh. Any other way to fix this issue? I am on Ubuntu 16.04 latest patch.

antoniopll commented 6 years ago

Same issue. Any solution?

shazbot1 commented 5 years ago

I am also facing the same issue. CentOS 7 minimal 1804. OMS Government, omsagent-1.8.1-256.universal.x64.sh. Any solutions as of yet?

Seclogic commented 5 years ago

Even by adding the user into the correct group I still get the error with the latest OMSagent and Ubuntu 16.04 Someone managed to fix it ?