| 1 |
2008/12/22 Nadav Horesh <nadavh@×××××××××××.com>: |
| 2 |
> I tries the following: |
| 3 |
> |
| 4 |
> Commented out all lines in /etc/init.d/net |
| 5 |
> emerged dhcdbd and added it to the chain: |
| 6 |
> |
| 7 |
> acpid | default |
| 8 |
> alsasound | boot |
| 9 |
> beagled | default |
| 10 |
> bootmisc | boot |
| 11 |
> checkfs | boot |
| 12 |
> checkroot | boot |
| 13 |
> clock | boot |
| 14 |
> consolefont | boot |
| 15 |
> cpudyn | default |
| 16 |
> cupsd | default |
| 17 |
> dhcdbd | default |
| 18 |
> esound | default |
| 19 |
> gpm | default |
| 20 |
> hald | default |
| 21 |
> hostname | boot |
| 22 |
> ivman-user | default |
| 23 |
> keymaps | boot |
| 24 |
> lm_sensors | boot |
| 25 |
> local | default nonetwork |
| 26 |
> localmount | boot |
| 27 |
> modules | boot |
| 28 |
> net.eth0 | default |
| 29 |
> net.lo | boot |
| 30 |
> netmount | default |
| 31 |
> rmnologin | boot |
| 32 |
> samba | default |
| 33 |
> syslog-ng | default |
| 34 |
> urandom | boot |
| 35 |
> usbd | default |
| 36 |
> vixie-cron | default |
| 37 |
> xdm | default |
| 38 |
> xinetd | default |
| 39 |
> |
| 40 |
> |
| 41 |
> But it did not bring dhcp on at boot. |
| 42 |
> Is there any method I can follow the initialisation process and see if the |
| 43 |
> dhcp daemon is called? |
| 44 |
> |
| 45 |
> Nadav. |
| 46 |
> |
| 47 |
try to see the status of dhcdbd with /etc/init.d/dhcdbd status |
| 48 |
after you've ascertained that it has been started then you have to see |
| 49 |
the system |
| 50 |
logs for eventual errors: /var/log/messages contain the logs and dmesg |
| 51 |
give infos |
| 52 |
about them. i suspect that dhcdbd starts but cannot find a suitable dhcp server |
| 53 |
and thus it cannot assign the address. |
| 54 |
the other problem might be that you are starting in a different |
| 55 |
runlevel which doesn't |
| 56 |
have the service, but i doubt that this is the case. try to see the |
| 57 |
initial boot process |
| 58 |
and see if you're starting in default runlevel. |
| 59 |
|
| 60 |
in my logs i can get the following: |
| 61 |
|
| 62 |
Dec 22 19:45:28 [dhcdbd] Started up. |
| 63 |
Dec 22 19:45:33 [dhcdbd] message_handler: message handler not found |
| 64 |
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason |
| 65 |
Dec 22 20:45:34 [dhclient] wmaster0: unknown hardware address type 801 |
| 66 |
Dec 22 20:45:34 [dhclient] can't create |
| 67 |
/var/lib/dhclient/dhclient-eth2.leases: No such file or directory |
| 68 |
Dec 22 20:45:35 [dhclient] wmaster0: unknown hardware address type 801 |
| 69 |
Dec 22 20:45:36 [dhclient] DHCPDISCOVER on eth2 to 255.255.255.255 |
| 70 |
port 67 interval 4 |
| 71 |
Dec 22 20:45:36 [dhclient] DHCPOFFER from 192.168.0.1 |
| 72 |
Dec 22 20:45:36 [dhclient] DHCPREQUEST on eth2 to 255.255.255.255 port 67 |
| 73 |
Dec 22 20:45:36 [dhclient] DHCPACK from 192.168.0.1 |
| 74 |
Dec 22 20:45:36 [dhclient] can't create |
| 75 |
/var/lib/dhclient/dhclient-eth2.leases: No such file or directory |
| 76 |
Dec 22 20:45:36 [dhclient] bound to 192.168.0.6 -- renewal in 42566 seconds. |
| 77 |
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found |
| 78 |
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.host_name |
| 79 |
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found |
| 80 |
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.domain_name |
| 81 |
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found |
| 82 |
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.nis_domain |
| 83 |
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found |
| 84 |
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.nis_servers |
| 85 |
Dec 22 19:45:36 [dhcdbd] message_handler: message handler not found |
| 86 |
under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.interface_mtu |
| 87 |
|
| 88 |
you might have different formats, but the content should be similar. |
| 89 |
|
| 90 |
-- |
| 91 |
dott. ing. beso |
Archives