You are not logged in.

#1 2014-02-28 17:00:42

schnip_schnap
Member
Registered: 2014-02-28
Posts: 6

Failed to activate service 'org.freedesktop.systemd1': timed out

Hey guys,



after restoring a complete tar system backup (excluding, /mnt,/run,/proc,/sys,/dev,/tmp,/lost+found) i have run into this problem when trying to login via tty:


Complete journal for boot:

http://pastebin.com/XyBdTb0U



Interesting part:

http://pastebin.com/Sz5u1N84


The systems seems usable (after the login delay) and X seems to start fine (according to the log file) But i only get a black screen when i use startx. Could it be that excluding all the paths
( /mnt,/run,/proc,/sys,/dev,/tmp,/lost+found) was too much? I recreated them with the proper permissions after restoring the backup.(bootable usbstick) I thought nothing of these directories should be in the backup as they are virtual file systems, am i right?


This part causes a massive delay of 16 seconds after hitting enter to login:

Mär 02 18:29:08 arch login[259]: pam_unix(login:session): session opened for user root by (uid=0)
Mär 02 18:29:08 arch dbus[257]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Mär 02 18:29:24 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out

Then this happens (Failed to create session and root logs in anyways):


Mär 02 18:29:24 arch dbus[257]: [system] Successfully activated service 'org.freedesktop.login1'
Mär 02 18:29:24 arch systemd-logind[256]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
Mär 02 18:29:24 arch systemd-logind[256]: Watching system buttons on /dev/input/event3 (Power Button)
Mär 02 18:29:24 arch systemd-logind[256]: Watching system buttons on /dev/input/event2 (Power Button)
Mär 02 18:29:24 arch systemd-logind[256]: New seat seat0.
Mär 02 18:29:33 arch login[259]: pam_systemd(login:session): Failed to create session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:29:33 arch login[259]: ROOT LOGIN ON tty1

Some more failures afterwards:


Mär 02 18:29:49 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mär 02 18:29:49 arch systemd-logind[256]: Failed to start unit user-0.slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:29:49 arch systemd-logind[256]: Failed to start user slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:30:14 arch systemd-logind[256]: Failed to start unit user@0.service: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:30:14 arch systemd-logind[256]: Failed to start user service: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:30:14 arch systemd-logind[256]: Assertion 's->user->slice' failed at src/login/logind-session.c:502, function session_start_scope(). Aborting.
Mär 02 18:30:14 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mär 02 18:30:15 arch systemd-coredump[360]: Process 256 (systemd-logind) dumped core.
Mär 02 18:30:15 arch systemd[1]: systemd-logind.service: main process exited, code=dumped, status=6/ABRT
Mär 02 18:30:15 arch systemd[1]: Failed to start Login Service.
















OLD DIAGNOSTICS START HERE:



------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
i restored a complete system backup of my arch installation. I used this to create the backup:


tar -zcvpf /mnt/usb/backup.tar.gz --directory=/ --exclude=run --exclude=mnt --exclude=proc --exclude=sys --exclude=dev --exclude=tmp --exclude=lost+found .


To restore i reformatted my disk and put the tar archive in the root dir. Then used this command:



tar xvpfz backup.tgz

and manually created the directores i excluded in the backup command.





My system boots but i get weird delays when trrying to login. I dont use graphical login but tty. I put in my User [ENTER] put in my password [ENTER] then i have 10 seconds delay until i get logged in. When i use startx i just get a black screen. Everything else from the console seems to work though...



Thanks in advance!

Last edited by schnip_schnap (2014-03-02 22:43:09)

Offline

#2 2014-02-28 17:10:05

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,280

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

What are the file system types?
What is the output of mount   ?
What are the contents of /etc/fstab  ?
Please post your ~/.xinitrc.
Please post your /var/log/Xorg.0.log 

Oh, and welcome to Arch Linux.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2014-02-28 21:56:48

schnip_schnap
Member
Registered: 2014-02-28
Posts: 6

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

Please look at my first post or my last post on this thread. Thanks





OLD DIAGNOSTICS START HERE:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

the file system type of my root fs is ext4. (/dev/sdd3) My boot partition is ext2 (/dev/sdd1)



mount:

[root@arch /]# mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=4071128k,nr_inodes=1017782,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sdd3 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
/dev/sdd1 on /boot type ext2 (rw,relatime)

fstab


[root@arch /]# cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# UUID=78c56dfc-1e70-47a4-a65a-1ae2f9ec8f2b
UUID=78c56dfc-1e70-47a4-a65a-1ae2f9ec8f2b               /boot           ext2            rw,relatime     0 2

# UUID=62ff7e52-da9f-4798-abd7-346515d2d358
UUID=62ff7e52-da9f-4798-abd7-346515d2d358               none            swap            defaults        0 0

# /dev/sdd3
UUID=116cd475-bd76-4168-a7b9-6d5a43b52484       /               ext4            rw,relatime,data=ordered        0 1

.xinitrc

[root@arch /]# cd /home/schnip/
[root@arch schnip]# cat .xinitrc
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

[[ -f ~/.Xresources ]] && xrdb -merge ~/.Xresources

exec awesome



Xorg.0.log


[root@arch log]# cat Xorg.0.log
[   659.409]
X.Org X Server 1.15.0
Release Date: 2013-12-27
[   659.410] X Protocol Version 11, Revision 0
[   659.410] Build Operating System: Linux 3.12.5-1-ARCH x86_64
[   659.410] Current Operating System: Linux arch 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64
[   659.410] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=UUID=116cd475-bd76-4168-a7b9-6d5a43b52484 rw initrd=../initramfs-linux.img
[   659.410] Build Date: 09 January 2014  08:47:24AM
[   659.410]
[   659.411] Current version of pixman: 0.32.4
[   659.411]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[   659.411] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   659.412] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 28 22:40:12 2014
[   659.414] (==) Using config file: "/etc/X11/xorg.conf"
[   659.414] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   659.415] (==) ServerLayout "Layout0"
[   659.415] (**) |-->Screen "Screen0" (0)
[   659.415] (**) |   |-->Monitor "Monitor0"
[   659.415] (**) |   |-->Device "Device0"
[   659.415] (**) |-->Input Device "Keyboard0"
[   659.415] (**) |-->Input Device "Mouse0"
[   659.415] (**) Option "Xinerama" "0"
[   659.415] (==) Automatically adding devices
[   659.415] (==) Automatically enabling devices
[   659.415] (==) Automatically adding GPU devices
[   659.418] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   659.418]    Entry deleted from font path.
[   659.418] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   659.418]    Entry deleted from font path.
[   659.418]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   659.418] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   659.418]    Entry deleted from font path.
[   659.418]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   659.418] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/Type1/
[   659.418] (==) ModulePath set to "/usr/lib/xorg/modules"
[   659.418] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[   659.418] (WW) Disabling Keyboard0
[   659.418] (WW) Disabling Mouse0
[   659.418] (II) Loader magic: 0x804c80
[   659.418] (II) Module ABI versions:
[   659.418]    X.Org ANSI C Emulation: 0.4
[   659.418]    X.Org Video Driver: 15.0
[   659.418]    X.Org XInput driver : 20.0
[   659.418]    X.Org Server Extension : 8.0
[   659.418] (II) xfree86: Adding drm device (/dev/dri/card0)
[   659.420] (--) PCI:*(0:1:0:0) 10de:1200:1462:2601 rev 161, Mem @ 0xf4000000/33554432, 0xe0000000/134217728, 0xe8000000/67108864, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[   659.420] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   659.421] Initializing built-in extension Generic Event Extension
[   659.421] Initializing built-in extension SHAPE
[   659.421] Initializing built-in extension MIT-SHM
[   659.421] Initializing built-in extension XInputExtension
[   659.421] Initializing built-in extension XTEST
[   659.421] Initializing built-in extension BIG-REQUESTS
[   659.422] Initializing built-in extension SYNC
[   659.422] Initializing built-in extension XKEYBOARD
[   659.422] Initializing built-in extension XC-MISC
[   659.422] Initializing built-in extension SECURITY
[   659.422] Initializing built-in extension XINERAMA
[   659.422] Initializing built-in extension XFIXES
[   659.422] Initializing built-in extension RENDER
[   659.423] Initializing built-in extension RANDR
[   659.423] Initializing built-in extension COMPOSITE
[   659.423] Initializing built-in extension DAMAGE
[   659.423] Initializing built-in extension MIT-SCREEN-SAVER
[   659.423] Initializing built-in extension DOUBLE-BUFFER
[   659.423] Initializing built-in extension RECORD
[   659.424] Initializing built-in extension DPMS
[   659.424] Initializing built-in extension Present
[   659.424] Initializing built-in extension DRI3
[   659.424] Initializing built-in extension X-Resource
[   659.424] Initializing built-in extension XVideo
[   659.424] Initializing built-in extension XVideo-MotionCompensation
[   659.425] Initializing built-in extension XFree86-VidModeExtension
[   659.425] Initializing built-in extension XFree86-DGA
[   659.425] Initializing built-in extension XFree86-DRI
[   659.425] Initializing built-in extension DRI2
[   659.425] (II) LoadModule: "glx"
[   659.427] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   659.516] (II) Module glx: vendor="NVIDIA Corporation"
[   659.516]    compiled for 4.0.2, module version = 1.0.0
[   659.516]    Module class: X.Org Server Extension
[   659.516] (II) NVIDIA GLX Module  331.49  Wed Feb 12 20:17:10 PST 2014
[   659.517] Loading extension GLX
[   659.517] (II) LoadModule: "nvidia"
[   659.517] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   659.524] (II) Module nvidia: vendor="NVIDIA Corporation"
[   659.524]    compiled for 4.0.2, module version = 1.0.0
[   659.524]    Module class: X.Org Video Driver
[   659.524] (II) NVIDIA dlloader X Driver  331.49  Wed Feb 12 19:57:36 PST 2014
[   659.524] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   659.525] (--) using VT number 2

[   659.529] (II) Loading sub module "fb"
[   659.529] (II) LoadModule: "fb"
[   659.529] (II) Loading /usr/lib/xorg/modules/libfb.so
[   659.530] (II) Module fb: vendor="X.Org Foundation"
[   659.530]    compiled for 1.15.0, module version = 1.0.0
[   659.530]    ABI class: X.Org ANSI C Emulation, version 0.4
[   659.530] (WW) Unresolved symbol: fbGetGCPrivateKey
[   659.530] (II) Loading sub module "wfb"
[   659.530] (II) LoadModule: "wfb"
[   659.531] (II) Loading /usr/lib/xorg/modules/libwfb.so
[   659.532] (II) Module wfb: vendor="X.Org Foundation"
[   659.532]    compiled for 1.15.0, module version = 1.0.0
[   659.532]    ABI class: X.Org ANSI C Emulation, version 0.4
[   659.532] (II) Loading sub module "ramdac"
[   659.532] (II) LoadModule: "ramdac"
[   659.532] (II) Module "ramdac" already built-in
[   659.533] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[   659.533] (==) NVIDIA(0): RGB weight 888
[   659.533] (==) NVIDIA(0): Default visual is TrueColor
[   659.533] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[   659.534] (**) NVIDIA(0): Option "Stereo" "0"
[   659.534] (**) NVIDIA(0): Option "SLI" "Off"
[   659.534] (**) NVIDIA(0): Option "MultiGPU" "Off"
[   659.534] (**) NVIDIA(0): Option "BaseMosaic" "off"
[   659.534] (**) NVIDIA(0): Stereo disabled by request
[   659.534] (**) NVIDIA(0): NVIDIA SLI disabled.
[   659.534] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[   659.534] (**) NVIDIA(0): Option "MetaModes" "DVI-I-2: nvidia-auto-select +1920+0, HDMI-0: nvidia-auto-select +0+0"
[   659.534] (**) NVIDIA(0): Enabling 2D acceleration
[   660.152] (II) NVIDIA(0): Display (Medion MD 20165 (DFP-0)) does not support NVIDIA 3D
[   660.152] (II) NVIDIA(0):     Vision stereo.
[   660.182] (II) NVIDIA(0): Display (Samsung SMS22A350H (DFP-1)) does not support NVIDIA
[   660.182] (II) NVIDIA(0):     3D Vision stereo.
[   660.182] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[   660.182] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 Ti (GF114) at PCI:1:0:0 (GPU-0)
[   660.182] (--) NVIDIA(0): Memory: 1048576 kBytes
[   660.182] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
[   660.182] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[   660.183] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 Ti at PCI:1:0:0
[   660.183] (--) NVIDIA(0):     CRT-0
[   660.183] (--) NVIDIA(0):     CRT-1
[   660.183] (--) NVIDIA(0):     Medion MD 20165 (DFP-0) (boot, connected)
[   660.183] (--) NVIDIA(0):     Samsung SMS22A350H (DFP-1) (connected)
[   660.183] (--) NVIDIA(0):     DFP-2
[   660.183] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[   660.183] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
[   660.183] (--) NVIDIA(0): Medion MD 20165 (DFP-0): Internal Dual Link TMDS
[   660.183] (--) NVIDIA(0): Medion MD 20165 (DFP-0): 330.0 MHz maximum pixel clock
[   660.183] (--) NVIDIA(0): Samsung SMS22A350H (DFP-1): Internal Single Link TMDS
[   660.183] (--) NVIDIA(0): Samsung SMS22A350H (DFP-1): 165.0 MHz maximum pixel clock
[   660.183] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS
[   660.183] (--) NVIDIA(0): DFP-2: 330.0 MHz maximum pixel clock
[   660.183] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[   660.183] (**) NVIDIA(0):     device Medion MD 20165 (DFP-0) (Using EDID frequencies has
[   660.183] (**) NVIDIA(0):     been enabled on all display devices.)
[   660.184] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[   660.184] (**) NVIDIA(0):     device Samsung SMS22A350H (DFP-1) (Using EDID frequencies
[   660.184] (**) NVIDIA(0):     has been enabled on all display devices.)
[   660.184] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS22A350H (DFP-1) contradicts itself:
[   660.184] (WW) NVIDIA(GPU-0):     mode "1920x1080" is specified in the EDID; however, the
[   660.184] (WW) NVIDIA(GPU-0):     EDID's valid HorizSync range (31.000-81.000 kHz) would
[   660.184] (WW) NVIDIA(GPU-0):     exclude this mode's HorizSync (28.1 kHz); ignoring
[   660.184] (WW) NVIDIA(GPU-0):     HorizSync check for mode "1920x1080".
[   660.185] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS22A350H (DFP-1) contradicts itself:
[   660.185] (WW) NVIDIA(GPU-0):     mode "1920x1080" is specified in the EDID; however, the
[   660.185] (WW) NVIDIA(GPU-0):     EDID's valid HorizSync range (31.000-81.000 kHz) would
[   660.185] (WW) NVIDIA(GPU-0):     exclude this mode's HorizSync (28.1 kHz); ignoring
[   660.185] (WW) NVIDIA(GPU-0):     HorizSync check for mode "1920x1080".
[   660.186] (II) NVIDIA(0): Validated MetaModes:
[   660.186] (II) NVIDIA(0):
[   660.186] (II) NVIDIA(0):     "DVI-I-2:nvidia-auto-select+1920+0,HDMI-0:nvidia-auto-select+0+0"
[   660.186] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
[   660.210] (--) NVIDIA(0): DPI set to (101, 97); computed from "UseEdidDpi" X config
[   660.210] (--) NVIDIA(0):     option
[   660.210] (--) Depth 24 pixmap format is 32 bpp
[   660.210] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[   660.210] (II) NVIDIA:     access.
[   660.212] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[   660.212] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[   660.212] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[   660.212] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[   660.212] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[   660.212] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   660.212] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[   660.212] (II) NVIDIA(0):     Config Options in the README.
[   660.213] (II) NVIDIA(0): Setting mode "DVI-I-2:nvidia-auto-select+1920+0,HDMI-0:nvidia-auto-select+0+0"
[   660.346] Loading extension NV-GLX
[   660.436] (==) NVIDIA(0): Disabling shared memory pixmaps
[   660.436] (==) NVIDIA(0): Backing store enabled
[   660.436] (==) NVIDIA(0): Silken mouse enabled
[   660.436] (**) NVIDIA(0): DPMS enabled
[   660.437] Loading extension NV-CONTROL
[   660.437] Loading extension XINERAMA
[   660.437] (II) Loading sub module "dri2"
[   660.437] (II) LoadModule: "dri2"
[   660.437] (II) Module "dri2" already built-in
[   660.437] (II) NVIDIA(0): [DRI2] Setup complete
[   660.437] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   660.437] (--) RandR disabled
[   660.440] (II) Initializing extension GLX
[   660.477] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[   660.477] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   660.477] (**) Power Button: Applying InputClass "system-keyboard"
[   660.477] (II) LoadModule: "evdev"
[   660.477] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[   660.478] (II) Module evdev: vendor="X.Org Foundation"
[   660.478]    compiled for 1.15.0, module version = 2.8.2
[   660.478]    Module class: X.Org XInput Driver
[   660.478]    ABI class: X.Org XInput driver, version 20.0
[   660.478] (II) Using input driver 'evdev' for 'Power Button'
[   660.478] (**) Power Button: always reports core events
[   660.478] (**) evdev: Power Button: Device: "/dev/input/event3"
[   660.478] (--) evdev: Power Button: Vendor 0 Product 0x1
[   660.478] (--) evdev: Power Button: Found keys
[   660.478] (II) evdev: Power Button: Configuring as keyboard
[   660.478] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[   660.478] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   660.478] (**) Option "xkb_rules" "evdev"
[   660.478] (**) Option "xkb_model" "pc104"
[   660.478] (**) Option "xkb_layout" "de"
[   660.490] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[   660.490] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   660.490] (**) Power Button: Applying InputClass "system-keyboard"
[   660.490] (II) Using input driver 'evdev' for 'Power Button'
[   660.490] (**) Power Button: always reports core events
[   660.490] (**) evdev: Power Button: Device: "/dev/input/event2"
[   660.490] (--) evdev: Power Button: Vendor 0 Product 0x1
[   660.490] (--) evdev: Power Button: Found keys
[   660.490] (II) evdev: Power Button: Configuring as keyboard
[   660.490] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event2"
[   660.490] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[   660.490] (**) Option "xkb_rules" "evdev"
[   660.490] (**) Option "xkb_model" "pc104"
[   660.490] (**) Option "xkb_layout" "de"
[   660.490] (II) config/udev: Adding drm device (/dev/dri/card0)
[   660.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[   660.490] (II) No input driver specified, ignoring this device.
[   660.490] (II) This device may have been added with another device file.
[   660.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
[   660.490] (II) No input driver specified, ignoring this device.
[   660.490] (II) This device may have been added with another device file.
[   660.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
[   660.490] (II) No input driver specified, ignoring this device.
[   660.490] (II) This device may have been added with another device file.
[   660.490] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event15)
[   660.490] (II) No input driver specified, ignoring this device.
[   660.490] (II) This device may have been added with another device file.
[   660.490] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event11)
[   660.490] (II) No input driver specified, ignoring this device.
[   660.490] (II) This device may have been added with another device file.
[   660.490] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
[   660.490] (II) No input driver specified, ignoring this device.
[   660.490] (II) This device may have been added with another device file.
[   660.490] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event9)
[   660.490] (II) No input driver specified, ignoring this device.
[   660.490] (II) This device may have been added with another device file.
[   660.491] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event8)
[   660.491] (II) No input driver specified, ignoring this device.
[   660.491] (II) This device may have been added with another device file.
[   660.491] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event7)
[   660.491] (II) No input driver specified, ignoring this device.
[   660.491] (II) This device may have been added with another device file.
[   660.491] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event14)
[   660.491] (II) No input driver specified, ignoring this device.
[   660.491] (II) This device may have been added with another device file.
[   660.491] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event13)
[   660.491] (II) No input driver specified, ignoring this device.
[   660.491] (II) This device may have been added with another device file.
[   660.491] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event12)
[   660.491] (II) No input driver specified, ignoring this device.
[   660.491] (II) This device may have been added with another device file.
[   660.491] (II) config/udev: Adding input device Burr-Brown from TI               USB Audio CODEC  (/dev/input/event1)
[   660.491] (**) Burr-Brown from TI               USB Audio CODEC : Applying InputClass "evdev keyboard catchall"
[   660.491] (**) Burr-Brown from TI               USB Audio CODEC : Applying InputClass "system-keyboard"
[   660.491] (II) Using input driver 'evdev' for 'Burr-Brown from TI               USB Audio CODEC '
[   660.491] (**) Burr-Brown from TI               USB Audio CODEC : always reports core events
[   660.491] (**) evdev: Burr-Brown from TI               USB Audio CODEC : Device: "/dev/input/event1"
[   660.491] (--) evdev: Burr-Brown from TI               USB Audio CODEC : Vendor 0x8bb Product 0x2902
[   660.491] (--) evdev: Burr-Brown from TI               USB Audio CODEC : Found keys
[   660.491] (II) evdev: Burr-Brown from TI               USB Audio CODEC : Configuring as keyboard
[   660.491] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/usb2/2-2/2-2:1.3/input/input1/event1"
[   660.491] (II) XINPUT: Adding extended input device "Burr-Brown from TI               USB Audio CODEC " (type: KEYBOARD, id 8)
[   660.491] (**) Option "xkb_rules" "evdev"
[   660.491] (**) Option "xkb_model" "pc104"
[   660.491] (**) Option "xkb_layout" "de"
[   660.491] (II) config/udev: Adding input device Logitech G400s Optical Gaming Mouse (/dev/input/event6)
[   660.491] (**) Logitech G400s Optical Gaming Mouse: Applying InputClass "evdev pointer catchall"
[   660.491] (II) Using input driver 'evdev' for 'Logitech G400s Optical Gaming Mouse'
[   660.491] (**) Logitech G400s Optical Gaming Mouse: always reports core events
[   660.491] (**) evdev: Logitech G400s Optical Gaming Mouse: Device: "/dev/input/event6"
[   660.491] (--) evdev: Logitech G400s Optical Gaming Mouse: Vendor 0x46d Product 0xc24c
[   660.491] (--) evdev: Logitech G400s Optical Gaming Mouse: Found 12 mouse buttons
[   660.491] (--) evdev: Logitech G400s Optical Gaming Mouse: Found scroll wheel(s)
[   660.491] (--) evdev: Logitech G400s Optical Gaming Mouse: Found relative axes
[   660.491] (--) evdev: Logitech G400s Optical Gaming Mouse: Found x and y relative axes
[   660.491] (II) evdev: Logitech G400s Optical Gaming Mouse: Configuring as mouse
[   660.491] (II) evdev: Logitech G400s Optical Gaming Mouse: Adding scrollwheel support
[   660.491] (**) evdev: Logitech G400s Optical Gaming Mouse: YAxisMapping: buttons 4 and 5
[   660.491] (**) evdev: Logitech G400s Optical Gaming Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   660.491] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/input/input6/event6"
[   660.491] (II) XINPUT: Adding extended input device "Logitech G400s Optical Gaming Mouse" (type: MOUSE, id 9)
[   660.491] (II) evdev: Logitech G400s Optical Gaming Mouse: initialized for relative axes.
[   660.491] (**) Logitech G400s Optical Gaming Mouse: (accel) keeping acceleration scheme 1
[   660.491] (**) Logitech G400s Optical Gaming Mouse: (accel) acceleration profile 0
[   660.491] (**) Logitech G400s Optical Gaming Mouse: (accel) acceleration factor: 2.000
[   660.491] (**) Logitech G400s Optical Gaming Mouse: (accel) acceleration threshold: 4
[   660.492] (II) config/udev: Adding input device Logitech G400s Optical Gaming Mouse (/dev/input/mouse0)
[   660.492] (II) No input driver specified, ignoring this device.
[   660.492] (II) This device may have been added with another device file.
[   660.492] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event5)
[   660.492] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[   660.492] (**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
[   660.492] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[   660.492] (**) Eee PC WMI hotkeys: always reports core events
[   660.492] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event5"
[   660.492] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[   660.492] (--) evdev: Eee PC WMI hotkeys: Found keys
[   660.492] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[   660.492] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input5/event5"
[   660.492] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 10)
[   660.492] (**) Option "xkb_rules" "evdev"
[   660.492] (**) Option "xkb_model" "pc104"
[   660.492] (**) Option "xkb_layout" "de"
[   660.492] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[   660.492] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[   660.492] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[   660.492] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[   660.492] (**) AT Translated Set 2 keyboard: always reports core events
[   660.492] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[   660.492] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[   660.492] (--) evdev: AT Translated Set 2 keyboard: Found keys
[   660.492] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[   660.492] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[   660.492] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[   660.492] (**) Option "xkb_rules" "evdev"
[   660.492] (**) Option "xkb_model" "pc104"
[   660.492] (**) Option "xkb_layout" "de"
[   660.492] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[   660.492] (II) No input driver specified, ignoring this device.
[   660.492] (II) This device may have been added with another device file.
[   745.120] (II) evdev: AT Translated Set 2 keyboard: Close
[   745.120] (II) UnloadModule: "evdev"
[   745.120] (II) evdev: Eee PC WMI hotkeys: Close
[   745.120] (II) UnloadModule: "evdev"
[   745.120] (II) evdev: Logitech G400s Optical Gaming Mouse: Close
[   745.120] (II) UnloadModule: "evdev"
[   745.120] (II) evdev: Burr-Brown from TI               USB Audio CODEC : Close
[   745.120] (II) UnloadModule: "evdev"
[   745.120] (II) evdev: Power Button: Close
[   745.120] (II) UnloadModule: "evdev"
[   745.120] (II) evdev: Power Button: Close
[   745.120] (II) UnloadModule: "evdev"
[   745.383] (II) NVIDIA(GPU-0): Deleting GPU-0
[   745.387] (EE) Server terminated successfully (0). Closing log file.
[root@arch log]#





I noticed that i didnt set any permissions on the directories that i created manually after restoring. The permissions on /tmp were 755. I used chmod 1777 on /tmp but I dont get drwxrwxrwxt but this:



[root@arch /]# ls -la
insgesamt 1925513
drwxr-xr-x  16 root root       4096 28. Feb 17:26 .
drwxr-xr-x  16 root root       4096 28. Feb 17:26 ..
-rw-r--r--   1 root root 1971678005 28. Feb 17:23 20feb2014.tar.gz
lrwxrwxrwx   1 root root          7 31. Mai 2013  bin -> usr/bin
drwxr-xr-x   4 root root       1024 28. Feb 17:36 boot
drwxr-xr-x  19 root root       3200 28. Feb 22:40 dev
drwxr-xr-x  59 root root       4096 28. Feb 17:36 etc
drwxr-xr-x   3 root root       4096  9. Feb 00:47 home
lrwxrwxrwx   1 root root          7 31. Mai 2013  lib -> usr/lib
lrwxrwxrwx   1 root root          7 31. Mai 2013  lib64 -> usr/lib
drwxr-xr-x   2 root root       4096 28. Feb 17:26 mnt
drwxr-xr-x   3 root root       4096  9. Feb 01:15 opt
dr-xr-xr-x 107 root root          0 28. Feb 22:29 proc
drwxr-x---   7 root root       4096 19. Feb 18:24 root
drwxr-xr-x  16 root root        400 28. Feb 22:29 run
lrwxrwxrwx   1 root root          7 31. Mai 2013  sbin -> usr/bin
drwxr-xr-x   4 root root       4096 31. Mai 2013  srv
dr-xr-xr-x  13 root root          0 28. Feb 22:29 sys
drwsrwsrwx   9 root root        180 28. Feb 22:44 tmp
drwxr-xr-x   8 root root       4096  8. Feb 23:31 usr
drwxr-xr-x  12 root root       4096 28. Feb 17:28 var

Last edited by schnip_schnap (2014-03-02 20:34:42)

Offline

#4 2014-02-28 23:06:28

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,280

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

That all looks pretty normal.  I was looking for a volume that had been identified by UUID that is not being located.  If you had used UUID, the rebuilt disk would not show up as it would have a different ID.    I think you are are on the right track looking at permissions.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2014-03-01 00:01:33

schnip_schnap
Member
Registered: 2014-02-28
Posts: 6

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

Well after reformatting my root fs i put the new UUID in syslinux.cfg and in the fstab so thats not the problem. I mean the system boots successfully which means that partitions are properly recognized.


I really dont have much knowledge about these kind of issues but i had to deal with a similar situation when i had wrong permissions on a user's home directory. Some things didnt just throw an error but rather were delayed and wonky.


In this case it is important that i recover the directories excluded from the tar backup exactly as they were before. To me it seems as if they are just as they were before. Can you confirm that?


PS: I rebooted and the permissions on /tmp look ok now.

Offline

#6 2014-03-02 17:52:25

schnip_schnap
Member
Registered: 2014-02-28
Posts: 6

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

Hey Guys,


after restoring a complete tar system backup (excluding, /mnt,/run,/proc,/sys,/dev,/tmp,/lost+found) i have run into this problem when trying to login via tty:


Complete journal for boot:

http://pastebin.com/XyBdTb0U



Interesting part:

http://pastebin.com/Sz5u1N84


The systems seems usable (after the login delay) and X seems to start fine (according to the log file) But i only get a black screen when i use startx. Could it be that excluding all the paths
( /mnt,/run,/proc,/sys,/dev,/tmp,/lost+found) was too much? I recreated them with the proper permissions after restoring the backup.(bootable usbstick) I thought nothing of these directories should be in the backup as they are virtual file systems, am i right?


This part causes a massive delay of 16 seconds after hitting enter to login:

Mär 02 18:29:08 arch login[259]: pam_unix(login:session): session opened for user root by (uid=0)
Mär 02 18:29:08 arch dbus[257]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Mär 02 18:29:24 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out

Then this happens (Failed to create session and root logs in anyways):


Mär 02 18:29:24 arch dbus[257]: [system] Successfully activated service 'org.freedesktop.login1'
Mär 02 18:29:24 arch systemd-logind[256]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
Mär 02 18:29:24 arch systemd-logind[256]: Watching system buttons on /dev/input/event3 (Power Button)
Mär 02 18:29:24 arch systemd-logind[256]: Watching system buttons on /dev/input/event2 (Power Button)
Mär 02 18:29:24 arch systemd-logind[256]: New seat seat0.
Mär 02 18:29:33 arch login[259]: pam_systemd(login:session): Failed to create session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:29:33 arch login[259]: ROOT LOGIN ON tty1

Some more failures afterwards:


Mär 02 18:29:49 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mär 02 18:29:49 arch systemd-logind[256]: Failed to start unit user-0.slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:29:49 arch systemd-logind[256]: Failed to start user slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:30:14 arch systemd-logind[256]: Failed to start unit user@0.service: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:30:14 arch systemd-logind[256]: Failed to start user service: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mär 02 18:30:14 arch systemd-logind[256]: Assertion 's->user->slice' failed at src/login/logind-session.c:502, function session_start_scope(). Aborting.
Mär 02 18:30:14 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mär 02 18:30:15 arch systemd-coredump[360]: Process 256 (systemd-logind) dumped core.
Mär 02 18:30:15 arch systemd[1]: systemd-logind.service: main process exited, code=dumped, status=6/ABRT
Mär 02 18:30:15 arch systemd[1]: Failed to start Login Service.

Last edited by schnip_schnap (2014-03-02 18:04:30)

Offline

#7 2014-03-02 18:15:16

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,280

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

Merged your new thread with this one.  I see no reason to have started a new thread.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#8 2014-03-03 11:12:46

schnip_schnap
Member
Registered: 2014-02-28
Posts: 6

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

ok i actually made some progress. The problem with the X Server was apparently a problem with the /tmp directory. The thing i did was just remove /dev /run /proc /tmp /sys with a live usb stick and reboot the system. The virtual file systems get mounted anyhow and everything works now except for the login delay. This delay is caused by this:


Mär 02 18:29:08 arch login[259]: pam_unix(login:session): session opened for user root by (uid=0)
Mär 02 18:29:08 arch dbus[257]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Mär 02 18:29:24 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out

im not a 100% sure what that means but i guess dbus is trying to make systemd give the login daemon a session or something like that which fails because systemd does not respond.

Offline

#9 2014-03-05 13:37:53

schnip_schnap
Member
Registered: 2014-02-28
Posts: 6

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

Can no one point me in the right direction? I mean "org.freedesktop.systemd1 timed out" is a pretty clear error isnt it? How could one debug that?

Offline

#10 2014-03-19 06:28:34

mauriciootta
Member
Registered: 2012-04-05
Posts: 9

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

I just started having the same issue. I use ZFS, so the file system itself is probably not the culprit

[root@brain ~]# cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
UUID=784c7f67-0c2b-41e4-b732-45b46e8f9f4f       /boot           ext4            rw,relatime,stripe=4,data=ordered     0 2
/dev/zvol/unsafepool/swap       none swap defaults 0 0

my pools are fine:
# zpool status
  pool: brainpool
state: ONLINE
  scan: scrub repaired 0 in 3h32m with 0 errors on Fri Mar 14 23:02:48 2014
config:

        NAME                                                STATE     READ WRITE CKSUM
        brainpool                                           ONLINE       0     0     0
          raidz1-0                                          ONLINE       0     0     0
            ata-WDC_WD20EFRX-68AX9N0_WD-WMC301692156-part3  ONLINE       0     0     0
            ata-WDC_WD20EFRX-68AX9N0_WD-WMC1T3209660-part3  ONLINE       0     0     0

errors: No known data errors

  pool: unsafepool
state: ONLINE
  scan: scrub repaired 0 in 3h21m with 0 errors on Mon Mar 17 01:34:13 2014
config:

        NAME                               STATE     READ WRITE CKSUM
        unsafepool                         ONLINE       0     0     0
          ata-ST2000DM001-1CH164_Z1E47MBG  ONLINE       0     0     0
          ata-ST2000DM001-9YN164_S1E0MC70  ONLINE       0     0     0

errors: No known data errors



mount looks ok
# mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8059592k,nr_inodes=2014898,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
brainpool on / type zfs (rw,relatime,xattr)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
configfs on /sys/kernel/config type configfs (rw,relatime)
unsafepool/home on /home type zfs (rw,relatime,xattr)
unsafepool/tmp on /tmp type zfs (rw,relatime,xattr)
unsafepool on /unsafepool type zfs (rw,relatime,xattr)
/dev/md127 on /boot type ext4 (rw,relatime,stripe=4,data=ordered)



/tmp looks right, I think:

# ls -la /tmp
total 4464
drwxrwxrwt 32 root          root          56 Mar 18 20:46 .
drwxr-xr-x 22 root          root          26 Aug 22  2013 ..




[root@brain ~]# systemctl restart nginx
Failed to restart nginx.service: Activation of org.freedesktop.systemd1 timed out
[root@brain ~]# systemctl restart postgresql
Failed to restart postgresql.service: Connection timed out
[root@brain ~]#



were you able to find any pointer?

Offline

#11 2014-03-19 06:52:42

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

When posting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode

like this

It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Offline

#12 2014-03-19 14:46:05

earthrise
Member
Registered: 2013-10-05
Posts: 1

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

I am seeing this too.

# shutdown -h now
Failed to start poweroff.target: Activation of org.freedesktop.systemd1 timed out
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
# shutdown -h now
Failed to start poweroff.target: Connection timed out
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

I just upgraded and haven't rebooted yet, though, so it could be that.

Edit: Everything seems fine after rebooting (I had to use reboot -f). If I remember correctly, I saw this message a few days ago too when I was trying to use TeamViewer.

Last edited by earthrise (2014-03-19 15:00:40)

Offline

#13 2014-05-04 16:35:03

ikwyl6
Member
Registered: 2014-05-02
Posts: 3

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

Running raspberry pi (Rpi), I also had same reboot issues as earthrise above when trying to use

shutdown -r now

or

systemctl reboot

I would get:

$ sudo shutdown -r now
Failed to start reboot.target: Activation of org.freedesktop.systemd1 timed out
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

And it wouldn't reboot. My arch linux is up-to-date using systemctl -Syu.

Kernel is:

$ uname -a
Linux alarmpi 3.10.37-1-ARCH #1 PREEMPT Wed Apr 16 01:51:34 MDT 2014 armv6l GNU/Linux

Trying to figure out what was going on, I would just type

$ systemctl
Failed to list units: Connection timed out

OR running

$ systemctl list-units
Failed to list units: Connection timed out

would throw those errors.

Doing a "reboot -f" actually made the rpi reboot. I could then run systemctl by itself. Not sure what happened!

Offline

#14 2019-01-30 04:45:41

kamysheblid
Member
Registered: 2019-01-30
Posts: 1

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

I think I figured out the problem with the long delay for using sudo.
I had to enable a service called nscd.

The strace of pam_timestamp_check gave me

connect(3, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)

I looked at my init.d (I'm using parabola, a type of arch which uses openrc instead of systemd) folder and noticed nscd is a service and that it wasn't set to startup. As soon as I enabled it the problem went away. I have no delay when using sudo.

Offline

#15 2019-01-30 08:03:20

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 10,014

Re: Failed to activate service 'org.freedesktop.systemd1': timed out

This thread is 4 years old, it doesn't look like what you are seeing is of any relevance to the original thread. Please pay attention to the dates, and don't necrobump.

Closing.

Offline

Board footer

Powered by FluxBB