Tim, thanks for the reply. I looked at /var/adm/messages and this is what I found
Apr 13 00:00:21 fortress zfs-auto-snap: [ID 702911 daemon.notice] Error: Unable to take recursive snapshots of datap...@zfs-auto-snap:daily-2010-04-13-00:00. Apr 13 00:00:21 fortress zfs-auto-snap: [ID 702911 daemon.notice] Moving service svc:/system/filesystem/zfs/auto-snapshot:daily to maintenance mode. Apr 13 00:00:32 fortress svc.startd[7]: [ID 748625 daemon.error] system/filesystem/zfs/auto-snapshot:daily transitioned to maintenance by request (see 'svcs -xv' for deta ils) It seems it was not able to take a recursive snapshot of datap...@zfs-auto-snap:daily-2010-04-13-00:00 and dropped down to maintenance. Would it be possible to find more information about why it was unable to do that? I was not aware of 'svcadm mark..', which is nice. On Apr 14, 2010, at 8:36 AM, Tim Foster wrote: > On Wed, 2010-04-14 at 08:28 -0700, melbogia wrote: >> Hello, >> Yesterday the zfs/auto-snapshot:daily service went into maintenance >> mode and I am trying to figure out why. This is what I see but nothing >> explains why it went into maintenance mode. > > There's a bunch of reasons why we can drop to maintenance. The service > should have logged the reason to syslog (/var/adm/messages) though. > > Apart from during service start/stop, at the moment the auto-snapshot > jobs run from a cron job as a non-root user, and as such, can't write to > the SMF logs. > > It would be nice to be able to provide a message along with the call to > 'svcadm mark maintenance <instance>' to explain why we're dropping the > service to maintenance. > >> I tried disabling and enabling the service and it came back up. But why did >> it went down? > > There should be info in syslog. > > cheers, > tim > _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
