Bug 743779 - too many messages in /var/log/messages
Summary: too many messages in /var/log/messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdelibs
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukáš Tinkl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 753431 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 01:52 UTC by nucleo
Modified: 2015-07-13 17:36 UTC (History)
44 users (show)

Fixed In Version: 4.8.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-04 23:21:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
strace capture from my machine. (26.56 KB, text/plain)
2012-01-05 07:15 UTC, Robin Laing
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 293495 0 NOR RESOLVED Fix udisk/upower property queries done by solid 2020-08-18 07:28:25 UTC

Description nucleo 2011-10-06 01:52:45 UTC
Description of problem:
There are sent too many messages by dbus-daemon to /var/log/messages.

Version-Release number of selected component (if applicable):
dbus-1.4.10-3.fc16.i686


Additional info:
Some of dbus-daemon messages in /var/log/messag:

Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:21 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:15:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:16:09 localhost dbus-daemon[4150]: ** (udisks-daemon:4348): WARNING **: Property get or set does not have an interface string as first arg
Oct  6 04:16:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:16:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:16:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-DEBUG: emitting changed on /sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/usb/hidd
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG:
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG:  user of caller is unix-user:root
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG:
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG:  user of caller is unix-user:root
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG:
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG:  user of caller is unix-user:root
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG:
Oct  6 04:29:05 localhost dbus-daemon[4150]: ** (polkitd:4247): DEBUG: system-bus-name::1.36 is inquiring whether system-bus-name::1.35 is authorized for org.freedesktop.color-manager.modify-device
Oct  6 04:32:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-DEBUG: emitting device-changed: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:32:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:33:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:33:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:34:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:34:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-DEBUG: emitting device-changed: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:34:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:35:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:35:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-DEBUG: emitting changed on /sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/usb/hiddev1
Oct  6 04:35:13 localhost dbus-daemon[4150]: (upowerd:4326): UPower-DEBUG: emitting device-changed: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:35:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-Linux-DEBUG: Polling: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:35:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-DEBUG: emitting changed on /sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/usb/hiddev1
Oct  6 04:35:43 localhost dbus-daemon[4150]: (upowerd:4326): UPower-DEBUG: emitting device-changed: /org/freedesktop/UPower/devices/ups_hiddev1
Oct  6 04:35:43 localhost dbus-daemon[4150]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda
Oct  6 04:35:43 localhost dbus-daemon[4150]: helper(pid  7010): launched job udisks-helper-ata-smart-collect on /dev/sda
Oct  6 04:35:43 localhost dbus-daemon[4150]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/host2/target2:0:1/2:0:1:0/block/sdb

Comment 1 Elad Alfassa 2011-10-06 07:37:44 UTC
The only dbus "bug" here is that it outputs DEBUG messages to the system log, which IMO should be changed for final.

The warnings aren't dbus fault, you should report separate bugs for upower and udisks about those.

Elad Alfassa,
Not a dbus developer.

Comment 2 Orion Poplawski 2011-10-14 22:47:05 UTC

*** This bug has been marked as a duplicate of bug 743344 ***

Comment 3 Orion Poplawski 2011-10-14 22:50:50 UTC
Okay, so we are waiting for debug messages to be deactivated in dbus?

Comment 4 nucleo 2011-10-17 22:31:24 UTC
There are also a lot of such messages in /var/log/messages:

Oct 18 01:26:36 localhost rsyslogd-2177: imuxsock begins to drop messages from pid 505 due to rate-limiting
Oct 18 01:26:43 localhost rsyslogd-2177: imuxsock lost 35 messages from pid 505 due to rate-limiting

pid 505 is dbus-daemon

Comment 5 nucleo 2011-10-18 17:21:32 UTC
So looks like part of this bug related with udisksd and polkitd messages was fixed.
https://bugzilla.redhat.com/show_bug.cgi?id=743344#c11

Now only upowerd messages neddes fixing.

Comment 6 David Zeuthen 2011-10-18 17:55:02 UTC
(In reply to comment #5)
> So looks like part of this bug related with udisksd and polkitd messages was
> fixed.
> https://bugzilla.redhat.com/show_bug.cgi?id=743344#c11

Well, there are updates for it, sure

 https://admin.fedoraproject.org/updates/udisks-1.0.4-2.fc16
 https://admin.fedoraproject.org/updates/polkit-0.102-2.fc16

but someone needs to make sure these updates ends getting picked up etc etc.


> 
> Now only upowerd messages neddes fixing.

Comment 7 nucleo 2011-10-21 15:36:47 UTC
Is there any progress with fixing such upowerd messages?

dbus-daemon[524]: ** (upowerd:1543): WARNING **: Property get or set does not have an interface string as first arg

Comment 8 Elad Alfassa 2011-10-21 15:47:20 UTC
Please file a separate bug under the upower component for this issue.

Comment 9 nucleo 2011-10-21 15:52:47 UTC
maybe just reassign this bug to upower?

Comment 10 Elad Alfassa 2011-10-21 15:56:08 UTC
Done.

Comment 11 Habig, Alec 2011-11-29 18:14:23 UTC
Still here, only now F-16 (with this bug) is released with this bug, and logfiles round the world are filling up with upowerd spam.  Is there at least a workaround for telling upowerd that we're not interested in debug level messages?

Comment 12 AMM 2011-12-20 12:05:44 UTC
Just noticed this bug today. Its flooding my log as well. (F16 with latest updates)

I checked old logs, in old logs, it stops after few lines (most likely system boot time). But today it just goes on continuously. I wonder why?

What does upowerd do anyway? Can I simply kill it?

Any plan to update upower package for this?

Thank you.

Comment 13 Orion Poplawski 2011-12-21 18:26:06 UTC
*** Bug 753431 has been marked as a duplicate of this bug. ***

Comment 14 AMM 2011-12-22 01:35:03 UTC
I dont see this bug if I boot my laptop after removing battery! i.e running only on AC.

Just incase it helps identify the bug.

Thank you.

Comment 15 Donald Cohen 2011-12-30 19:21:44 UTC
(In reply to comment #1)
> The only dbus "bug" here is that it outputs DEBUG messages to the system log,

I disagree - if you're going to report a problem then you could at least
provide some more info to locate the bug - how about telling us what property?
Also, isn't there some way to avoid repeating the message?  How about remembering that you reported it before?

Comment 16 Robin Laing 2012-01-05 07:15:01 UTC
Created attachment 550829 [details]
strace capture from my machine.

This should be about 2 minutes worth, four lines in messages.

Comment 17 Robin Laing 2012-01-05 07:32:35 UTC
Installed FC 16 yesterday and I already have over 4000 upowerd warnings.

Jan  4 23:29:09 eagle1 dbus-daemon[1414]: ** (upowerd:1745): WARNING **:
Property get or set does not have an interface string as first arg
Jan  4 23:29:39 eagle1 dbus-daemon[1414]: ** (upowerd:1745): WARNING **:
Property get or set does not have an interface string as first arg
Jan  4 23:29:39 eagle1 dbus-daemon[1414]: ** (upowerd:1745): WARNING **:
Property get or set does not have an interface string as first arg
Jan  4 23:30:09 eagle1 dbus-daemon[1414]: ** (upowerd:1745): WARNING **:
Property get or set does not have an interface string as first arg
Jan  4 23:30:09 eagle1 dbus-daemon[1414]: ** (upowerd:1745): WARNING **:
Property get or set does not have an interface string as first arg
Jan  4 23:30:39 eagle1 dbus-daemon[1414]: ** (upowerd:1745): WARNING **:
Property get or set does not have an interface string as first arg
Jan  4 23:30:39 eagle1 dbus-daemon[1414]: ** (upowerd:1745): WARNING **:
Property get or set does not have an interface string as first arg

----------  Checked on the laptop that I just installed FC16 on as well and
there is no difference if the AC is plugged in or not.  I still get a warning
every 30 seconds.

On a laptop with minimal HDD space, this can be a problem.


I attached an strace message if that can be of assistance.

Comment 18 AMM 2012-01-05 07:46:06 UTC
Umm.. its not abt AC adaptor. I mentioned abt Battery.. if I remove battery and run only on AC adaptor then the messages dont shows up in logs (needs reboot)

Comment 19 Robin Laing 2012-01-11 04:47:08 UTC
Sorry, misunderstood.

Comment 20 Pavel Alexeev 2012-01-15 09:02:48 UTC
I also have a lot of such messages - 2-5 in minutes. Is there at least workaround to mute it until it will be properly resolved?

Comment 21 Gilboa Davara 2012-01-21 10:00:38 UTC
I'm seeing the same on my Xeon workstation (connected to a APC PSU).
This issue seems to be rather new. (Haven't noticed it in the past)
FWIW, I'm using KDE 4.8rc (from kde-redhat).

- Gilboa

Comment 22 Chris Tatman 2012-02-06 04:30:59 UTC
I ran across this one today too after upgrading an F15 box to F16.  Not sure if it is taboo or not, but I am just telling rsyslog to discard these messages until this bug is fixed.

http://www.rsyslog.com/discarding-unwanted-messages/

So I created a file:

/etc/rsyslog.d/01-blocklist.conf

And added the following line:
:msg,contains,"WARNING **: Property get or set does not have an interface string as first arg" ~

Annoying message problem solved. Just need to remember to remove this rule once the bug is solved.  

Hope this helps someone.

Comment 23 Donald Cohen 2012-02-10 19:36:41 UTC
That last comment helped me, thanks.
had to kill and restart rsyslog though

Comment 24 Ale Qwerty 2012-02-18 15:08:55 UTC
I'm still getting this warning (repeated many times) under Fedora-16/KDE


** (upowerd:1627): WARNING **: Property get or set does not have an interface string as first arg


Linux fedora.linux 3.2.6-3.fc16.x86_64 #1 SMP Mon Feb 13 20:35:42 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux


udisks 1.04-3.fc-16 x86_64


Thanks.

Comment 25 Brian Burns 2012-04-01 01:51:08 UTC
(In reply to comment #22)
> And added the following line:
> :msg,contains,"WARNING **: Property get or set does not have an interface
> string as first arg" ~
> 
FYI, You can also use 'regex' here to be more selective.
:msg, regex, ".*upowerd.*WARNING \*\*\: Property get or set does not have an interface string as first arg$" ~

Comment 26 Brian Burns 2012-04-02 06:20:19 UTC
(In reply to comment #25)
> (In reply to comment #22)
> > And added the following line:
> > :msg,contains,"WARNING **: Property get or set does not have an interface
> > string as first arg" ~
> > 
> FYI, You can also use 'regex' here to be more selective.
> :msg, regex, ".*upowerd.*WARNING \*\*\: Property get or set does not have an
> interface string as first arg$" ~

My bad. This works.
:msg, ereregex, "upowerd.*WARNING.*Property get or set does not have an interface string as first arg" ~

This page helps as well :)
http://www.rsyslog.com/regex/

Comment 27 Sergio Basto 2012-04-02 17:45:24 UTC
solution on comment 22 , works for me ...

Comment 28 Anders Montonen 2012-06-05 11:57:04 UTC
Still seeing this in Fedora 17.

Comment 29 Chris Tatman 2012-06-05 17:03:16 UTC
Same here.  Problem still manifesting in F17.  Fresh install, and I had to apply my work around from comment# 22.

--Chris

Comment 30 Loïc Yhuel 2012-06-13 19:18:26 UTC
There is a KDE bug with a patch which fixes the bad D-Bus calls generating the upowerd/udisks-daemon warnings.
https://bugs.kde.org/show_bug.cgi?id=293495

Comment 31 Sergio Basto 2012-06-13 21:19:43 UTC
based on last comment is kde bug ? as anyone have this bug and don't use kde ?

Comment 32 Vasiliy Glazov 2012-07-05 06:46:43 UTC
I have this bug and KDE.
But here https://bugs.kde.org/show_bug.cgi?id=293495 bug has Status:	UNCONFIRMED

Comment 33 Germano Massullo 2012-07-16 09:51:57 UTC
I found this bugreport with Google since I am having on Fedora 17 a LOT of messages identical to

Jul 12 12:38:44 computer-4 upowerd[1738]: ** (upowerd:1738): WARNING **: Property get or set does not have an interface string as first arg

Comment 34 Sergio Basto 2012-07-16 20:31:00 UTC
(In reply to comment #33)
> I found this bugreport with Google since I am having on Fedora 17 a LOT of
> messages identical to
> 
> Jul 12 12:38:44 computer-4 upowerd[1738]: ** (upowerd:1738): WARNING **:
> Property get or set does not have an interface string as first arg

do you have KDE ?

Comment 35 Germano Massullo 2012-07-16 20:33:44 UTC
(In reply to comment #34)
> (In reply to comment #33)
> > I found this bugreport with Google since I am having on Fedora 17 a LOT of
> > messages identical to
> > 
> > Jul 12 12:38:44 computer-4 upowerd[1738]: ** (upowerd:1738): WARNING **:
> > Property get or set does not have an interface string as first arg
> 
> do you have KDE ?

Yes, 4.8.4 version

Comment 36 Johann Suhm 2012-07-16 23:47:33 UTC
same here with kde / 3.4.4-5.fc17.x86_64
I use the workaround from comment 26

Comment 37 Sergio Basto 2012-07-17 02:01:16 UTC
(In reply to comment #30)
> There is a KDE bug with a patch which fixes the bad D-Bus calls generating
> the upowerd/udisks-daemon warnings.
> https://bugs.kde.org/show_bug.cgi?id=293495

Since is verified that is a KDE bug, we should change component. Maybe to kde-workspace where found "Product : solid" of kde bug report.

Comment 38 Tim Landscheidt 2012-09-03 22:23:38 UTC
Is this bug still active after recent KDE updates?  I can't find any warnings in my /var/log/messages for the past four weeks.

Comment 39 Gilboa Davara 2012-09-04 01:32:40 UTC
Confirmed.
I no longer see upower / udisk events on the system log.

However, my system log now contains 50,000+ udev xend messages [1], but this is most likely another bug, I think.

- Gilboa
[1] "RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/xend.rules"

Comment 40 Kevin Kofler 2012-09-04 09:49:15 UTC
Yes, that's a bug in Xen.

Comment 41 Sergio Basto 2012-09-04 17:54:02 UTC
seems that we can close this bug as fixed. It appears clear in my systems too.

Comment 42 Chris Tatman 2012-09-04 17:58:26 UTC
Clear on mine as well.   I removed my work around from comment #22 and the messages are no longer showing up.

Comment 43 Kevin Kofler 2012-09-04 22:00:27 UTC
So, in what Fedora releases is this fixed now? Rawhide (19)? 18? 17? 16?

Comment 44 Sergio Basto 2012-09-04 22:04:26 UTC
17

Comment 45 Tim Landscheidt 2012-09-04 22:16:21 UTC
(In reply to comment #43)
> So, in what Fedora releases is this fixed now? Rawhide (19)? 18? 17? 16?

Works for me in F16.

Comment 46 Kevin Kofler 2012-09-04 23:21:57 UTC
Looks like the bad D-Bus calls have been fixed in kdelibs 4.8.5 by Lukáš Tinkl (according to the bugs.kde.org report). Now in principle upower still could avoid spamming /var/log/messages in that way, but nothing should trigger the log spam anymore. So let's close this as fixed.

Comment 47 Donald Cohen 2013-02-04 08:22:22 UTC
I just installed fedora 17 and I'm seeing this all over again!!

Comment 48 Sergio Basto 2013-02-04 19:51:08 UTC
(In reply to comment #47)
> I just installed fedora 17 and I'm seeing this all over again!!

You need update kde 
(Looks like the bad D-Bus calls have been fixed in kdelibs 4.8.5 by Lukáš Tinkl )

Comment 49 Donald Cohen 2013-02-04 20:00:05 UTC
Where do I get these updates?  Apper doesn't show anything for kde.


Note You need to log in before you can comment on or make changes to this bug.