greetings,
each and every time i run yum or yumex, system time is advanced by 5 hours.
this has gone on thru several updates, maybe even upgrades.
centos = 6.6 current yum = 3.2.29 yumex = 3.0.5
for awhile, i did not mind resetting clock when i noticed it off.
now, it is a pita because when i forget, emails and what ever else i am doing get wrong time stamps.
i have searched for problem/solution, but none found. or i missed it reading search page.
most appreciative if anyone knows of a solution.
tia.
On Tue, Jun 23, 2015 at 01:56:13PM -0500, g wrote:
each and every time i run yum or yumex, system time is advanced by 5 hours.
this has gone on thru several updates, maybe even upgrades.
centos = 6.6 current yum = 3.2.29 yumex = 3.0.5
for awhile, i did not mind resetting clock when i noticed it off.
now, it is a pita because when i forget, emails and what ever else i am doing get wrong time stamps.
i have searched for problem/solution, but none found. or i missed it reading search page.
most appreciative if anyone knows of a solution.
Hmmm, that's a really strange problem.
yum really doesn't have anything to do with your system clock. It just installs, updates and removes packages. I've never used 'yumex' but i assume it just runs yum behind the scenes.
The only thing I can think of is that your system is installing a tzdata package and failing, and somehow you're replacing the time zone with the original each time you fix it. Since your date is listed as -0500, it would seem likely that it is related.
Date: Tuesday, June 23, 2015 03:48:36 PM -0400 From: Jonathan Billings billings@negate.org
On Tue, Jun 23, 2015 at 01:56:13PM -0500, g wrote:
each and every time i run yum or yumex, system time is advanced by 5 hours.
this has gone on thru several updates, maybe even upgrades.
centos = 6.6 current yum = 3.2.29 yumex = 3.0.5
for awhile, i did not mind resetting clock when i noticed it off.
now, it is a pita because when i forget, emails and what ever else i am doing get wrong time stamps.
i have searched for problem/solution, but none found. or i missed it reading search page.
most appreciative if anyone knows of a solution.
Hmmm, that's a really strange problem.
yum really doesn't have anything to do with your system clock. It just installs, updates and removes packages. I've never used 'yumex' but i assume it just runs yum behind the scenes.
The only thing I can think of is that your system is installing a tzdata package and failing, and somehow you're replacing the time zone with the original each time you fix it. Since your date is listed as -0500, it would seem likely that it is related.
I agree, so my questions are:
- what is your TZ?
- what does "[/bin/]date" show?
- what does your hardware clock: "/sbin/hwclock --show" report? [need to be root to use that command]
- is your /etc/localtime file a standalone file or a symlink to /usr/share/zoneinfo/... ?
- if a symlink, to what file?
- what is the timestamp on the localtime (or what it's symlinked to) file?
- what does "zdump -v /etc/localtime" return ? i.e., is it for the correct TZ?
On Tue, Jun 23, 2015 at 07:51:39PM +0000, Richard wrote:
I agree, so my questions are:
what is your TZ?
what does "[/bin/]date" show?
what does your hardware clock: "/sbin/hwclock --show" report? [need to be root to use that command]
is your /etc/localtime file a standalone file or a symlink to /usr/share/zoneinfo/... ?
if a symlink, to what file?
what is the timestamp on the localtime (or what it's symlinked to) file?
what does "zdump -v /etc/localtime" return ? i.e., is it for the correct TZ?
To add to this list of questions:
- What are you doing to fix the clock each time you discover it is incorrect?
On 06/23/2015 02:53 PM, Jonathan Billings wrote: <<>>
To add to this list of questions:
- What are you doing to fix the clock each time you discover it is incorrect?
cussing and using "System Settings > Date & Time" to make change after i enter root user password. :-\
thanks again for you response.
Richard, thank you for your response.
On 06/23/2015 02:51 PM, Richard wrote: <<>>
I agree, so my questions are:
- what is your TZ?
u.s.a. 'central time zone' - currently on 'daylight savings time'.
- what does "[/bin/]date" show?
[geo@boxen ~]$ date Tue Jun 23 14:54:42 CDT 2015
- what does your hardware clock: "/sbin/hwclock --show" report? [need to be root to use that command]
[geo@boxen ~]$ sudo hwclock --show [sudo] password for geo: Tue 23 Jun 2015 02:55:40 PM CDT -0.899861 seconds
- is your /etc/localtime file a standalone file or a symlink to /usr/share/zoneinfo/... ?
currently it is a copy of file from /usr/share/zoneinfo/ on advice from a post to this list when i had problem getting correct time to show in clock in panel.
- if a symlink, to what file?
see above answer.
- what is the timestamp on the localtime (or what it's symlinked to) file?
2015-06-18 20:50
this file was copied several months ago so time stamp shows file has been updated.
- what does "zdump -v /etc/localtime" return ? i.e., is it for the correct TZ?
[geo@boxen ~]$ zdump -v /etc/localtime /etc/localtime -9223372036854775808 = NULL /etc/localtime -9223372036854689408 = NULL /etc/localtime Sun Nov 18 17:59:59 1883 UTC = Sun Nov 18 12:09:23 1883 LMT isdst=0 gmtoff=-21036
<one hell of a long list snipped>
/etc/localtime Sun Nov 1 06:59:59 2499 UTC = Sun Nov 1 01:59:59 2499 CDT isdst=1 gmtoff=-18000 /etc/localtime Sun Nov 1 07:00:00 2499 UTC = Sun Nov 1 01:00:00 2499 CST isdst=0 gmtoff=-21600 /etc/localtime 9223372036854689407 = NULL /etc/localtime 9223372036854775807 = NULL
[geo@boxen ~]$ zdump -v CDT /etc/localtime CDT -9223372036854775808 = NULL CDT -9223372036854689408 = NULL CDT 9223372036854689407 = NULL CDT 9223372036854775807 = NULL /etc/localtime -9223372036854775808 = NULL /etc/localtime -9223372036854689408 = NULL /etc/localtime Sun Nov 18 17:59:59 1883 UTC = Sun Nov 18 12:09:23 1883 LMT isdst=0 gmtoff=-21036 /etc/localtime Sun Nov 18 18:00:00 1883 UTC = Sun Nov 18 12:00:00 1883 CST isdst=0 gmtoff=-21600 /etc/localtime Sun Mar 31 07:59:59 1918 UTC = Sun Mar 31 01:59:59 1918 CST isdst=0 gmtoff=-21600
<similar hell of a long list like above>
/etc/localtime Sun Nov 1 06:59:59 2499 UTC = Sun Nov 1 01:59:59 2499 CDT isdst=1 gmtoff=-18000 /etc/localtime Sun Nov 1 07:00:00 2499 UTC = Sun Nov 1 01:00:00 2499 CST isdst=0 gmtoff=-21600 /etc/localtime 9223372036854689407 = NULL /etc/localtime 9223372036854775807 = NULL
[geo@boxen ~]$ zdump -v CDT CDT -9223372036854775808 = NULL CDT -9223372036854689408 = NULL CDT 9223372036854689407 = NULL CDT 9223372036854775807 = NULL
so, yes. i am in 'central time zone' observing 'daylight savings time'.
On 06/23/2015 04:47 PM, g wrote:
Richard, thank you for your response.
On 06/23/2015 02:51 PM, Richard wrote: <<>>
I agree, so my questions are:
- what is your TZ?
u.s.a. 'central time zone' - currently on 'daylight savings time'.
- what does "[/bin/]date" show?
[geo@boxen ~]$ date Tue Jun 23 14:54:42 CDT 2015
- what does your hardware clock: "/sbin/hwclock --show" report? [need to be root to use that command]
[geo@boxen ~]$ sudo hwclock --show [sudo] password for geo: Tue 23 Jun 2015 02:55:40 PM CDT -0.899861 seconds
- is your /etc/localtime file a standalone file or a symlink to /usr/share/zoneinfo/... ?
currently it is a copy of file from /usr/share/zoneinfo/ on advice from a post to this list when i had problem getting correct time to show in clock in panel.
- if a symlink, to what file?see above answer.
- what is the timestamp on the localtime (or what it's symlinked to) file?2015-06-18 20:50
this file was copied several months ago so time stamp shows file has been updated.
- what does "zdump -v /etc/localtime" return ? i.e., is it for the correct TZ?
[geo@boxen ~]$ zdump -v /etc/localtime /etc/localtime -9223372036854775808 = NULL /etc/localtime -9223372036854689408 = NULL /etc/localtime Sun Nov 18 17:59:59 1883 UTC = Sun Nov 18 12:09:23 1883 LMT isdst=0 gmtoff=-21036
<one hell of a long list snipped>
/etc/localtime Sun Nov 1 06:59:59 2499 UTC = Sun Nov 1 01:59:59 2499 CDT isdst=1 gmtoff=-18000 /etc/localtime Sun Nov 1 07:00:00 2499 UTC = Sun Nov 1 01:00:00 2499 CST isdst=0 gmtoff=-21600 /etc/localtime 9223372036854689407 = NULL /etc/localtime 9223372036854775807 = NULL
[geo@boxen ~]$ zdump -v CDT /etc/localtime CDT -9223372036854775808 = NULL CDT -9223372036854689408 = NULL CDT 9223372036854689407 = NULL CDT 9223372036854775807 = NULL /etc/localtime -9223372036854775808 = NULL /etc/localtime -9223372036854689408 = NULL /etc/localtime Sun Nov 18 17:59:59 1883 UTC = Sun Nov 18 12:09:23 1883 LMT isdst=0 gmtoff=-21036 /etc/localtime Sun Nov 18 18:00:00 1883 UTC = Sun Nov 18 12:00:00 1883 CST isdst=0 gmtoff=-21600 /etc/localtime Sun Mar 31 07:59:59 1918 UTC = Sun Mar 31 01:59:59 1918 CST isdst=0 gmtoff=-21600
<similar hell of a long list like above>
/etc/localtime Sun Nov 1 06:59:59 2499 UTC = Sun Nov 1 01:59:59 2499 CDT isdst=1 gmtoff=-18000 /etc/localtime Sun Nov 1 07:00:00 2499 UTC = Sun Nov 1 01:00:00 2499 CST isdst=0 gmtoff=-21600 /etc/localtime 9223372036854689407 = NULL /etc/localtime 9223372036854775807 = NULL
[geo@boxen ~]$ zdump -v CDT CDT -9223372036854775808 = NULL CDT -9223372036854689408 = NULL CDT 9223372036854689407 = NULL CDT 9223372036854775807 = NULL
so, yes. i am in 'central time zone' observing 'daylight savings time'.
Edit the file:
/etc/sysconfig/clock
make sure to set:
ZONE="America/Chicago"
then copy /usr/share/zoneinfo/America/Chicago to /etc/localtime
Run the time tool and make sure that "System clock uses UTC" is NOT checked
On Wednesday, 24 June 2015 at @01:25 zulu, Johnny Hughes johnny@centos.org wrote:
Run the time tool and make sure that "System clock uses UTC" is NOT checked
THAT's the option Anaconda also presents, that I was thinking of. :)
On 06/23/2015 08:25 PM, Johnny Hughes wrote: <<>>
Edit the file:
/etc/sysconfig/clock
make sure to set:
ZONE="America/Chicago"
it was;
ZONE="Etc/UTC"
it is now.
ZONE="America/Chicago"
then copy /usr/share/zoneinfo/America/Chicago to /etc/localtime
done.
Run the time tool and make sure that "System clock uses UTC" is NOT checked
if by 'time tool' you mean "System Settings > Date & Time", there is no "System clock uses UTC".
i ran 'yumex' to pull in some progs, 'tzdata-2015e-1.el6.noarch.rpm' was updated 2015-0621, so i could not pull it.
closed 'yumex' no change in system time in panel. rebooted, still OK.
1 problem left. :-(
when i started kde after rebooting, i ran the 'hwclock' and 'zdump' checks, all compared to before. but...
time stamp showing in konqueror is CST, not CDT.
when i mouse over clock in panel, 'Chicago' and 'UTC' times show correctly, ie,
Chicago 21:30, Wednesday 24 June 2015 UTC 02:30, Thursday 25 June 2015
'Chicago' is CDT, -0500 hrs, yet, knoqueror stamps CST.
what would be causing konqueror to be time stamping CST instead of CDT?
how to correct?
On 06/23/2015 02:48 PM, Jonathan Billings wrote: <<>>
Hmmm, that's a really strange problem.
if there were no strange problems, i would have no problems. ;-)
yum really doesn't have anything to do with your system clock. It just installs, updates and removes packages. I've never used 'yumex' but i assume it just runs yum behind the scenes.
i would think not, but something is happening.
The only thing I can think of is that your system is installing a tzdata package and failing, and somehow you're replacing the time zone with the original each time you fix it. Since your date is listed as -0500, it would seem likely that it is related.
time change happens even when there is no tzdata package.
-0500 = utc -0600 daylight savings time = utc -0500
thank you for responding.
-
Darr247 -
g -
Johnny Hughes -
Jonathan Billings -
Richard