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 > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 04-16-2008, 01:42 PM
Tom Brown
 
Default CentOS 4.6 - dhcp issue

Hi - On my CentOS 4 cobbler server i am having some odd dhcp issues.

There is only 1 dhcp server on the network and the cobbler box manages
the dhcp. When i kick off the PXE install during the PXE phase things
seem OK then when anaconda tried to get an IP sometimes things work out
fine and other times it sits waiting for hostname/domainname. From the
logs you can see that the mac requesting the IP is constant but the IP
being offered is sometimes 'wrong'. In the 2 examples below nothing is
changed the differing result is just achieved by trying another install,
as i said its rather random.


Any thoughts?

thanks


** section of log i see when i have install issue **

Apr 16 14:25:53 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:16:f8:b5 via eth0
Apr 16 14:25:53 cobbler dhcpd: DHCPOFFER on 192.168.12.190 to
00:0c:29:16:f8:b5 via eth0

Apr 16 14:25:53 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:16:f8:b5 via eth0
Apr 16 14:25:53 cobbler dhcpd: DHCPOFFER on 192.168.12.190 to
00:0c:29:16:f8:b5 via eth0
Apr 16 14:25:53 cobbler dhcpd: DHCPREQUEST for 192.168.12.212
(192.168.12.117) from 00:0c:29:16:f8:b5 via eth0: lease 192.168.12.212
unavailable.
Apr 16 14:25:53 cobbler dhcpd: DHCPNAK on 192.168.12.212 to
00:0c:29:16:f8:b5 via eth0


** section of log when everything works OK **

Apr 16 14:31:42 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:16:f8:b5 via eth0
Apr 16 14:31:42 cobbler dhcpd: DHCPOFFER on 192.168.12.190 to
00:0c:29:16:f8:b5 via eth0
Apr 16 14:31:44 cobbler dhcpd: DHCPREQUEST for 192.168.12.190
(192.168.12.161) from 00:0c:29:16:f8:b5 via eth0
Apr 16 14:31:44 cobbler dhcpd: DHCPACK on 192.168.12.190 to
00:0c:29:16:f8:b5 via eth0
Apr 16 13:31:44 cobbler in.tftpd[4334]: tftp: client does not accept
options

Apr 16 14:32:08 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:16:f8:b5 via eth0
Apr 16 14:32:08 cobbler dhcpd: DHCPOFFER on 192.168.12.190 to
00:0c:29:16:f8:b5 via eth0

Apr 16 14:32:08 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:16:f8:b5 via eth0
Apr 16 14:32:08 cobbler dhcpd: DHCPOFFER on 192.168.12.190 to
00:0c:29:16:f8:b5 via eth0
Apr 16 14:32:08 cobbler dhcpd: DHCPREQUEST for 192.168.12.190
(192.168.12.161) from 00:0c:29:16:f8:b5 via eth0
Apr 16 14:32:08 cobbler dhcpd: DHCPACK on 192.168.12.190 to
00:0c:29:16:f8:b5 via eth0


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 04-17-2008, 06:31 PM
Kai Schaetzl
 
Default CentOS 4.6 - dhcp issue

these are not virtual machines?

Kai

--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 04-17-2008, 06:40 PM
Tom Brown
 
Default CentOS 4.6 - dhcp issue

these are not virtual machines?





the cobbler server is (currently) a VM yes - the clients are not. Why
should that make any difference?


thanks



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 04-17-2008, 06:45 PM
Tom Brown
 
Default CentOS 4.6 - dhcp issue

Tom Brown wrote:



these are not virtual machines?





the cobbler server is (currently) a VM yes - the clients are not. Why
should that make any difference?




actually in that example the client was also a VM i remember now - but
the symptoms are the same on 'real' clients


thanks

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 04-17-2008, 08:31 PM
Kai Schaetzl
 
Default CentOS 4.6 - dhcp issue

Tom Brown wrote on Thu, 17 Apr 2008 19:40:21 +0100:

> Why
> should that make any difference?

The conversations looked a bit like you had several clients with the same
MAC in the LAN. This can happen if one copies existing config files.

Also, I know there are cases where a DHCPOFFER (or any DHCP packet from
the server for that matter) may not make it over the bridge for the VMs).

I'm afraid I can't help more, I can just say that I've never seen such a
conversation:

> Apr 16 14:25:53 cobbler dhcpd: DHCPREQUEST for 192.168.12.212
> (192.168.12.117) from 00:0c:29:16:f8:b5 via eth0:

Any hint where that (192.168.12.117) comes from? I see that you have the
same on your successful conversation, though.

Is there a chance you have two DHCP servers on the LAN?


Kai

--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 04-17-2008, 08:51 PM
Tom Brown
 
Default CentOS 4.6 - dhcp issue

Apr 16 14:25:53 cobbler dhcpd: DHCPREQUEST for 192.168.12.212
(192.168.12.117) from 00:0c:29:16:f8:b5 via eth0:



Any hint where that (192.168.12.117) comes from? I see that you have the
same on your successful conversation, though.


Is there a chance you have two DHCP servers on the LAN?



no idea where the 12.117 comes from as there is definately not another
dhcp server on the LAN as in the logs there is only ever dhcp 'stuff' in
the logs of this server so i dont really know whats going on.


maybe i just wait to fix this until i get it onto a physical machine.


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 11:44 PM.

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