Thought I would just send an update on this. Thanks for the all the
To get around our particular issue I just added some retry logic to the
/etc/init.d/ script. When it runs it if finds that the operation has failed
it pauses for a second and will try again. It will try up to three times
before giving up.
Running more tests we were able to see that on some occasions it still
fails on the first attempt but so far has always been successful on the 2nd.
On Thu, Dec 1, 2011 at 3:37 PM, Ian Collins <i...@ianshome.com> wrote:
> On 12/ 2/11 10:30 AM, Derek McEachern wrote:
>> On Thu, Dec 1, 2011 at 2:48 PM, Ian Collins <i...@ianshome.com <mailto:
>> i...@ianshome.com>> wrote:
>> On 12/ 2/11 05:39 AM, Derek McEachern wrote:
>> Have a peculiar problem that I haven't seen before.
>> When starting a system that has about 35 - 40 zones on it
>> occasionally we see that one of the zones doesn't come up
>> properly. You can log into the zone but none of the /etc/rc3.d
>> scripts have been run.
>> The same zone, or a random one?
>> What happens if you halt one or more zones before rebooting? Is
>> there a threshold where the problem begins to occur?
>> Random zone.
>> We've been testing to see if there is a threshold of trying to start too
>> many in parallel but so far we don't see anything.
>> We saw the problem trying to start 3 zones in parallel but it was very
>> intermittent. Like 1 out of every 4 tries at started all 40 zones we would
>> see 1 failure. We ran some tests starting 10 zones in parallel and so far
>> no errors. Our assumption was that if it was load related moving from 3 to
>> 10 zones we would see problems.
>> I have several systems that start 10 or more zones and I've never seen
> any problems.
> I agree with the comment elsewhere that you should be using SMF rather
> than rc scripts to start services.
> It is also possible to create SMF services with the appropriate
> dependencies to start your zones in the correct order.
zones-discuss mailing list