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 (Should I file a ticket?). 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?
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@xxxxxxxxx <mailto:ole.ersoy@xxxxxxxxx>>:
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@xxxxxxxxxx <mailto:et-mgmt-tools@xxxxxxxxxx>
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
--
Regards
Dan
------------------------------------------------------------------------
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
