Does anybody have problem with tftpboot ?

[nicolaslebrun]

Hi !

When trying to launch a netboot product, i often have the problem that the pxe configuration is read but the computer doesn't boot pxe...

The computer seams to read the fifo file but i guess it is not totally read...

Here is log of atftpd when it fails...

Code: Alles auswählen

Oct 30 16:46:00 opsiserver atftpd[16254.-939497728]: Creating new socket: 10.145.254.136:34975
Oct 30 16:46:00 opsiserver atftpd[16254.-939497728]: Serving /linux/pxelinux.cfg/a922ef55-e486-40dd-ade1-5c6ef4cdee84 to 192.168.230.217:49153
Oct 30 16:46:00 opsiserver atftpd[16254.-939497728]: File /srv/tftpboot//linux/pxelinux.cfg/a922ef55-e486-40dd-ade1-5c6ef4cdee84 not found
Oct 30 16:46:00 opsiserver atftpd[16254.-939497728]: Server thread exiting
Oct 30 16:46:00 opsiserver atftpd[16254.-939497728]: Creating new socket: 10.145.254.136:42991
Oct 30 16:46:00 opsiserver atftpd[16254.-939497728]: Serving /linux/pxelinux.cfg/01-08-00-27-25-d3-7c to 192.168.230.217:49154
Oct 30 16:46:00 opsiserver atftpd[16254.-928917760]: Creating new socket: 10.145.254.136:50437
Oct 30 16:46:00 opsiserver atftpd[16254.-928917760]: Serving /linux/pxelinux.cfg/01-08-00-27-25-d3-7c to 192.168.230.217:49154
Oct 30 16:46:00 opsiserver atftpd[16254.-947890432]: Creating new socket: 10.145.254.136:51770
Oct 30 16:46:00 opsiserver atftpd[16254.-947890432]: Serving /linux/pxelinux.cfg/01-08-00-27-25-d3-7c to 192.168.230.217:49154
Oct 30 16:46:01 opsiserver atftpd[16254.-956283136]: Creating new socket: 10.145.254.136:60467
Oct 30 16:46:01 opsiserver atftpd[16254.-956283136]: Serving /linux/pxelinux.cfg/01-08-00-27-25-d3-7c to 192.168.230.217:49154
Oct 30 16:46:01 opsiserver atftpd[16254.-964675840]: Creating new socket: 10.145.254.136:44118
Oct 30 16:46:01 opsiserver atftpd[16254.-964675840]: Serving /linux/pxelinux.cfg/01-08-00-27-25-d3-7c to 192.168.230.217:49154
Oct 30 16:46:01 opsiserver atftpd[16254.-947890432]: Read 0 bytes from pipe
Oct 30 16:46:01 opsiserver atftpd[16254.-964675840]: Read 0 bytes from pipe
Oct 30 16:46:01 opsiserver atftpd[16254.-964675840]: tsize option -> 0
Oct 30 16:46:01 opsiserver atftpd[16254.-964675840]: blksize option -> 1408
Oct 30 16:46:01 opsiserver atftpd[16254.-947890432]: tsize option -> 0
Oct 30 16:46:01 opsiserver atftpd[16254.-947890432]: blksize option -> 1408
Oct 30 16:46:01 opsiserver atftpd[16254.-939497728]: Read 0 bytes from pipe
Oct 30 16:46:01 opsiserver atftpd[16254.-939497728]: tsize option -> 0
Oct 30 16:46:01 opsiserver atftpd[16254.-939497728]: blksize option -> 1408
Oct 30 16:46:01 opsiserver atftpd[16254.-956283136]: Read 0 bytes from pipe
Oct 30 16:46:01 opsiserver atftpd[16254.-928917760]: Read 326 bytes from pipe
Oct 30 16:46:01 opsiserver atftpd[16254.-956283136]: tsize option -> 0
Oct 30 16:46:01 opsiserver atftpd[16254.-956283136]: blksize option -> 1408
Oct 30 16:46:01 opsiserver atftpd[16254.-928917760]: tsize option -> 326
Oct 30 16:46:01 opsiserver atftpd[16254.-928917760]: blksize option -> 1408

My confile of atftpd is /etc/default/atftpd

Code: Alles auswählen

$ cat /etc/default/atftpd 
USE_INETD=false
OPTIONS="--daemon --port 69 --retry-timeout 5     --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 --logfile /var/log/atftpd.log  /srv/tftpboot"

Am I missing something ?

[nicolaslebrun]

When it works, the good size is given first ...

326bytes at the first call ! Any idea ?

Code: Alles auswählen

Oct 30 17:17:18 opsiserver atftpd[16254.-947890432]: Creating new socket: 10.145.254.136:57965
Oct 30 17:17:18 opsiserver atftpd[16254.-947890432]: Serving /linux/pxelinux.cfg/01-08-00-27-25-d3-7c to 192.168.230.217:49154
Oct 30 17:17:18 opsiserver atftpd[16254.-939497728]: Creating new socket: 10.145.254.136:44028
Oct 30 17:17:18 opsiserver atftpd[16254.-939497728]: Serving /linux/pxelinux.cfg/01-08-00-27-25-d3-7c to 192.168.230.217:49154
Oct 30 17:17:18 opsiserver atftpd[16254.-947890432]: Read 326 bytes from pipe
Oct 30 17:17:18 opsiserver atftpd[16254.-939497728]: Read 0 bytes from pipe
Oct 30 17:17:18 opsiserver atftpd[16254.-947890432]: tsize option -> 326
Oct 30 17:17:18 opsiserver atftpd[16254.-947890432]: blksize option -> 1408
Oct 30 17:17:18 opsiserver atftpd[16254.-939497728]: tsize option -> 0
Oct 30 17:17:18 opsiserver atftpd[16254.-939497728]: blksize option -> 1408
Oct 30 17:17:18 opsiserver atftpd[16254.-947890432]: End of transfer

[m.radtke]

would be nice to know which OS and package versions

[nicolaslebrun]

Hello,

We're on Debian Wheezy (old stable)

ii opsi-atftpd 0.7.dfsg-5 amd64 advanced TFTP server - opsi version with pcre, fifo and max-blksize patches
ii opsi-configed 4.0.6.3.5.1-2 all OPSI config editor
ii opsi-depotserver 4.0.6.4-1 all opsi depotserver configuration package
ii opsi-linux-bootimage 20150916-3 amd64 opsi bootimage for netboot tasks.
ii opsi-utils 4.0.6.9-1 all utilites for working with opsi.
ii opsiconfd 4.0.6.10-7 all opsi configuration service
ii opsipxeconfd 4.0.5.5-2 all opsi pxe configuration daemon
ii python-opsi 4.0.6.28-1 all opsi python library

Could it be a problem with max-blksize ?

Thks,
Regards,

[n.wenselowski]

Hi,

did you read the releasenotes RE new bootimage / syslinux?
A downgrade of syslinux might help.


-Niko

[nicolaslebrun]

Thanks Niko,

We'll give it a try ...

Some news later !

Regards

Nico

[nicolaslebrun]

Hello,

It seems to be much reliable with syslinux 3.71...

Any idea why syslinux 6.0.3 sometimes fail with fifo files ?

Regards,

[m.radtke]

I suspect that the timing fails and thus requests the pipe several times. In the end the pipe is not available anymore then and it fails

[nicolaslebrun]

Hi M. Radtke,

I do agree with you !

Is there a way to change the time limit on the server side ?

I suppose I can't do anything on the client side ...

I have seen you revert to syslinux 3.71 in opsi 4.0.6 ... Is that for that reason ?

Thks,
Regards,

Nico

[m.radtke]

Yes this and other reasons like an incompatbility between syslinux 6 and various bioses causing that the client cannot localboot when running in PXE Mode

Currently I do not know where and how to change the limit. I would suggest to install the new testing bootimage and give it a try. See how it works for your problem.

Cheers
Mathias