Do you get these cheetah template errors from sysB also ???
Google "tftp timeout" and you'll get a lot of hits… there's nothing cobbler specific here, most likely, just network related, and things can be intermittent.Particularly read the timeout info here: http://fedoraproject.org/wiki/Anaconda/NetworkIssuesThe portfast issue, in particular, came up a lot.On Wednesday, February 22, 2012 at 12:24 PM, Daniel Lollman wrote:
Hello Siddharth –
I tried that and it seems to be working ok!
[root@sysA ~]# tftp 172.19.10.200
tftp> get /pxelinux.0
tftp> get /pxelinux.cfg/01-00-00-00-00-00-00
tftp> get //images/CentOS6-x86_64/vmlinuz
tftp> quit
[root@sysA ~]#
Not sure if that helps anything or if I should try to get more.
[root@sysA ~]# ls -lah
-rw-r--r-- 1 root root 15K Feb 22 12:15 pxelinux.0
-rw-r--r-- 1 root root 264 Feb 22 12:16 01-00-00-00-00-00-00
[root@sysA ~]# ls -lah|grep vml
-rw-r--r-- 1 root root 3.8M Feb 22 12:16 vmlinuz
[root@sysA ~]#
Thanks again.
Daniel
From: cobbler-bounces@lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Siddharth Deshpande
Sent: Wednesday, February 22, 2012 12:06 PM
To: cobbler mailing list
Subject: Re: [cobbler] Testing cobbler install - pxe tftp open timeout
On Wednesday 22 February 2012 10:04 PM, Daniel Lollman wrote:
Until this morning.. I was working with one system (let’s call it sysA) which is in a subnet 172.19.10.x. For some reason when this system boots up now it gets a DHCP address but then tftp times out and eventually boots from local disk instead of reinstalling.
At the very least, from sysA (or another machine on the same layer-2 network, you should be able to use tftp on the command line and get the pxe boot file from the PXE server. Just in case you haven't tried that already.
--
siddharth._______________________________________________cobbler mailing list
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler