Liane Praza writes:
> Michael Hale wrote:
> > ultimately, once we were able to get in (by booting with milestone=none,
> > we did a
> > svcadm disable svc:/network/initial:default and svcadm milestone=all and
> > then everything started normally.
> >
> > We're still seeing:
> >
> > nis domain name is:
> >
> > at boot time, which it wasn't doing before, and we don't know why we had
> > to disable svc:/network/initial:default to get the host to finish
> > booting properly. Is there something you know of that we can check to
> > try to get a better handle on what is going on? Even though we ran the
> > following commands:
> >
> > /svcadm disable svc:/network/nis/server:default
> > //svcadm disable svc:/network/nis/passwd:default
> > //svcadm disable svc:/network/nis/update:default
> > //svcadm disable svc:/network/nis/xfr:default//
> > //svcadm disable svc:/network/nis/client:default
> > //svcadm disable svc:/network/rpc/nisplus:default/
> >
> > we're still seeing it trying to obtain an NIS name at boot. We're also
> > still unsure why we had to disable svc:/network/initial:default to get
> > the host to finish booting properly
>
> If the system is up, you should check that nis/client is really disabled:
>
> $ svcs -p general/enabled nis/client
I think this command should be
svcprop -p general/enabled nis/client
>
> If that says 'true', run:
>
> # svcadm disable nis/client
> # svcs -p general/enabled nis/client
Again
svcprop -p general/enabled nis/client
>
> Confirm that now you get back 'false'. Reboot. Confirm again that
> general/enabled is 'false'. I apologize for being pedantic and
> repetitive here, but you've done a number of different things and I want
> to be sure to tease apart any separate issues.
>
> If the last svcs -p invocation gives you 'true', I can guess at a hazily
> remembered bug from s10, and suggest you send the output of:
>
> $ ls -asl /var/svc/profile/name_service.xml
>
> But, again, NIS being enabled doesn't explain the problems you're
> describing with a hang in boot -s. nis/client isn't started then.
> network/initial, however, is.
>
> Another vague memory is that I've seen the ifconfig in the
> network/initial method hang. To work out what's going on with
> network/initial, you should be able to re-enable network/initial, then:
>
> boot -m milestone=none
> login at the sulogin prompt
> # svcadm milestone all
>
> Then either wait a bit, or keep running "svcs" until the system state
> stops changing -- hopefully (or hopefully not), you'll see
> network/initial hanging again, and can use svcs -p network/initial to
> see what it's up to.
>
> Really, that's my first-principles debugging method for any reproducible
> hangs during boot: boot -m milestone=none, then svcadm milestone all
> and be able to see what's going on at the command line.
>
> liane
> _______________________________________________
> smf-discuss mailing list
> smf-discuss at opensolaris.org
