New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
AndreasKarz opened this Issue Apr 21, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@AndreasKarz

AndreasKarz commented Apr 21, 2017

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

This comment has been minimized.

Show comment
Hide comment
@lagalbra

lagalbra Apr 21, 2017

Member

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.

Member

lagalbra commented Apr 21, 2017

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

This comment has been minimized.

Show comment
Hide comment
@drivard

drivard Nov 21, 2017

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.

drivard commented Nov 21, 2017

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

This comment has been minimized.

Show comment
Hide comment
@antoniopll

antoniopll Jul 19, 2018

Same issue. Any solution?

antoniopll commented Jul 19, 2018

Same issue. Any solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment