ROSA Forum

Below error is continous in system logs. How to sort it out?

[root@localhost vmware]# tail -f /var/log/messages
Jul 9 20:19:13 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:14 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:15 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:16 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:16 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:16 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:16 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:16 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:16 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have an interface string as first arg
Jul 9 20:19:16 localhost udisks-daemon[1963]: ** (udisks-daemon:1963): WARNING **: Property get or set does not have

vmware?
I would set for the test on usb hdd.

I do the same. without VMware.

vadi01 писал(а):Below error is continous in system logs. How to sort it out?

create a file /etc/rsyslog.d/blacklist.conf and add there something like this:

Код: Выделить всё

:msg, contains, "upowerd" ~
:msg, contains, "udisks-daemon" ~

Not sure, probably, you'll need to restart rsyslogd afterwards (/etc/init.d/rsyslog.d restart).

Not sure, probably, you'll need to restart rsyslogd afterwards (/etc/init.d/rsyslog.d restart).

It may be necessary to give

Код: Выделить всё

systemctl restart rsyslog.service

VictorR2007 писал(а):
Not sure, probably, you'll need to restart rsyslogd afterwards (/etc/init.d/rsyslog.d restart).
It may be necessary to give
Код: Выделить всё
systemctl restart rsyslog.service

.. if you remember that strange systemctl commands

I'm not. Fortunately wrappers in /etc/init.d still work.

ROSA Forum

too many messages in /var/log/messages

too many messages in /var/log/messages

Re: too many messages in /var/log/messages

Re: too many messages in /var/log/messages

Re: too many messages in /var/log/messages

Re: too many messages in /var/log/messages

Re: too many messages in /var/log/messages