[OpenIndiana-discuss] SMF retries count

[Michael Stapleton]

Could these be of use?


startd/critical_failure_count
startd/critical_failure_period

         The critical_failure_count  and  critical_failure_period
         properties  together  specify the maximum number of ser-
         vice failures allowed in a given  time  interval  before
         svc.startd  transitions  the service to maintenance.  If
         the number of failures exceeds critical_failure_count in
         any    period    of   critical_failure_period   seconds,
         svc.startd will transition the service to maintenance.



Mike

On Tue, 2013-03-26 at 15:52 +0100, Jim Klimov wrote:

> On 2013-03-26 14:44, Michael Stapleton wrote:
> > There are a number of environmental variables used by asadmin, but I did
> > not find anything that looked promising.
> >
> > As a last resort hack, you could you wrap the asadmin command in a
> > script.
> 
> I thought of changing the SMF method to something like
>    "while ! asadmin ... ; do sleep 1; done"
> (perhaps with my arbitrarily-picked timeout, like running 10 loops
> max), but this would be prone to any number of other unforeseen
> errors causing the failure exit code - and that event should be
> detected/reported rather than ignored in this manner.
> 
> > I would also try to find out why my app takes over 60 seconds to stop.
> > We might be trying to cure the symptom.
> 
> Well, there are no particular errors in the log, just zillions of
> closing, unregistering, unhooking stuff. No erroneous stacktrace,
> no real hiccups like a minute of silence. Simply a lot of work to
> stop the portal properly. That part we don't really find unusual.
> 
> Thanks for commiserating with me on this ;)
> ///Jim
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss