Guralp Systems CMG-DCM build <10,000 - Manual (Page 270)

Acquisition Modules and Platinum Firmware Appendices
16.4 Appendix D - Troubleshooting
This section of the manual comprises answers to the questions most
frequently asked of our support team.
16.4.1 Upgrades report “Temporary failure in name resolution”
If an attempt to run the upgrade process produces error messages like
rsync: getaddrinfo: rsync.guralp.com 873: Temporary failure
in name resolution
rsync error: error in socket IO (code 10) at
clientserver.c(122) [receiver=3.0.2]
the Domain Name Service (DNS) client is misconfigured. If you are running
DHCP, this may be a problem with your DHCP server not providing a
nameserver (or providing an incorrect one). If you are using static
addressing, check and correct the
16.4.2 Upgrades report “Network is unreachable”
If an attempt to run the upgrade process produces error messages like
rsync: failed to connect to rsync.guralp.com: Network is
unreachable (101)
rsync error: error in socket IO (code 10) at
clientserver.c(122) [receiver=3.0.2]
the network routing is misconfigured. If you are running DHCP, this may be a
problem with your DHCP server not providing a default route (or providing an
incorrect one). If you are using static addressing, check and correct the
Default route (gateway) field in the “Network interface” configuration page, as
described in section 7.1.1 on page 71.
16.4.3 Upgrades report “rsync error”
If an attempt to run the upgrade process (using the GSL rsync server over the
internet) produces error messages like
rsync error: received SIGINT, SIGTERM or SIGHUP (code 20) at
rsync.c(541)
the likelihood is that a firewall is blocking traffic on the rsync port. Ask your
network administrator to permit the EAM to open TCP connections to host
rsync.guralp.com on port 873.
16.4.4 Errors during upgrade: “directory not empty”
This message can occur under two separate sets of circumstances.
On CMG-DCMs running firmware earlier than Build 3696, this message could
appear in relation to files with the .so extension and/or files in the
MAN-EAM-0003 270 Issue E - February 2014