[OpenIndiana-discuss] How to debug recent time-slider failure

[Harry Putnam]

running 151_9 (fairly recent update from 151_a8)
Running oi as  guest of win7 64bit vbox vm

I've been using the time-slider service for a month or two and only
noticed that it had been sidelined to maintenance today.

svcs -xv says since today at 11:07  and not much else, other than
start method failed repeatedly.  The log content says no more either.

svc:/application/time-slider:default (GNOME Desktop Snapshot Management Service)
 State: maintenance since April 16, 2014 11:07:43 AM EDT
Reason: Start method failed repeatedly, last died on Killed (9).
   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

I wouldn't mind if this only meant the gui is what failed but don't
know enough to be able to tell.

Can the service be controlled from the command line? The man page
referenced in the above ouput appears to have nothing whatever to do
with the time-slider.

The log  shows this message repeatedly:

Just todays lines:
[...]
[ Apr 16 11:03:45 Enabled. ]
[ Apr 16 11:04:39 Executing start method ("/lib/svc/method/time-slider start"). ]
[ Apr 16 11:05:41 Method or service exit timed out.  Killing contract 104. ]
[ Apr 16 11:05:41 Method "start" failed due to signal KILL. ]
[ Apr 16 11:05:41 Executing start method ("/lib/svc/method/time-slider start"). ]
[ Apr 16 11:06:42 Method or service exit timed out.  Killing contract 120. ]
[ Apr 16 11:06:42 Method "start" failed due to signal KILL. ]
[ Apr 16 11:06:42 Executing start method ("/lib/svc/method/time-slider start"). ]
[ Apr 16 11:07:43 Method or service exit timed out.  Killing contract 121. ]
[ Apr 16 11:07:43 Method "start" failed due to signal KILL. ]

I guess the start times out and is killed.

The last record of the start ending with exit 0 was:

  [ Apr 13 14:36:50 Method "start" exited with status 0. ]

Its been timeing out since then.

That isn't the date of a hefty update I did... Don't remember when
that was exactly but in Apr single digit days.

Not at all sure where to get somekind of useful debugging info.