You are on page 1of 1

Customer View

Avamar - Symptom Code 4202 - failed garbage collection with error MSG_ERR_BADTIMESYNC

Article Number: 458081


Version: 3
Article Type: Break Fix
Last Published: 20 Jun 2019
Summary:

Issue Avamar maintenance activities will fail.

The garbage collection process will fail.


Error messages received via High Priority Events, ConnectEMC (DialHome) or Events Management in the MCGUI:

ERROR: <4202> failed garbage collection with error MSG_ERR_BADTIMESYNC

Cause Time is not in sync between one or more Avamar data nodes and utility node.
If time is not in sync this can cause Avamar maintenance activiites to fail

Resolution Workaround:
1. Login to the Avamar server via a putty session and load the admin keys. See 95614 for instructions on loading keys.

2. Verify time is in sync across all Avamar nodes. See APPENDIX A for sample output.

mapall --all --parallel 'date'

If the time is in sync then do not proceed with this KB article.


If the time is out of sync proceed to Step 2.

3. Please follow the steps in KB Link Error 108926 to sync time across all nodes.

4. Once time is in sync verify that garbage collection passes with no errors.

5. If the time is still out of sync and garbage collection is failing please contact EMC Technical Support.

Notes APPENDIX A:
Sample output for mapall date command.
All node times are in sync.

mapall --all --parallel 'date'

Using /usr/local/avamar/var/probe.xml
(0.s) ssh -x -o GSSAPIAuthentication=no admin@192.168.255.1 'date'
(0.0) ssh -x -o GSSAPIAuthentication=no admin@192.168.255.2 'date'
(0.1) ssh -x -o GSSAPIAuthentication=no admin@192.168.255.3 'date'
(0.2) ssh -x -o GSSAPIAuthentication=no admin@192.168.255.4 'date'
Mon May 12 20:26:25 UTC 2014
Mon May 12 20:26:25 UTC 2014
Mon May 12 20:26:25 UTC 2014
Mon May 12 20:26:25 UTC 2014

Attachments

Article Properties

First Published Fri Feb 05 2016 17:06:41 GMT

Primary Product Avamar

Product Avamar, Avamar Server 5, Avamar Server 6, Avamar Server 7

You might also like