Thanks Dave for the suggestions. Bruce
On Nov 13, 2009, at 8:58 AM, Dave Miner wrote: > Bruce Rothermal wrote: >> On first boot by the time I can login network is configured and dns >> is working. At this point the system is preparing to retrieve >> packages from IPS. Failure always occurs after reboot. I also found >> that if I edit the /var/svc/manifest/network/dns/client.xml file >> during initial start, and change the start timeout value from 10 to >> 30 sec's the dns service doesn't fail after reboot. > > OK, since we've determined that your problem is really not part of > AI, but rather the boot after installation, some ideas: > > - Rework your service to deal with networking potentially not being > quite ready yet: have it retry, etc. Networks aren't reliable > anyway (just because we reached a milestone that has everything > configured, there's no guarantee packets get to their destinations) > so this may be beneficial to the product in any case. Transient > services can have effectively infinite timeouts; see smf_method(5). > > - You can interface to NWAM using the scripting it offers, perhaps > having it enable your service only after a network interface is on- > line. See nwamd(1M). A caution there is that NWAM v1 is coming > around build 130 and changes the interfaces. nwam-discuss would be > the place for more help with this. > > - AI will be offering static network configurations in the not-too- > distant future once we finish working out interfaces with the > networking team and get them implemented. Customers of a product > such as yours may rather use that than NWAM, I guess. That doesn't > help you right now, but it could be fairly straightforward for you > to generate an alternate AI installation environment that could set > up some non-NWAM networking for your development environment until > this support arrives. > > Dave > >> Thanks for the attention to this matter. >> Bruce >> On Nov 13, 2009, at 8:02 AM, Dave Miner wrote: >>> Bruce Rothermal wrote: >>>> We tried the delay suggestion and it did not help the problem. If >>>> anything it make it worse because services have a timeout value. >>>> So adding delays takes away time for the service script to >>>> complete its work before hitting timeout value. >>>> Anyway our service requires that network services be up and >>>> working. Our service will continue to fail as long as dns client >>>> service is failed and in maintenance state. dns client service >>>> seems to be failing because it is timing out before nwam >>>> completes bringing up the interface. >>>> Are there any doc's which outline the time line of what >>>> functionality runs during automated install and in what order. >>> >>> Bruce, are the service you're referring to running at first boot >>> after automated installation or are you building a customized AI >>> image with your services inserted somehow? It's not clear from >>> the thread so far. >>> >>> Dave >>> >> ------------------------------------------------------------------------ >> Bruce Rothermal >> Email: bruce.rothermal at sun.com >> Skype: bruce.rothermal >> Google Talk: bruce.rothermal at gmail.com > -------------- next part -------------- A non-text attachment was scrubbed... Name: 1.jpg Type: image/jpeg Size: 3120 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20091113/e587d92c/attachment.jpg> -------------- next part -------------- Bruce Rothermal Email: bruce.rothermal at sun.com Skype: bruce.rothermal Google Talk: bruce.rothermal at gmail.com
