Thanks for the clarification. I'll add comments to 8695 if necessary. Regds, Paul
On 09/02/09 19:53, Sundar Yamunachari wrote: > Paul Neary wrote: >> I had a curious problem recently with my AI server (based on 2009.06). >> >> o I had two services setup for X86 and SPARC >> >> # installadm list -n 0906x86 >> Manifest >> -------- >> ai_manifest1.xml >> >> # installadm list -n 0906cparc >> Manifest >> -------- >> ai_manifest1.xml >> >> o However,when I just used the list option it saw no services >> >> # installadm list >> No install services running on the system > The 'installadm list' command gets the information using dns-sd > command. Since dns-sd processes dies, it doesn't show any services. > There is a disconnect between different list commands. They get data > from different places. The list command will be modified so that all > the data is coming from install service (SMF) >> >> o Also I couldn't get installadm create-client to work >> # installadm create-client -e 0:3:ba:68:11:7f -t >> /export/images/osol-0906-ai-sparc/ -n 0906cparc >> create-client: Service does not exist: 0906cparc >> >> o However, the install service is running fine. >> svcs install/server:default >> STATE STIME FMRI >> online 19:09:34 svc:/system/install/server:default >> >> o Also, the two services are listed as part of the install service. >> # svccfg -s install/server:default listprop | grep service_name >> AI0906x86/service_name astring 0906x86 >> AI0906cparc/service_name astring 0906cparc >> >> It turns out the problem was because the following dns-sd processes >> were missing (not sure what caused this to happen) >> # root 3750 1 0 19:09:28 ? 0:00 /usr/bin/dns-sd -R >> 0906cparc _OSInstall._tcp local 46502 aiwebserver=10.16.23.1 >> # root 3705 1 0 19:09:23 ? 0:00 /usr/bin/dns-sd -R >> 0906x86 _OSInstall._tcp local 46501 aiwebserver=10.16.23.19 >> >> o When I disabled and enabled the install service it restarted the >> dns-sd processes. The install SMF log file shows the following. >> Registering the service 0906x86._OSInstall._tcp.local >> Registering the service 0906cparc._OSInstall._tcp.local >> >> o However, there is no obvious connection between these processes and >> the install service. >> # ps -eo ctid,args | grep dns-sd >> 875 /usr/bin/dns-sd -R 0906x86 _OSInstall._tcp local 46501 >> aiwebserver=10.16.23.198 >> 876 /usr/bin/dns-sd -R 0906cparc _OSInstall._tcp local 46502 >> aiwebserver=10.16.23.1 >> #svcs -o ctid,fmri | grep 875 >> #svcs -o ctid,fmri | grep 876 >> >> o In fact the dns-sd processes show up as children of /sbin/init (ppid=1) >> >> SO, my questions are, >> If the dns-sd process is killed shouldn't this cause the install >> service to go into maintenance mode? > The install service will go to maintenance mode if all the services > created by create-service are disabled or died. In your case, it looks > like all dns-sd processes died but the install service didn't go to > maintenance mode. It looks like a bug. here is a bug against installer > service and dns-sd (8695). Please add your comments in the bug. > > Thanks, > Sundar >> Even though the install service starts the dns-sd processes is >> remains dependent on these processes working (I'm not sure how this >> translated to SMF though). >> Is this a bug in the SMF description of the AI install service? >> >> Thanks for any help, >> paul >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090903/bdadbadd/attachment.html>
