Discussion:
masked services and a lot of warnings
(too old to reply)
Reindl Harald
2013-02-17 17:33:08 UTC
Permalink
can we gat rid of this messages somehow?
i know that they are masked and can not be started
this as the reason to mask them

nobody needs upower on a virtual machine because
he connects via SSH and opens a X application with
X-Forwarding

Feb 17 17:32:21 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
Feb 17 17:32:21 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 17:32:21 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 17:32:24 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 17:32:24 buildserver dbus[450]: [system] Activation via systemd failed for unit 'upower.service': Unit
upower.service is masked.
Feb 17 17:32:24 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 17:32:24 buildserver dbus[450]: [system] Activation via systemd failed for unit 'upower.service': Unit
upower.service is masked.
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
Cristian Rodríguez
2013-02-17 18:33:39 UTC
Permalink
Post by Reindl Harald
can we gat rid of this messages somehow?
i know that they are masked and can not be started
this as the reason to mask them
nobody needs upower on a virtual machine because
he connects via SSH and opens a X application with
X-Forwarding
Huh ? isnt that bug in the unit instead.. ? there is no ned to mask it ,
just set ConditionVirtualization=false
Reindl Harald
2013-02-17 18:37:11 UTC
Permalink
Post by Cristian Rodríguez
Post by Reindl Harald
can we gat rid of this messages somehow?
i know that they are masked and can not be started
this as the reason to mask them
nobody needs upower on a virtual machine because
he connects via SSH and opens a X application with
X-Forwarding
Huh ? isnt that bug in the unit instead..
in which one?

this happens as example starting kate (a kde text editor)
Post by Cristian Rodríguez
there is no need to mask it , just set ConditionVirtualization=false
again: where?
Cristian Rodríguez
2013-02-17 18:48:28 UTC
Permalink
Post by Reindl Harald
Post by Cristian Rodríguez
Post by Reindl Harald
can we gat rid of this messages somehow?
i know that they are masked and can not be started
this as the reason to mask them
nobody needs upower on a virtual machine because
he connects via SSH and opens a X application with
X-Forwarding
Huh ? isnt that bug in the unit instead..
in which one?
this happens as example starting kate (a kde text editor)
Post by Cristian Rodríguez
there is no need to mask it , just set ConditionVirtualization=false
again: where?
vim /etc/systemd/system/upower.service

.include /usr/lib/systemd/system/upower.service

[Unit]
ConditionVirtualization=false


systemctl --system daemon-reload
Reindl Harald
2013-02-17 19:12:51 UTC
Permalink
Post by Cristian Rodríguez
Post by Reindl Harald
Post by Cristian Rodríguez
Post by Reindl Harald
can we gat rid of this messages somehow?
i know that they are masked and can not be started
this as the reason to mask them
nobody needs upower on a virtual machine because
he connects via SSH and opens a X application with
X-Forwarding
Huh ? isnt that bug in the unit instead..
in which one?
this happens as example starting kate (a kde text editor)
Post by Cristian Rodríguez
there is no need to mask it , just set ConditionVirtualization=false
again: where?
vim /etc/systemd/system/upower.service
.include /usr/lib/systemd/system/upower.service
[Unit]
ConditionVirtualization=false
systemctl --system daemon-reload
does not work inside a vmware guest
yes, systemctl daemon-reload was executed

and so again: why the hell are the warnings about masked services
yes they are masked for a reason

the same on yum updates if you masked atd.service and
google-crhome try to restart it - i know that it is masked
___________________________________

Feb 17 20:09:18 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 20:09:18 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 20:09:43 buildserver dbus-daemon[450]: dbus[450]: [system] Failed to activate service
'org.freedesktop.UPower': timed out
Feb 17 20:09:43 buildserver dbus[450]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Feb 17 20:09:43 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 20:09:43 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 20:10:08 buildserver dbus-daemon[450]: dbus[450]: [system] Failed to activate service
'org.freedesktop.UPower': timed out
Feb 17 20:10:08 buildserver dbus[450]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Feb 17 20:10:11 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 20:10:11 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'

[***@buildserver:~]$ cat /etc/systemd/system
system/ system.conf systemd-journald.conf systemd-logind.conf
[***@buildserver:~]$ cat /etc/systemd/system/upower.service
.include /usr/lib/systemd/system/upower.service

[Unit]
ConditionVirtualization=false
David Strauss
2013-02-18 01:17:49 UTC
Permalink
Couldn't you also just disable or mask the sources of activation?
Post by Reindl Harald
Post by Cristian Rodríguez
Post by Reindl Harald
Post by Cristian Rodríguez
Post by Reindl Harald
can we gat rid of this messages somehow?
i know that they are masked and can not be started
this as the reason to mask them
nobody needs upower on a virtual machine because
he connects via SSH and opens a X application with
X-Forwarding
Huh ? isnt that bug in the unit instead..
in which one?
this happens as example starting kate (a kde text editor)
Post by Cristian Rodríguez
there is no need to mask it , just set ConditionVirtualization=false
again: where?
vim /etc/systemd/system/upower.service
.include /usr/lib/systemd/system/upower.service
[Unit]
ConditionVirtualization=false
systemctl --system daemon-reload
does not work inside a vmware guest
yes, systemctl daemon-reload was executed
and so again: why the hell are the warnings about masked services
yes they are masked for a reason
the same on yum updates if you masked atd.service and
google-crhome try to restart it - i know that it is masked
___________________________________
Feb 17 20:09:18 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 20:09:18 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 20:09:43 buildserver dbus-daemon[450]: dbus[450]: [system] Failed to activate service
'org.freedesktop.UPower': timed out
Feb 17 20:09:43 buildserver dbus[450]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Feb 17 20:09:43 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 20:09:43 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 20:10:08 buildserver dbus-daemon[450]: dbus[450]: [system] Failed to activate service
'org.freedesktop.UPower': timed out
Feb 17 20:10:08 buildserver dbus[450]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Feb 17 20:10:11 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 20:10:11 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
system/ system.conf systemd-journald.conf systemd-logind.conf
.include /usr/lib/systemd/system/upower.service
[Unit]
ConditionVirtualization=false
_______________________________________________
systemd-devel mailing list
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
David Strauss
| ***@davidstrauss.net
| +1 512 577 5827 [mobile]
Mantas Mikulėnas
2013-02-18 07:00:56 UTC
Permalink
Post by David Strauss
Couldn't you also just disable or mask the sources of activation?
I'm not sure if this can be done when services are activated via DBus
– other than removing the files in /usr/share/dbus-1/system-services/,
which is "package manager territory".

In fact, masking the dbus-$name.service units at systemd level does
not help at all with the syslog spam; it only changes "No such file"
to "Masked".
--
Mantas Mikulėnas
Reindl Harald
2013-02-18 09:05:40 UTC
Permalink
Post by Mantas Mikulėnas
Post by David Strauss
Couldn't you also just disable or mask the sources of activation?
I'm not sure if this can be done when services are activated via DBus
– other than removing the files in /usr/share/dbus-1/system-services/,
which is "package manager territory".
In fact, masking the dbus-$name.service units at systemd level does
not help at all with the syslog spam; it only changes "No such file"
to "Masked"
yes, and "kate" is running fine without "upower.service"

i am not a big friend of this magic starting services
which you can't disable in a clean way
Mantas Mikulėnas
2013-02-18 09:38:31 UTC
Permalink
Post by Reindl Harald
Post by Mantas Mikulėnas
Post by David Strauss
Couldn't you also just disable or mask the sources of activation?
I'm not sure if this can be done when services are activated via DBus
– other than removing the files in /usr/share/dbus-1/system-services/,
which is "package manager territory".
In fact, masking the dbus-$name.service units at systemd level does
not help at all with the syslog spam; it only changes "No such file"
to "Masked"
yes, and "kate" is running fine without "upower.service"
i am not a big friend of this magic starting services
which you can't disable in a clean way
I'm aware of this. I have at least three programs that hopelessly try
to start Avahi.

I just see it a DBus bug (or lack of "masking" feature).
--
Mantas Mikulėnas
Lennart Poettering
2013-03-01 18:35:00 UTC
Permalink
Post by Reindl Harald
can we gat rid of this messages somehow?
i know that they are masked and can not be started
this as the reason to mask them
nobody needs upower on a virtual machine because
he connects via SSH and opens a X application with
X-Forwarding
Feb 17 17:32:21 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
Feb 17 17:32:21 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 17:32:21 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 17:32:24 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 17:32:24 buildserver dbus[450]: [system] Activation via systemd failed for unit 'upower.service': Unit
upower.service is masked.
Feb 17 17:32:24 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service'
Feb 17 17:32:24 buildserver dbus[450]: [system] Activation via systemd failed for unit 'upower.service': Unit
upower.service is masked.
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
name='org.freedesktop.UPower' unit='upower.service'
Feb 17 17:32:24 buildserver dbus-daemon[450]: dbus[450]: [system] Activation via systemd failed for unit
'upower.service': Unit upower.service is masked.
These are messages from dbus-daemon. Could you please file a bug against
D-Bus on fdo, requesting that these log messages are downgraded/turned off?

Lennart
--
Lennart Poettering - Red Hat, Inc.
Continue reading on narkive:
Loading...