Ignite-UX BO lan.<IP> install Failed to initialize Status = -4

[Matthias Schuendehuette]

Well, first of all I have to say that *my* error reports a status of "-7", exactly as Mel Burslan (erroneously?) understood.

And "yes", client and server are of course in the same subnet, they're standing side by side besides my desk, connected to the same switch.

What I found so far is, that the entry in /etc/opt/ignite/instl_boottab is not reset for the client. If I stop/cancel the client installation on the ignite server, there's still the entry for the client in instl_boottab and the server refuses to boot the client again for 24 hours or so... Perhaps some misconfiguration elsewhere in ignite? I'm still new to this...

[Michael Roberts_3]

The default "reuse" time for entries in instl_boottab is 5 minutes. This can be overridden use the '-r' option to instl_bootd in /etc/inetd.conf. see instl_bootd(1m):

-r reuse_time Specify the minimum amount of time (in minutes)
that must elapse before an IP address may be
reused. The default value for reuse_time is five
minutes. reuse_time should correspond to the
amount of time a client requires to perform the
initial phase of the boot process (that is,
transferring the kernel into memory). Once
instl_bootd allocates an IP address to a client,
it will not reallocate the same address to another
client for reuse_time minutes. This prevents IP
address collision during the client's boot phase.
instl_bootd does not respond to clients (and
clients cannot boot) if it cannot successfully
allocate an IP address old enough to satisfy the
reuse_time requirement. In this case, a
diagnostic message is logged to syslogd (see
syslogd(1M)). If this condition occurs
frequently, adding more IP addresses to
instl_boottab may be necessary.

[Shane Russell]

Thanks guys