search for: systemd1

...vm180" --- # journalctl -f -u systemd-machined.service -- Logs begin at Tue 2013-08-27 23:38:28 CEST. -- Dec 03 18:02:55 jupiter systemd-machined[23995]: Failed to start machine scope: Method "StartTransientUnit" with signature "ssa(sv)" on interface "org.freedesktop.systemd1.Manager" doesn't exist Dec 03 18:04:31 jupiter systemd-machined[23995]: Failed to start machine scope: Method "StartTransientUnit" with signature "ssa(sv)" on interface "org.freedesktop.systemd1.Manager" doesn't exist Dec 03 18:06:49 jupiter systemd-machin...

On a gentoo server with libvirt-1.1.3 I get problems with starting VMs. When I do: # virsh start vm180 error: Failed to start domain vm180 error: Input/output error This happens with 1.1.3 and 1.1.4 (I rebuilt the packages and restarted the libvirtd.service). # journalctl -f -u libvirtd.service shows: Dec 03 17:32:56 jupiter libvirtd[24020]: Input/output error Dec 03 17:33:47 jupiter

On my Centos 7 update, into "journalctl -f" I have tons of this kind of message > feb 17 23:52:09 s-ispc.local systemd-logind[663]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=17152 reply_cookie=0 error=n/a > feb 17 23:52:09 s-ispc.local systemd-logind[663]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice inte...

...rting up. Jan 21 16:10:39 linux7-7.mpc.local dbus[817]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to enable subscription: Failed to activate service 'org.freedesktop.systemd1': timed out Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to fully start up daemon: Connection timed out Jan 21 1...

...7.mpc.local dbus[817]: [system] Activating >> systemd to hand-off: service name='org.freedesktop.login1' >> unit='dbus-org.freedesktop.login1.service' >> Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to >> activate service 'org.freedesktop.systemd1': timed out >> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to >> enable subscription: Failed to activate service >> 'org.freedesktop.systemd1': timed out >> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to fully >> star...

...to subscribe to activation signal: Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to register name: Connection timed out Jan 30 20:40:02 VM systemd[1]: Failed to set up API bus: Connection timed out an 30 20:40:32 VM dbus[1009]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Jan 30 20:40:32 VM systemd-logind[998]: Failed to enable subscription: Failed to activate service 'org.freedesktop.systemd1': timed out Jan 30 20:40:32 VM systemd-logind[998]: Failed to fully start up daemon: Connection timed out Host machine specifications:- OS : Ub...

I've just updated a couple of servers, latest 7.3, and systemd is flooding dmesg, journalctl with info level messages... or maybe debug level 1. Examples: [ 478.258571] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=436 reply_cookie=0 error=n/a [ 478.258971] systemd[1]: Got notification message for unit systemd-logind.service [ 478.258980] systemd[1]: systemd-logind.service: Got notification message from PID 821 (...

...only Intel builtin graphics, and every single module installed is part of the CentOS distribution. This is from a file /tmp/xses-.XXXXXX (random 6-char string) xrdb: Can't open display '' xmodmap: unable to open display '' Failed to import environment: Process org.freedesktop.systemd1 exited with status 1 /usr/bin/xmbind: Can't open display Unable to init server: Could not connect: Connection refused Something is different in the way Xorg is started. In this situation, the first part of the Xorg log file (under ~/.local) is a dump of X command line options. use: X [:<di...

...16:10:39 linux7-7.mpc.local dbus[817]: [system] Activating > systemd to hand-off: service name='org.freedesktop.login1' > unit='dbus-org.freedesktop.login1.service' > Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to > activate service 'org.freedesktop.systemd1': timed out > Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to > enable subscription: Failed to activate service > 'org.freedesktop.systemd1': timed out > Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to fully > start up daemon: Connect...

...le. See below: nsasia at db2:/etc/tinc$ sudo systemctl enable tinc at VPN1 Created symlink /etc/systemd/system/tinc.service.wants/tinc at VPN1.service → /lib/ systemd/system/tinc at .service. nsasia at db2:/etc/tinc$ systemctl start tinc at VPN1 ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to start 'tinc at VPN1.service'. Authenticating as: NETsolutions (nsasia) Password: ==== AUTHENTICATION COMPLETE === nsasia at db2:/etc/tinc$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul t qle...

...[817]: [system] Activating >>> systemd to hand-off: service name='org.freedesktop.login1' >>> unit='dbus-org.freedesktop.login1.service' >>> Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to >>> activate service 'org.freedesktop.systemd1': timed out >>> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to >>> enable subscription: Failed to activate service >>> 'org.freedesktop.systemd1': timed out >>> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to &gt...

...and every single module installed is part of the CentOS distribution. > > This is from a file /tmp/xses-.XXXXXX (random 6-char string) > > xrdb: Can't open display '' > xmodmap: unable to open display '' > Failed to import environment: Process org.freedesktop.systemd1 exited with status 1 > /usr/bin/xmbind: Can't open display > Unable to init server: Could not connect: Connection refused > > Something is different in the way Xorg is started. In this situation, the first part of the Xorg log file (under ~/.local) is a dump of X command line optio...

...wrote: > I've just updated a couple of servers, latest 7.3, and systemd is flooding > dmesg, journalctl with info level messages... or maybe debug level 1. > > Examples: > [ 478.258571] systemd[1]: Sent message type=signal sender=n/a > destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice > interface=org.freedesktop.DBus.Properties member=PropertiesChanged > cookie=436 reply_cookie=0 error=n/a > > [ 478.258971] systemd[1]: Got notification message for unit > systemd-logind.service > [ 478.258980] systemd[1]: systemd-logind.service: Got notifi...

...Ah.. I know, you installed the "Standard Server"... These upgrades always fail, yes i run some ubuntu servers. 2 to be exact, for my kodi systems. > > On the first system I upgraded there was a file collision > with > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.ser > vice (I didn't note which packages) which caused the > do-release-upgrade program to die, I had to manually complete > the install after that > using apt commands. On the second system I moved this file > out of the way before starting and then cleaned it up at the &g...

...y were previously using the default packages on 16.04 and now default on 18.04. The original 16.04 installation was a standard server install + a few extra packages. What went wrong: On the first system I upgraded there was a file collision with /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service (I didn't note which packages) which caused the do-release-upgrade program to die, I had to manually complete the install after that using apt commands. On the second system I moved this file out of the way before starting and then cleaned it up at the end of the upgrade. The dpkg --...

...rg.freedesktop.locale1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.login1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.machine1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.systemd1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.timedate1.conf: Cannot write: No space left on device tar: ./etc/pam.d/systemd-user: Cannot write: No space left on device tar: ./etc/rsyslog.d/listen.conf: Cannot write: No space left on device tar: ./etc/system...

...rg.freedesktop.locale1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.login1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.machine1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.systemd1.conf: Cannot write: No space left on device tar: ./etc/dbus-1/system.d/org.freedesktop.timedate1.conf: Cannot write: No space left on device tar: ./etc/pam.d/systemd-user: Cannot write: No space left on device tar: ./etc/rsyslog.d/listen.conf: Cannot write: No space left on device tar: ./etc/system...

...ernel: [ 619.825758] nouveau E[ PFIFO][0000:01:00.0] SCHED_ERROR [ CTXSW_TIMEOUT ] Jul 16 17:27:15 dioo-XPS kernel: [ 619.825764] nouveau E[ PFIFO][0000:01:00.0] PGRAPH engine fault on channel 2, recovering... Jul 16 17:28:35 dioo-XPS dbus[894]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) The downstream bug is https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1474538 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freed...