Symptoms

This event can be logged as a Dial Home event, an MC UI event or seen in the command line of the Avamar Utility Node: Symptom: 22402, Desc: Could not save console server data to server. The following error may also be logged in the flush log (/usr/local/avamar/var/mc/server_log/flush.log) on the Avamar Utility Node: avtar Error <5137>: Unable to open "var/mc/server_data/mcserver.xml" for backup (code 13: Permission denied).

Cause

If any file in the directory "/usr/local/avamar/var/mc/server_data/prefs" does not have "admin:admin" ownership, flushes fail.

Resolution

Check the ownership of the files in the /usr/local/avamar/var/mc/server_data/prefs/ directory: 1. Log in to the Avamar Utility Node as admin and load the admin keys. For instructions on loading keys see Avamar: How to Log in to an Avamar Server and Load Various Keys. 2. Check the existing ownership: ls -la /usr/local/avamar/var/mc/server_data/prefs/ See APPENDIX A for sample output. a. If all file ownership is correctly set to "admin:admin," stop referencing this article and review Avamar: Symptom Code 22402 - Could not save console server data to server (Resolution Path) for additional troubleshooting. b. If any ownership is not admin:admin, go to Step 3. 3. Switch to the root user: su - 4. Change to the directory: cd /usr/local/avamar/var/mc/server_data/prefs 5. Correct the permissions on files that are not "admin:admin": chown admin:admin <filename> 6. Repeat for each file with incorrect ownership. 7. Restart the Management Console Server (MCS) using Avamar: How to Restart Management Console Server 8. Monitor the MC UI Event Monitor to ensure that MCS flushes are now working.If flush errors continue, review Avamar: Symptom Code 22402 - Could not save console server data to server (Resolution Path) for additional help.

Support Cases