Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: stuartiannaylor on August 17, 2010, 06:01:42 pm
-
Hi sorry to post again about my problems with DHCP.
As I have said before the dhcpd.conf file doesn't seem to be correct. When I manually edit a subnet range with options when i restart dhcp3-server the conf file is over written.
Anyway I the ebox.log gives this infomation.
Can anyone tell me what this means? I have two identical broadcom built into the asus motherboard or is this a config error?
Many Thanks
Stuart
Any help would be much appreciated as I reall want to show a customer how eBox would be a really good solution (lol) maybe just not me!
010/08/17 16:47:37 INFO> Base.pm:152 EBox::Module::Base::save - Restarting service for module: dhcp
2010/08/17 16:47:37 ERROR> Sudo.pm:216 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/eth1/firmware' failed.
Error output:
Command output: .
Exit value: 1
2010/08/17 16:47:37 INFO> Base.pm:152 EBox::Module::Base::save - Restarting service for module: logs
2010/08/17 16:47:52 INFO> Service.pm:670 EBox::Module::Service::restartService - Restarting service for module: dhcp
2010/08/17 16:47:52 ERROR> Sudo.pm:216 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/eth1/firmware' failed.
Error output:
Command output: .
Exit value: 1
2010/08/17 16:48:09 INFO> Service.pm:670 EBox::Module::Service::restartService - Restarting service for module: dhcp
2010/08/17 16:48:09 ERROR> Sudo.pm:216 EBox::Sudo::_rootError - root command /usr/bin/test -f '/var/lib/ebox/conf/dhcp/eth1/firmware' failed.
Error output:
Command output: .
Exit value: 1
-
Have a look here:
http://forum.ebox-platform.com/index.php?topic=2360.msg10138#msg10138
Easiest fix is simply to upload a boot image.
http://rom-o-matic.net/gpxe/gpxe-1.0.1/contrib/rom-o-matic/
Choose "PXE bootstrap loader keep [Keep PXE stack method 1] (.kpxe)" and "all-drivers" then click Get Image.
Upload the resulting file to ebox's DHCP under Advanced Options -> Thin Client, choose Next Server: eBox, then click browse and upload the gpxe-1.0.1-gpxe.kpxe file.
That should take care of your test -f warnings, because now the file should exist.
It's not fatal or anything; but should probably be filed as a bug and fixed at some point.
Also -- you can't make changes to the dhcpd.conf directly; eBox will overwrite them from it's template every time you save the module. You *can* however, edit the template, with the caveat of losing your changes each time the module's upgraded. They live in /usr/share/ebox/templates/
-
Hi there,
That should take care of your test -f warnings, because now the file should exist.
It's not fatal or anything; but should probably be filed as a bug and fixed at some point.
These tests are harmless and ebox-dhcp does nothing if these files are not uploaded.
Thanks Kamilion for helping this out. :)
-
Sure thing.
The tests may be harmless; but an ERROR is an ERROR; and bosses don't like ERRORs.
The bug would be; there's not an exception check around this test for a return code of 1 to return a sane log entry like
2010/08/17 16:48:09 INFO> Service.pm:670 EBox::Module::Service::restartService - Restarting service for module: dhcp
2010/08/17 16:48:09 INFO> Dhcp.pm:670 EBox::Module::dhcp::checkFirmware - no network boot firmware available for: eth1
Also: 'sudo touch /var/lib/ebox/conf/dhcp/eth1/firmware' would have worked too.
-
Thanks for this thread...
Like Kamilion said, it help to just create the files in this folders.
"sudo touch /var/lib/ebox/conf/dhcp/eth1/firmware"
It would be better to log this as WARN not as ERROR.