[BUG] logrotate config waagent-extn.logrotate conflict with azure-lad
See original GitHub issue/etc/logrotate.d/waagent-extn.logrotate
which is installed by WALinuxAgent 2.2.46 conflict with /etc/logrotate.d/azure-lad
which is installed by lad-mdsd-1.5.109-LADmaster.101.x86_64.
Distro and WALinuxAgent details (please complete the following information):
- Any Distro with 2.2.46
Additional context The rotate file was merged by #1740
Log file attached
# logrotate /etc/logrotate.conf
error: waagent-extn.logrotate:1 duplicate log entry for /var/log/azure/Microsoft.Azure.Diagnostics.LinuxDiagnostic/extension.log
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Azure linux VM error: waagent-extn.logrotate:1 - Microsoft Q&A
After a minor Linux OS version upgrade we have noticed a problem with the following command: logrotate /etc/logrotate.conf error: ...
Read more >Logrotate - Is there a conflict? - Server Fault
There is no conflict, but there is a problem. Your config will cause auth.log to be rotated daily, without notifying rsyslog.
Read more >1992155 – consider splitting out logrotate config and ...
Bug 1992155 - consider splitting out logrotate config and dependency in a subpackage ... for rotating logs (where the default config may conflict...
Read more >error with logrotate that it has insecure permissions | Support
Set the "su" directive in the config file to tell logrotate which user/group should be used for rotation. When mysql has been installed,...
Read more >How to Manage Log Files Using Logrotate - Datadog
In this case, logrotate will only run the rsync script once, after all Apache access and error logs are rotated. This configuration ensures...
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
Hi there!
I think that I found the same issue:
It’s looks like, the waagent try to handle the log rotation for omsagent logs but omsagent has already a logrorate configuration:
Is waagent is legitimate to rotate the logs of other plugin/extension which are not populated by waagent ?
Fixed by #2143