Ethan Quach wrote:
>
>
> Piotr Jasiukajtis wrote:
>> Hi,
>>
>>
>>> Can you check whether the
>>> svc:/network/dns/multicast:default
>>> service is online? And if its not, try enabling
>>> that, and then
>>> seeing if the create-service succeeds.
>>>
>> The dns/multicast was disabled. Now installadm works on both b111 and
>> b117.
>>
>>
>>> Also, is this the first install service you're trying
>>> to create on
>>> this system?
>>>
>> Right.
>>
>
>
> Thanks for replying with the additional info. I'll see if
> this is a known issue or not and file bugs as necessary.
installadm(1M) currently doesn't check status of dns/multicast -
it seem it might either make sure that dns/multicast is enabled
when the first service is to be created or (if less intrusive
approach might be more suitable) detect that it is not, report
this and abort, since in this case it is not able to register
the install service anyway.
Also, looking at install/server SMF service dependencies,
multicast/dns is listed as optional_all:
# svccfg -s install/server listprop
general framework
general/entity_stability astring Unstable
general/single_instance boolean true
dns-multicast dependency
dns-multicast/entities fmri svc:/network/dns/multicast:default
dns-multicast/grouping astring optional_all
dns-multicast/restart_on astring restart
dns-multicast/type astring service
...
According to smf(5) man page, this kind of dependency is satisfied,
even if service is disabled:
...
optional_all Satisfied if the cited services are running
(online or degraded) or do not run without
administrative action (disabled, mainte-
nance, not present, or offline waiting for
dependencies which do not start without
administrative action).
...
I think it should be 'require_all' instead, as AI server can't
provide its service without it.
Jan
