Avamar: Unable to flush MCS after server_data files "Administrator Server flush failed." message due to filesystem corruption

Summary: Ungraceful shutdown resulted in corrupted files. Error Flushing Administrator Server "Administrator Server flush failed"

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.
Check out other resources

Symptoms

Proactive check reported file permissions failure as follows:

ERROR:  File /usr/local/avamar/var/mc/server_data/postgres/bad_data/pg_stat_tmp/db_0.stat is not readable by admin and will cause flush failures
ERROR:  File /usr/local/avamar/var/mc/server_data/postgres/bad_data/pg_stat_tmp/db_16384.stat is not readable by admin and will cause flush failures
RESOLUTION: Change permissions or move files. 
# --> File Permissions               *FAILED*

Attempt to manually flush MCS, fails (reduced output/command in bold):

admin@UtilityNode:~/>: mcserver.sh --flush --verbose
.
.
.
Flushing Administrator Server...
Administrator Server flush failed.

 

Cause

Ungraceful shutdown on the Avamar Server results in a corrupted filesystem with two bad files within.

Detected date when bad_data has been created:

root@UtilityNode:/data01/avamar/var/mc/server_data/postgres/#: ls -la /data01/avamar/var/mc/server_data/postgres/
total 8
drwx------  4 admin admin   32 Jul 21 13:21 .
drwxr-xr-x  6 admin admin 4096 Aug 15 14:32 ..
drwxr-xr-x  3 admin admin   24 Jul 21 13:21 bad_data
drwx------ 19 admin admin 4096 Aug 11 04:18 data

Corrupted files under /bad_data:

root@UtilityNode:/usr/local/avamar/var/mc/server_data/postgres/bad_data/pg_stat_tmp/#: ls -la
ls: cannot access db_0.stat: No such file or directory
ls: cannot access db_16384.stat: No such file or directory
total 0
drwx------ 2 admin admin 42 Jul 21 12:59 .
drwxr-xr-x 3 admin admin 24 Jul 21 13:21 ..
?????????? ? ?     ?      ?            ? db_0.stat
?????????? ? ?     ?      ?            ? db_16384.stat

Note how the time the system rebooted matches the modification date of the directory which contains the bad data.
root@UtilityNode:/data01/avamar/var/mc/server_data/postgres/#: uptime
 14:42pm  up 25 days  6:52,  1 user,  load average: 0.39, 0.42, 0.42

The cause for the reboot (on this particular example, it was a power outage). The /var/log/messages file contains the following:

Jul 21 05:49:33 UtilityNode ipmiutil: igetevent-gen4t: 00c7 07/21/17 05:49:29 MIN BMC Power Supply Status #98 External Fault (asserted) 6f [0d ff ff] - ELOG(632) 0x79 : 0xB800 0x7E : 0x00 0x80 : 0x00 0x01 : 0x80 0

 

Resolution

If the symptoms match on your Avamar system, engage Avamar Support and refer to this article (KB 503262)

Support reviews the system and, if the issue matches, they help identify the corrupted files and correct the issue.

 

Affected Products

Avamar

Products

Avamar
Article Properties
Article Number: 000052976
Article Type: Solution
Last Modified: 06 Nov 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.