Bug 583361
| Summary: | the system thinks that the hardware clock is set to UTC when it is not | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | atswartz |
| Component: | util-linux-ng | Assignee: | Karel Zak <kzak> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | atswartz, GoinEasy9, kzak, mzdunek, nphilipp, scottro11 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-08-09 17:29:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
atswartz
2010-04-18 06:08:52 UTC
I'm having similar problems, this is what the secure.log shows: Apr 17 01:43:22 localhost userhelper[2933]: pam_timestamp(gnome-system-log:auth): timestamp file `/var/run/sudo/GoinEasy9/unknown:root' has unacceptable age (14827 seconds), disallowing access to gnome-system-log for user GoinEasy9 Apr 17 01:43:26 localhost userhelper[2933]: pam_timestamp(gnome-system-log:session): updated timestamp file `/var/run/sudo/GoinEasy9/unknown:root' Apr 17 01:43:26 localhost userhelper[2941]: running '/usr/sbin/gnome-system-log ' with root privileges on behalf of 'GoinEasy9' I'm showing the same issue. I don't have system-config-date or Gnome installed. In dmesg it lists the correct date and time. uname -r 2.6.34-0.28.rc3.git3.fc14.i686.PAE No mention of timestamp in /var/log/secure.log I have the same issue on another KDE install, that is why I didn't know what package to file it against. (In reply to comment #0) > Description of problem:For the last few days I have been getting a: Superblock > last write time is in the future, in my boot.log. The system time is then > offset back five hours. I have never had it set to UTC and never even went > near the settings. I'm not sure that the system-config-date is the correct > package to file this against, but hwclock was not an option. Hwclock is part of the util-linux-ng package, changing component. After update tonight, problem still persists, and, if it's related, weather location in Clock loses it's location and has to be reset. I read a post on the fedora forum that claimed in yesterday's update util-linux-ng reverted back (if updating to a newer version is actually reverting back) to the version in F13, util-linux-ng-2.17.2-3.fc13.i686.rpm, and that fixed the problem. In tonight's update I didn't see that reversion happen. When I tried to pull the file in from koji, it would require my downgrading (or upgrading) 2 other files: could not do simulate: util-linux-ng-2.17.2-3.fc13.i686 requires libblkid = 2.17.2-3.fc13 util-linux-ng-2.17.2-3.fc13.i686 requires libuuid = 2.17.2-3.fc13 I don't know if that will just cause more problems so I'm waiting for that version to be included in the F14/rawhide repo. Since it is a newer version of what is in the F14 repo presently - util-linux-ng-2.17.2-1.fc14.i686. I am no longer having time problems on either machine. Although on one, I now have util-linux-ng-2.17.2-3.fc13.x86_64 and the other util-linux-ng-2.17.2-1.fc14.x86_64, so it must have been a different package that was causing the problem. I now have "downgraded" the util-linux-ng-2.17.2-3.fc13.x86_64 package to the f14 version (util-linux-ng-2.17.2-1.fc14.x86_64) and all is well. I am also no longer having a problem with time. The problem must have been elsewhere. I have had the following version of the apps all along. util-linux-ng-2.17.2-1.fc14.i686 libuuid-2.17.2-1.fc14.i686 libblkid-2.17.2-1.fc14.i686 I have dual boot with windows, when i reboot to other os clock speeds up +2h, my timezone is +2h from GMT hwclock --localtime pon, 7 cze 2010, 00:31:18 -0.072457 sekund from boot.log /dev/sdb2: Superblok last mount time is in the future. (by less than a day, probably due to the hardware clock being incorrectly set) POPRAWIONO. kernel 2.6.33.5-112.fc13.x86_64 util-linux-ng.x86_64 2.17.2-5.fc13 This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |