Le 17 f?vr. 08 ? 20:10, Peter Tribble a ?crit : > Running S10, pretty recent, we've noticed the following behaviour: > > The 'svcadm restart' command doesn't always work, and often leaves > our services in maintenance. > > The problem seems to be that a restart does a stop followed by > a start, and if the stop fails (the process doesn't die cleanly, so > then smf comes along and kills the process) then the service is > immediately put into maintenance with (apparently) no attempt > to start it back up.
Well, the concept is to have something you can trust in. How could you trust SMF if it decides by itself to ignore a bad stop ? > In terms of availability, this is the wrong way round, as it has > taken crucial services offline for us (and without any indication to > the user). Without indication ? Is the maintenance state not an indication ? > Why doesn't it try to start the service back up even if the stop > fails? Any service in maintenance state must be cleared (svcs clear) before accept any other action. > Or is there some other way of telling it that it's OK if the stop > method failed? Do you really want to do that ? > (The application is tomcat, which doesn't always shut down > when you ask it to nicely.) I guess smf specialist on this list may provide you a best howto. Anyway, the easiest is to modify the stop method...forcing it to be happy in any circumstance. Nicolas 01010101 01001110 01001001 01011000 Nicolas Dorfsman ndo at unikservice.com http://www.guses.org - French Speaking (Open)Solaris User Group http://www.solaris-fr.org - French OpenSolaris Wiki
