>(but that's only my guess, can you confirm this?
Yes, this is a (hopefully soon to be) non-interactive jumpstart
> The dump might still very well be coming from
> sysidns. Can you attach
> the sysidcfg file you're using and the
> /var/sadm/system/logs/sysidtool.log file after the
> failure happens.
> Those should tell the tale.
<snip>
> This warning is not a fatal error (its reporting that
> it was unable to
> update the eeprom to automatically boot the new
> boot_device), but if it
> immediately drops you to a shell prompt after this
> message, then
> something didnt' finish. Can you attach the
> /var/sadm/system/logs/install_log
I added some debugging to the sysid-finish script:
echo "Starting remote procedure call (RPC) services:\c"
echo about to call sysidns
SYSIDNS="/usr/sbin/sysidns -y"
if install_debug_isset man_sysid ; then
echo "Would have run \$SYSIDNS"
/sbin/sh
else
\$SYSIDNS
fi
echo just called sysidns
and here's what the output looked like:
Starting remote procedure call (RPC) services:about to call sysidns
Assertion failed: *count <= max, file ns_dns_misc.c, line 189
Abort - core dumped
just called sysidns
done.
I'll email those files to you directly. (Is there a definitive guide to
sysidcfg format and values, with an example for DNS, i.e. non-NIS/NIS+ folks
like me?)
Thanks!
This message posted from opensolaris.org
