Pivotal Knowledge Base

Follow

Timezone change using dca_setup completed successfully but it did not reflect the change on all servers

Problem

Timezone change using dca_setup completed successfully but it did not reflect the change on all servers

Cause

/etc/localtime was a symbolic link to one of the timezone files in /usr/share/zoneinfo directory, for some reason, the contents of the destination of the symbolic link pointed to the timezone before making the change.

In below example, timezone was changed from EST (New_York) to CST (Chicago) but the timezone remained EST

# date
Fri Nov 22 11:07:08 EST 2013

# ls -al /etc/localtime
lrwxrwxrwx 1 root root 35 Nov 22 10:12 /etc/localtime -> /usr/share/zoneinfo/America/Chicago

[root@mdw ~]# xxd /usr/share/zoneinfo/America/Chicago | tail -3
0000d90: 0045 5354 0045 5754 0045 5054 0000 0000  .EST.EWT.EPT....
0000da0: 0001 0000 0000 010a 4553 5435 4544 542c  ........EST5EDT,
0000db0: 4d33 2e32 2e30 2c4d 3131 2e31 2e30 0a    M3.2.0,M11.1.0.

# md5sum /usr/share/zoneinfo/America/New_York /usr/share/zoneinfo/America/Chicago
e4ca381035a34b7a852184cc0dd89baa  /usr/share/zoneinfo/America/New_York
e4ca381035a34b7a852184cc0dd89baa  /usr/share/zoneinfo/America/Chicago

The real cause for the above mentioned cause is yet to be known as the symptom is not reproducible in the lab.

Solution

Copy and restore the correct timezone file (in above example, /usr/share/zoneinfo/America/Chicago) from a healthy system.

If you do not have access to another healthy system, you can extract the timezone file from tzdata-2012j-1.el5 RPM package by doing the following as root:

cd /tmp

rpm2cpio /opt/rhel/55/CD1/Server/tzdata-2010e-1.el5.noarch.rpm | cpio --extract --make-directories ./usr/share/zoneinfo/America/Chicago

cp -ip ./usr/share/zoneinfo/America/Chicago /usr/share/zoneinfo/America/Chicago

Make sure the file permission is 644 and the ownership is root:root

Please NOTE: /etc/localtime file in some versions of DCA software is not a symbolic link , do investigate your current situation carefully before implementing the solution.

Comments

Powered by Zendesk