Avamar: How to address a ddrmaint.log that is not updating
Summary: This article outlines how to address two known issues when the ddrmaint.log is not updating.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Instructions
Outlined below are two common issues that can cause the ddrmaint.log (DDR maintenance log) to stop updating on the Avamar Utility Node.
The log is located in /usr/local/avamar/var/ddrmaintlogs/.
Scenario 1: Permissions:
There is a permission issue on the log file.
The following error is reported in /var/log/messages:
May 7 10:59:59 avamar syslog-ng[16153]: Error opening file for writing; filename='/usr/local/avamar/var/ddrmaintlogs/ddrmaint.log', error='Permission denied (13)'
If this error is seen, see Avamar: Error opening file for writing; filename='/usr/local/avamar/var/ddrmaintlogs/ddrmaint.log'
Scenario #2: Thread Lock:
The Avamar syslogd process is not working correctly.
The handle of original ddrmaint.log is locked by a thread of syslogd, preventing new content from being added.
This can be corrected by restarting the syslogd service as root:
service syslog restartAffected Products
Avamar ServerArticle Properties
Article Number: 000029529
Article Type: How To
Last Modified: 12 Aug 2025
Version: 6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.