I was able to get the unit up after running asktime and selecting 2 of our AD time servers. It just took a really long time for the storage nodes to sync. We are back up. Thank you.
Has anything changed when you changed the server rooms ? I mean the network also! Could you give us some details about the avamar config ? like number of nodes, version etc.
Hello. Our version is 6.0.1.66. We have 6 nodes, 1 utility node, 1 spare node and 4 storage nodes. We have not changed the IP addresses of the nodes. We were able to move the stack and keep the existing IP scheme.
1 error seen in output of "/usr/bin/yes no | /usr/local/avamar/bin/restart.dpn
I am not sure what I am looking at with this error. Is this telling me the location of the error log?
This is from a verbose start. How can we change the time server setting for each of the nodes? It is probably incorrect now that we moved the equipment.
ERROR: Time on nodes too far out of sync: giving up, stopped at /usr/local/avamar/bin/dpn.pm line 5121.
- - - - - - - - - - - - - - - END
dpnctl: ERROR: error return from "/usr/bin/yes no | /usr/local/avamar/bin/restart.dpn --verbose" - exit status 255
dpnctl: ERROR: 1 error seen in output of "/usr/bin/yes no | /usr/local/avamar/bin/restart.dpn --verbose"
We did not complete a checkpoint, however previous checkpoints have been made in the past. We did properly shut down gsan. When we brought the nodes back up and typed in dpnctl the gsan did not start.
pbbakerii
7 Posts
4583
0
Posted July 24th, 2013 05:00
I was able to get the unit up after running asktime and selecting 2 of our AD time servers. It just took a really long time for the storage nodes to sync. We are back up. Thank you.