7:16 a.m.
i'll give it a shot. no payments necessary. there shouldn't be any issues PXE
booting a system that already has an OS installed.
does the BIOS on the client system have PXE booting enabled? not sure if you'd get
the PXE output below if it wasn't, but better safe than sorry.
is this interface actually plugged into the network? this is most likely to happen if the
client has multiple NICs.
are both the client and the cobbler server on the same VLAN/subnet? if not is there a
properly configured DHCP proxy setup on the router(s) between the two? this may be done
at the switch level or the OS level, in the case of the cobbler server at least.
please post the output of the commands listed below. you'll need to replace anything
in <>'s to reflect your setup, such as the cobbler system name. here's the
laundry list of stuff i think we should look at, with examples from my setup:
do you have cobbler configured to manage DHCPD?
[root@cobbler ~]# egrep -i "dhcp|next_server" /etc/cobbler/settings | egrep -v
'^#'
manage_dhcp: 1
next_server: 192.168.1.1
restart_dhcp: 1
---
if so is DHCPD running?
[root@cobbler ~]# ps ax | grep dhcpd
20178 pts/1 S+ 0:00 \_ grep dhcpd
16430 ? Ss 0:01 /usr/sbin/dhcpd
---
is the dhcp.template file configured?
[root@cobbler ~]# egrep -iA9 "subnet
[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3} netmask"
/etc/cobbler/dhcp.template
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.5;
option domain-name-servers 192.168.1.1;
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.1.100 192.168.1.254;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server $next_server;
}
---
does this particular system object's MAC match the MAC displayed during PXE booting?
[root@cobbler ~]# cobbler system dumpvars --name=<YOUR_SYSTEM_NAME_HERE> | egrep -i
"mac"
allow_duplicate_macs : 0
dhcp_tag : default
dhcp_tag_eth0 :
interfaces : {'eth0': {'dhcp_tag': '', 'subnet':
'', 'virt_bridge': 'xenbr0', 'name':
'cobbler-client.domain.com', 'static_routes': [], 'dns_name':
' cobbler-client.domain.com ', 'hostname': ' cobbler-client.domain.com
', 'filename': '/pxelinux.0', 'ip_address':
'192.168.1.100', 'bonding': '', 'static': False,
'bonding_opts': '', 'mac_address': '00:50:56:be:00:49',
'next_server': ' cobbler.domain.com ', 'distro':
{'comment': 'rhel5.5', 'kernel':
'/var/www/cobbler/ks_mirror/CentOS-5.5-i386/images/pxeboot/vmlinuz',
'owners': ['admin'], 'breed': 'redhat', 'uid':
'MTI3NDM5MDYxNS4zOTI0NTMxNDMuMDc4NjU', 'kernel_options_post': {},
'arch': 'i386', 'redhat_management_key':
'<<inherit>>', 'source_repos':
[['http://@@http_server@@/cobbler/ks_mirror/config/CentOS-5.5-i386-0.repo',
'http://@@http_server@@/cobbler/ks_mirror/CentOS-5.5-i386']],
'kernel_options': {}, 'name': 'CentOS-5.5-i386',
'ks_meta': {}, 'os_version': 'rhel5', 'initrd':
'/var/www/cobbler/ks_mirror/CentOS-5.5-i386/images/pxeboot/initrd.img',
'depth': 0, 'tree_build_time': 1272587247.016243, 'mtime':
1282918027.2456779, 'redhat_management_server': '<<inherit>>',
'mgmt_classes': [], 'template_files': {}, 'ctime':
1274390615.3860371}, 'bonding_master': '', 'gateway': '',
'netboot_enabled': True}}
kernel_options : ksdevice=bootif lang= kssendmac text
ldap_search_prefix : sAMAccountName=mac_address_eth0 : 00:50:56:be:7b:94
manage_dhcp : 1
restart_dhcp : 1
static_eth0 : False
static_routes_eth0 : []
---
are there any log entries related to this system in the DHCPD logs?
[root@cobbler ~]# egrep -i $(cobbler system dumpvars --name=<YOUR_SYSTEM_NAME_HERE>
| egrep -o
'[[:digit:]a-eA-E]{2}:[[:digit:]a-eA-E]{2}:[[:digit:]a-eA-E]{2}:[[:digit:]a-eA-E]{2}:[[:digit:]a-eA-E]{2}:[[:digit:]a-eA-E]{2}'
| sort -u) /var/log/messages | sed -e 's/^.*\(dhcpd.*$\)/\1/g' | sort -u
dhcpd: DHCPDISCOVER from 00:50:56:be:00:49 via eth0
dhcpd: DHCPOFFER on 192.168.1.100 to 00:50:56:be:00:49 via eth0
dhcpd: DHCPACK on 192.168.1.100 to 00:50:56:be:00:49 via eth0
---
this should be a good start towards troubleshooting this issue.
byron
-----Original Message-----
From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Frank
Sent: Thursday, October 28, 2010 11:27 PM
To: cobbler mailing list
Subject: Re: Cobbler -- "No DHCP or proxyDHCP offers"
Apologies for my many typos and the last half sentence that should
not have been there! (corrected version below)
Frank
Hello All:
Someone from this list was so very kind several weeks ago to help me
installing Cobbler 2.003 on a VPS server account. It has now stopped
working, and I can't figure out why so.
When looking at what happens at the server via KVM (I tried this with
several presently unused servers) I see that the server is set up to
look for Cobbler, but can't find it (sorry about my terminology):
-------------------
Intel(R) Boot Agent GE v.1.3.31 IBA GE Slot 00C8 v1331 PXE 2.1 Build 086
Copyright (C) 1997-2009, Intel Corporation
CLIENT MAC ADDRESS: 00 27 0E UW 37 CF GUID: 6400C22C A4A0 11DE ...
PXE-E51: No DHCP or proxyDHCP offers were received.
PXE-M0F: Exiting Intel Boot Agent.
Boot Failure
Press any key to continue
-------------------
The MAC Address above has been altered ... but in Cobbler I sure
entered the correct one, and the correct IP also.
Would it make any difference is the server already has a working OS
installed (which is the case in all servers I tried)?
Is there anyone who could possibly help me with this? I am willing to pay.
Best wishes,
Frank
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler