Ryan, Ryan Schwartz wrote:
> Ok, so it's not sysidns that's dumping core as I suspected: > > system# sysidget > Assertion failed: *count <= max, file ns_dns_misc.c, line 189 > Abort (core dumped) > > it's sysidget. sysidget is only run when the GUI installer is running and from the *looks* of things, you're running a non-GUI jumpstart (but that's only my guess, can you confirm this?). 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. > And it's not just sysidget sysidlib, sysiduilib, and sysidtty are not runnable binaries, they are in fact libraries used by the other sysidtools. > The systems also reports: > > Installing boot information > - Installing boot blocks (c0t0d0s0) > - Updating system firmware for automatic rebooting > WARNING: Could not update system for automatic rebooting > > and drop to a prompt after completing their Jumpstart. 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 Ryan Schwartz wrote: > And it's not just sysidget > > system# sysidconfig > system# sysidget > Assertion failed: *count <= max, file ns_dns_misc.c, line 189 > Abort (core dumped) > system# sysidkrb5 > system# sysidlib > Illegal Instruction (core dumped) > system# sysidnet > system# sysidnfs4 > system# sysidns > system# sysidput > system# sysidroot > system# sysidsys > system# sysidtty > Illegal Instruction (core dumped) > system# sysiduilib > Illegal Instruction (core dumped) > > > This message posted from opensolaris.org > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/install-discuss
