Project

General

Profile

Bug #2027

installing time-slider does not force re-read of dbus configuration files

Added by Jan Owoc over 7 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2012-01-24
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

Steps to reproduce:

1. Install oi151a text. Reboot.

2. Login. Run:

# pkg install time-slider
# svcadm enable -r time-slider

3. Obtain error. Time-slider put in "maintenance" mode. This is caused by the default security settings in dbus not allowing time-slider to configure itself.

Workaround:
After installing time-slider, restart the dbus service (or reboot the computer).

Proposed solution:
Include a service dependency in the SMF manifest to force a restart of dbus after a successful install of time-slider.

History

#1

Updated by Ken Mays over 6 years ago

  • Assignee set to OI JDS
#2

Updated by Ken Mays over 6 years ago

  • Status changed from New to Closed
  • Assignee changed from OI JDS to Ken Mays
  • % Done changed from 0 to 100

Not a bug. Once you install time-slider (>0.2.97), best to reboot system for all services to enable properly.
enable sudo or root privs, then:
$ svcadm enable auto-snapshot:frequent
$ svcadm enable auto-snapshot:hourly
$ svcadm enable auto-snapshot:daily
$ svcadm enable auto-snapshot:weekly
$ svcadm enable auto-snapshot:monthly
$ svcadm enable time-slider/plugin:zfs-send
$ svcadm enable time-slider/plugin:rsync
$ svcadm enable time-slider
$ reboot
$ zfs list -t snapshot

#3

Updated by Jim Klimov over 2 years ago

Hit this (or similar) problem with a recent OI Hipster:

jim@jimoi:~$ svcs -xv
svc:/application/time-slider:default (GNOME Desktop Snapshot Management Service)
 State: maintenance since April  9, 2017 11:11:37 PM CEST
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
   See: http://illumos.org/msg/SMF-8000-KS
   See: man -M /usr/share/man -s 1M zfs
   See: /var/svc/log/application-time-slider:default.log
Impact: 5 dependent services are not running:
        svc:/system/filesystem/zfs/auto-snapshot:daily
        svc:/system/filesystem/zfs/auto-snapshot:frequent
        svc:/system/filesystem/zfs/auto-snapshot:hourly
        svc:/system/filesystem/zfs/auto-snapshot:monthly
        svc:/system/filesystem/zfs/auto-snapshot:weekly

jim@jimoi:~$ tail -18 /var/svc/log/application-time-slider:default.log
--------END ERROR MESSAGE--------
[ Apr  9 23:06:07 Stopping because service disabled. ]
[ Apr  9 23:06:07 Executing stop method (:kill). ]
[ Apr  9 23:11:35 Executing start method ("/lib/svc/method/time-slider start"). ]
Traceback (most recent call last):
  File "/usr/lib/time-sliderd", line 10, in <module>
    main(abspath(__file__))
  File "/usr/lib/../share/time-slider/lib/time_slider/timesliderd.py", line 937, in main
    systemBus = dbus.SystemBus()
  File "/usr/lib/python2.7/vendor-packages/dbus/_dbus.py", line 194, in __new__
    private=private)
  File "/usr/lib/python2.7/vendor-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/vendor-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Time Slider failed to start: error 95
[ Apr  9 23:11:37 Method "start" exited with status 95. ]

jim@jimoi:~$ cat /etc/release 
             OpenIndiana Hipster 2016.10 (powered by illumos)
        OpenIndiana Project, part of The Illumos Foundation (C) 2010-2016
                        Use is subject to license terms.
                           Assembled 30 October 2016

jim@jimoi:~$ uname -a
SunOS jimoi 5.11 illumos-152e375 i86pc i386 i86pc Solaris

Time-slider package version is:

pkg://openindiana.org/desktop/time-slider@0.2.101-2016.0.1.107:20161018T160201Z

And it just declares no dependency on DBus (shouldn't it? or would that deadlock somehow?), which started after time-slider had already failed :

jim@jimoi:~$ svcs -d time-slider
STATE          STIME    FMRI
online         23:11:35 svc:/milestone/multi-user:default

jim@jimoi:~$ svcs dbus time-slider
STATE          STIME    FMRI
online         23:11:47 svc:/system/dbus:default
maintenance    23:11:37 svc:/application/time-slider:default

And now it is just restartable to fix:

jim@jimoi:~$ sudo svcadm clear time-slider

jim@jimoi:~$ svcs dbus time-slider
STATE          STIME    FMRI
online         23:11:47 svc:/system/dbus:default
online         23:30:14 svc:/application/time-slider:default

Also available in: Atom PDF