topic Re: tftp problems with ignite in Operating System - HP-UX

tftp problems with ignite

GXW_1 — Thu, 10 Jul 2008 13:57:12 GMT

Hi, I've been getting an intermittent tftp error with my ignite server. Symptoms are when trying to boot itanium client - server times out, and looking in the syslog I see:

tftpd[17697]: chroot: No such file or directory

I have the following entries in /etc/inetd.conf:

tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd

But basically inetd -c doesn't sort it but a reboot does. Same lanboot works fine after a reboot.

Any ideas what could be causing this intermittent problem?

I thought it might be due to tftp user's home dir not existing but - a reboot wouldn't fix that!

Re: tftp problems with ignite

Tim Nelson — Thu, 10 Jul 2008 15:20:49 GMT

What version of Ignite ?

I have had no current issues lan booting IA clients. I am running C.7.5.142

IA clients use instl_bootd

instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd

Re: tftp problems with ignite

Steven E. Protter — Thu, 10 Jul 2008 16:47:03 GMT

Shalom,

Later versions of tftp in an effort to be more "secure" that being a relative term are sensitive to ownership and permissions.

tftp will only work from the home directory of the tftp user owned by that user.

SEP

Re: tftp problems with ignite

GXW_1 — Fri, 11 Jul 2008 12:17:13 GMT

Tim, I'm using 7.0.212 which is just what was shipped on my 11i v3 DVDs.

I believe instl_bootd is for anonymous clients - whereas mine are registered so I've stuck to bootpab.

As I said - it works fine most of the time.

Steven, I don't understand how perms on tftp's home directory can be an issue - a reboot wouldn't resolve the issue if that were the case - nor would it be intermittent!

Presumably the inetd.conf entries added during Ignite setup set up tftp access to /var/opt/ignite so that the INDEX file can be picked up. So the home directory doesn't really feature. Perms on /var/opt/ignite are 755 bin:bin.

I will just have to wait until this happens again and then do some more diagnosis. I hadn't really focussed on instl_bootd before so that might be something to investigate? Maybe instl_bootd and bootpd are getting in the way of each other?