[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd I/O error :-(



On Friday 01 July 2016 16:12:39 Michael Biebl wrote:
> Am 30.06.2016 um 17:25 schrieb Lisi Reisz:
> > [24772.681833] systemd-logind[21814]: Failed to enable subscription:
> > Launch helper exited with unknown return code 1
> > [24772.681890] systemd-logind[21814]: Failed to fully start up daemon:
> > Input/output errror
>
> Could you post the output of
> systemctl status dbus.service dbus.socket

sarah@debian-wheezy:~$ systemctl status dbus.service dbus.socket
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static)
   Active: active (running) since Fri 2016-07-01 16:23:33 BST; 33min ago
     Docs: man:dbus-daemon(1)
 Main PID: 1254 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           
├─1254 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --sys...
           └─2036 /opt/trinity/bin/tde_dbus_hardwarecontrol

● dbus.socket - D-Bus System Message Bus Socket
   Loaded: loaded (/lib/systemd/system/dbus.socket; static)
   Active: active (running) since Fri 2016-07-01 16:23:33 BST; 33min ago
   Listen: /var/run/dbus/system_bus_socket (Stream)
sarah@debian-wheezy:~$ 

> systemctl status systemd-logind.service

sarah@debian-wheezy:~$ systemctl status systemd-logind.service
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
   Active: active (running) since Fri 2016-07-01 16:23:38 BST; 34min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 1246 (systemd-logind)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-logind.service
           └─1246 /lib/systemd/systemd-logind
sarah@debian-wheezy:~$  

> What version of dbus 
1.8.20-0+deb8u1

> and systemd do you have installed? 
215-17+deb8u4

Thanks, Michael.  Though that problem does seem to have settled down a bit 
over a few reboots and a cooling off period over night.

Lisi


Reply to: