FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora/Linux Management Tools

 
 
LinkBack Thread Tools
 
Old 05-31-2008, 08:42 PM
Ole Ersoy
 
Default Booting Hangs on "Trying to Load: pxelinux.cfg/default"

Any trouble shooting tips? I used to get a "boot" menu prior to adding a system...

TIA,
- Ole

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 06-01-2008, 05:33 PM
Slinky
 
Default Booting Hangs on "Trying to Load: pxelinux.cfg/default"

Make sure you have verbose enabled in /etc/xinetd.d/tftp

..
******* server_args************ = -s -v -v -v /tftpboot
...

You'll then see tftp hits in /var/log/messages. Example:

/var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: RRQ from 137.138.32.49 filename tftpboot/dir/file.cbt

/var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: sending NAK (1, File not found) to 137.138.32.49

It could just be some thing simple like you're dhcp points somewhere but your tftp "files" are else where.


HTH
Slinky


2008/5/31 Ole Ersoy <ole.ersoy@gmail.com>:

Any trouble shooting tips? *I used to get a "boot" menu prior to adding a system...



TIA,

- Ole



_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools



--
Regards
Dan
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 06-01-2008, 08:15 PM
Slinky
 
Default Booting Hangs on "Trying to Load: pxelinux.cfg/default"

2008/6/1 Ole Ersoy <ole.ersoy@gmail.com>:

Slinky,



Awesome - I get lots of information now, such as:



Jun *1 14:11:53 localhost dhcpd: DHCPDISCOVER from 00:16:ec:cc:d1:f6 via eth0

Jun *1 14:11:53 localhost dhcpd: DHCPOFFER on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0

Jun *1 14:11:55 localhost dhcpd: DHCPREQUEST for 192.168.1.2 (192.168.1.6) from 00:16:ec:cc:d1:f6 via eth0

Jun *1 14:11:55 localhost dhcpd: DHCPACK on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0

Jun *1 14:11:55 localhost xinetd[30107]: START: tftp pid=30114 from=192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30115]: RRQ from 192.168.1.2 filename /pxelinux.0

Jun *1 14:11:55 localhost in.tftpd[30115]: tftp: client does not accept options

Jun *1 14:11:55 localhost in.tftpd[30116]: RRQ from 192.168.1.2 filename /pxelinux.0

Jun *1 14:11:55 localhost in.tftpd[30117]: RRQ from 192.168.1.2 filename /pxelinux.cfg/01-00-16-ec-cc-d1-f6

Jun *1 14:11:55 localhost in.tftpd[30117]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30118]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A80102

Jun *1 14:11:55 localhost in.tftpd[30118]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30119]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A8010

Jun *1 14:11:55 localhost in.tftpd[30119]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30120]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A801

Jun *1 14:11:55 localhost in.tftpd[30120]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30121]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A80

Jun *1 14:11:55 localhost in.tftpd[30121]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30122]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A8

Jun *1 14:11:55 localhost in.tftpd[30122]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30123]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A

Jun *1 14:11:55 localhost in.tftpd[30123]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30124]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0

Jun *1 14:11:55 localhost in.tftpd[30124]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30125]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C

Jun *1 14:11:55 localhost in.tftpd[30125]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30126]: RRQ from 192.168.1.2 filename /pxelinux.cfg/default

Jun *1 14:11:55 localhost in.tftpd[30127]: RRQ from 192.168.1.2 filename /menu

Jun *1 14:11:55 localhost in.tftpd[30127]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30128]: RRQ from 192.168.1.2 filename /menu.cbt

Jun *1 14:11:55 localhost in.tftpd[30128]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30129]: RRQ from 192.168.1.2 filename /menu.0

Jun *1 14:11:55 localhost in.tftpd[30129]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30130]: RRQ from 192.168.1.2 filename /menu.com

Jun *1 14:11:55 localhost in.tftpd[30130]: sending NAK (1, File not found) to 192.168.1.2

Jun *1 14:11:55 localhost in.tftpd[30131]: RRQ from 192.168.1.2 filename /menu.c32

Jun *1 14:11:55 localhost in.tftpd[30132]: RRQ from 192.168.1.2 filename /pxelinux.cfg/default



So, I reread the man page, and it says that filename should be set to "pxelinux.0" and I had "/pxelinux.0", which is what dhcp.template came with

pxelinux.0 is the binary pxe loader. dhcp needs to point at pxelinux.0 (wherever it is*), as this is what the client needs to boot with.


default is the default pxe configuration which a request falls down to if the corresponding 01-aa-bb-cc-dd-ee-ff isn't found, and is generally found in pxelinux.cfg/


* If my dhcp was something like...


if option client-architecture = 00:00 { # Intel x86PC
** option LINUX.pxelinux-magic F1:00:74:7E;
** option LINUX.pxelinux-pathprefix "cobbler";
** option LINUX.pxelinux-reboottime 50;
** filename "cobbler/loader/pxelinux.0";

}
else if option client-architecture = 00:02 { # EFI Itanium
** filename "cobbler/loader/elilo64.0";
}
else if option client-architecture = 00:06 { # EFI IA32 - future extension (think Intel Apple ..)

** filename "cobbler/loader/elilo32.0";
}

A client would expect to find it in /tftpboot/cobbler/loader/pxelinux.0....

Does that help?

*
(Should I file a ticket?).
No.
**So I changed that to "pxelinux.0", and attempted to run cobbler sync, which tells me:




[root@localhost ole]# cobbler sync

cannot find directory: -v



I tried restarting the cobbler daemon and doing cobbler sync and the same message appears. *Thoughts?


tbh your cobbler setup sounds a bit FUBAR. Purge and try again perhaps?
*


Thanks again,

- Ole









Slinky wrote:


Make sure you have verbose enabled in /etc/xinetd.d/tftp



..

* * * *server_args * * * * * * = -s -v -v -v /tftpboot

...



You'll then see tftp hits in /var/log/messages. Example:



/var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: RRQ from 137.138.32.49 <http://137.138.32.49> filename tftpboot/dir/file.cbt


/var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: sending NAK (1, File not found) to 137.138.32.49 <http://137.138.32.49>




It could just be some thing simple like you're dhcp points somewhere but your tftp "files" are else where.



HTH

Slinky





2008/5/31 Ole Ersoy <ole.ersoy@gmail.com <mailtole.ersoy@gmail.com>>:




* *Any trouble shooting tips? *I used to get a "boot" menu prior to

* *adding a system...



* *TIA,

* *- Ole



* *_______________________________________________

* *et-mgmt-tools mailing list

* *et-mgmt-tools@redhat.com <mailto:et-mgmt-tools@redhat.com>

* *https://www.redhat.com/mailman/listinfo/et-mgmt-tools









--

Regards

Dan





------------------------------------------------------------------------



_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools




_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools



--
Regards
Dan
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 06-02-2008, 08:41 AM
Slinky
 
Default Booting Hangs on "Trying to Load: pxelinux.cfg/default"

2008/6/2 Ole Ersoy <ole.ersoy@gmail.com>:


pxelinux.0 is the binary pxe loader. dhcp needs to point at pxelinux.0 (wherever it is*), as this is what the client needs to boot with.



default is the default pxe configuration which a request falls down to if the corresponding 01-aa-bb-cc-dd-ee-ff isn't found, and is generally found in pxelinux.cfg/



A client would expect to find it in /tftpboot/cobbler/loader/pxelinux.0....



Does that help?




I think so. *Just want to make sure I'm clear. *The file is currently here:



[root@localhost ole]# ls /tftpboot/

elilo-3.6-ia64.efi *images *menu.c32 *pxelinux.0 *pxelinux.cfg



So if I put "pxelinux.0" for the filename option it should resolve correctly right?
That's right.

If your loader is at /tftpboot/loader/pxelinux.0 then dhcp would point at /loader/pxelinux.0


*




*

* * So I changed that to "pxelinux.0", and attempted to run cobbler

* *sync, which tells me:



* *[root@localhost ole]# cobbler sync

* *cannot find directory: -v



* *I tried restarting the cobbler daemon and doing cobbler sync and the

* *same message appears. *Thoughts?





tbh your cobbler setup sounds a bit FUBAR. Purge and try again perhaps?




I'll try to nuke the system and profile I added to see whether that caused the hiccup. *It was syncing fine before that. *Otherwise I'll start from scratch.



Thanks!

- Ole





_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools



--
Regards
Dan
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 06-02-2008, 02:10 PM
Slinky
 
Default Booting Hangs on "Trying to Load: pxelinux.cfg/default"

2008/6/2 Michael DeHaan <mdehaan@redhat.com>:

Slinky wrote:


Make sure you have verbose enabled in /etc/xinetd.d/tftp



..

* * * *server_args * * * * * * = -s -v -v -v /tftpboot

...




Regarding your other post about server locations, here's your problem, Mr. Slinky broke you



-s /tftpboot -vvv



You just set directory explicitly to "-v"
lies! LIES!!*


* based on the fact it works for us

*









You'll then see tftp hits in /var/log/messages. Example:



/var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: RRQ from 137.138.32.49 <http://137.138.32.49> filename tftpboot/dir/file.cbt


/var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: sending NAK (1, File not found) to 137.138.32.49 <http://137.138.32.49>




It could just be some thing simple like you're dhcp points somewhere but your tftp "files" are else where.



HTH

Slinky





2008/5/31 Ole Ersoy <ole.ersoy@gmail.com <mailtole.ersoy@gmail.com>>:




* *Any trouble shooting tips? *I used to get a "boot" menu prior to

* *adding a system...



* *TIA,

* *- Ole



* *_______________________________________________

* *et-mgmt-tools mailing list

* *et-mgmt-tools@redhat.com <mailto:et-mgmt-tools@redhat.com>

* *https://www.redhat.com/mailman/listinfo/et-mgmt-tools









--

Regards

Dan

------------------------------------------------------------------------



_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools




_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools



--
Regards
Dan
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 06-02-2008, 02:23 PM
Slinky
 
Default Booting Hangs on "Trying to Load: pxelinux.cfg/default"

...I should make clear that this box is non Cobbler, so we're both kinda right I guess

without the v's, we get nothing in the logs so the options are being parsed...





2008/6/2 Michael DeHaan <mdehaan@redhat.com>:






lies! LIES!!*





* based on the fact it works for us




That may be, but if so, it's likely tftpd noting the directory arguments are junk and defaulting to /tftpboot



*-s * * Change root directory on startup. *This means *the *remote *host

* * * * * * does *not need to pass along the directory as part of the trans-

* * * * * * fer, and may add security. *When -s is *specified, *exactly *one

* * * * * * directory *should *be specified on the command line. *The use of

* * * * * * this option is recommended for security as well as compatibility

* * * * * * with *some *boot *ROMs *which cannot be easily made to include a

* * * * * * directory name in its request.







_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools



_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 

Thread Tools




All times are GMT. The time now is 04:12 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org