On 05/04/12 12:28, Pete Libke wrote:
On 5/4/2012 8:41 AM, Dave Miner wrote:
On 05/02/12 17:14, Mike Dotson wrote:
Howdy,
Doing AI installs of multiple SPARC systems and finding that
occasionally (and rising) we run into a system that has a boot-read fail
upon net boot. Digging into the issue, we see that the systems that boot
correctly have lines similar to the following in the error_log:
[$DATE] [error] [client $IP]INFO:root:Processing profile ${mac:address1}
[$DATE] [error] [client $IP]INFO:root:Parsed and loaded profile:
${mac:address1}
Systems that run into the boot-read fail issue don't have a
corresponding entry in the error_log but do show up in as configured in
the installadm list -c output:
installadm list -c
Service Name Client Address Arch Image Path
------------ -------------- ---- ----------
11_Express_b175b_sparc ${mac:address1} sparc
/export/install/media/11_Express_b175b_sparc/media
${mac:address2} sparc /export/install/media/11_Express_b175b_sparc/media
${mac:address3} sparc /export/install/media/11_Express_b175b_sparc/media
Should a properly configured system show up as being "Processed, Parsed
and loaded" in the /var/ai/image-server/logs/error_log or is this an
incorrect assumption?
I would expect that message to show up only when there is a
configuration profile associated with the client or service via criteria.
Stated another way, the error_log "processed and parsed entry" follows
the client's beginning wanboot request with the ai server?
A record of consumption rather than readiness?
Right. It's a result of a manifest+profile location request from a
booted AI client.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
