| Summary: | rtkit messages in /var/log/messages (syslog?) display the wrong time | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom London <selinux> | ||||
| Component: | rtkit | Assignee: | Lennart Poettering <lpoetter> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | lpoetter, stephent98 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-27 22:32:48 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Tom London
2011-03-22 02:36:08 UTC
hmm, if you disable selinux during boot, does the timezone work correctly then? Well, I've been booting permissively....
Here is a snippet from the latest boot:
Mar 31 06:32:45 tlondon pulseaudio[1788]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Mar 31 13:32:47 tlondon rtkit-daemon[843]: Successfully made thread 1811 of process 1811 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Mar 31 06:32:47 tlondon pulseaudio[1811]: pid.c: Daemon already running.
Mar 31 06:32:48 tlondon dbus: [system] Service 'org.freedesktop.ConsoleKit' is already active
Here is a snippet from the previous (enforcing) boot:
Mar 31 13:11:38 tlondon rtkit-daemon[840]: Failed to make thread 1542 RT: Operation not permitted
Mar 31 13:11:38 tlondon rtkit-daemon[840]: Failed to make thread 1542 RT: Operation not permitted
Mar 31 06:11:38 tlondon pulseaudio[1539]: module-alsa-card.c: Failed to find a working profile.
Mar 31 06:11:38 tlondon pulseaudio[1539]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
But it does appear that the 'first few' rtkit-daemon messages have the proper time:
[root@tlondon ~]# tail -1000 /var/log/messages | grep rtkit-daemon
Mar 31 06:32:06 tlondon kernel: [ 16.239978] rtkit-daemon[843]: Successfully called chroot.
Mar 31 06:32:06 tlondon kernel: [ 16.241647] rtkit-daemon[843]: Successfully dropped privileges.
Mar 31 06:32:06 tlondon kernel: [ 16.243194] rtkit-daemon[843]: Successfully limited resources.
Mar 31 06:32:06 tlondon kernel: [ 16.244753] rtkit-daemon[843]: Running.
Mar 31 06:32:06 tlondon kernel: [ 16.246333] rtkit-daemon[843]: Watchdog thread running.
Mar 31 06:32:06 tlondon kernel: [ 16.247906] rtkit-daemon[843]: Canary thread running.
Mar 31 13:32:29 tlondon rtkit-daemon[843]: Successfully made thread 1534 of process 1534 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
Mar 31 13:32:29 tlondon rtkit-daemon[843]: Failed to make thread 1537 RT: Operation not permitted
Mar 31 13:32:29 tlondon rtkit-daemon[843]: Failed to make thread 1537 RT: Operation not permitted
Mar 31 13:32:30 tlondon rtkit-daemon[843]: Failed to make thread 1538 RT: Operation not permitted
Mar 31 13:32:30 tlondon rtkit-daemon[843]: Failed to make thread 1538 RT: Operation not permitted
Mar 31 13:32:30 tlondon rtkit-daemon[843]: Failed to make thread 1539 RT: Operation not permitted
Mar 31 13:32:30 tlondon rtkit-daemon[843]: Failed to make thread 1539 RT: Operation not permitted
Mar 31 13:32:45 tlondon rtkit-daemon[843]: Successfully made thread 1788 of process 1788 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Mar 31 13:32:45 tlondon rtkit-daemon[843]: Successfully made thread 1789 of process 1788 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
Mar 31 13:32:45 tlondon rtkit-daemon[843]: Successfully made thread 1790 of process 1788 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
Mar 31 13:32:47 tlondon rtkit-daemon[843]: Successfully made thread 1811 of process 1811 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
[root@tlondon ~]#
This last set of messages was produced from a permissive boot ('enforcing=0'), but I see the same thing with an enforcing boot.
Created attachment 495167 [details]
/var/log/messages
rtkit-daemon is logging in UTC instead of local time.
Apr 27 03:06:26 fir pulseaudio [PDT = UTC - 7 ]
Apr 27 10:06:26 fir rtkit-daemon [UTC = PDT + 7]
$ date; date -u
Wed Apr 27 03:21:26 PDT 2011
Wed Apr 27 10:21:26 UTC 2011
$ getenforce
Enforcing
(In reply to comment #3) > rtkit-daemon is logging in UTC instead of local time. rtkit-0.10-1.fc15.x86_64 Recent rtkit chroot()s, and the timezone data is not available in it. Ideally rsyslog owuld just override the time data for local clients from SO_TIMESTAMP. Or glibc should be able to cache the tzdata instead of always going to disk. I think I filed a bug requesting the latter some time back. *** This bug has been marked as a duplicate of bug 698040 *** (In reply to comment #6) > > *** This bug has been marked as a duplicate of bug 698040 *** Reaction as expected, Commander ... ;-) |