[Maintain] Error updating dhcp
adam.nielson at hp.com
Mon Oct 15 19:19:01 UTC 2007
Thank you for the response. I dont believe this has yet been addressed however.
When I try and run check-dhcp and check-dns, from the /opt/maintain-3.1.0/bin/build directory, I get the following:
PHP Fatal error: Call to undefined function: getmodulebyname() in /opt/maintain-3.1.0/bin/build/check-dhcp on line 48
Which someone replied needed to be fixed, and they could send me a patch or fix for it. I am also assuming this ties in with running the 'all' script too?
From: bradmorgan596 at gmail.com [mailto:bradmorgan596 at gmail.com] On Behalf Of Brad Morgan
Sent: Monday, October 15, 2007 11:58 AM
To: Nielson, Adam
Subject: Re: [Maintain] Error updating dhcp
Here's a list of steps to get both dns and dhcp building. (Just leave out the parts that have to do with build_dns if you are only interested in dhcp, or vice-versa)
1. Make sure that build_dns and build_dhcp are installed and enabled.
1. From the command line, make sure you run '[MAINTAIN_DIR]/bin/modules.php -i build_dns' and ' [MAINTAIN_DIR]/bin/modules.php -i build_dhcp'. '-i' is the "install" flag, so notice that this only makes Maintain aware of the module, it doesn't quite enable it for use. (There are also -d disable, -e enable, -u uninstall)
2. Now, navigate to ' [MAINTAIN_DIR]/modules/build_dhcp' and make sure that your config file has all the correct information in there. (NOTE: Also, make sure that you move the config file that was distributed with the module ( build_dhcp.cfg.dist) to the file build_dhcp.cfg and make all of your changes there instead. build_dhcp.cfg.dist is a generic template file that should be your starting point, but Maintain will not build if you don't have a proper build_dhcp.cfg file.
3. Do #2 for build_dns if you need.
2. Run the build scripts.
* At this point, everything should be configured correctly. Assuming that you have data in Maintain to build config files for, you should be able to run '[MAINTAIN_DIR]/bin/build/all -b' and then take a look inside '[MAINTAIN_DIR]/build'. You should find dhcpd.conf.data in there as well as dns.data if you installed that module as well.
If you are having any particular problems, or receiving specific errors, let us know and we will help you out.
On 10/11/07, Nielson, Adam <adam.nielson at hp.com<mailto:adam.nielson at hp.com>> wrote:
> Ok, thank you for the information.
> ...So, the backend modules don't appear to be running. I have set up the build_dhcp config file, I just put the local system name in to connect to, etc, and I put the "all" script as a cron job. However, does the "all" script need fixed like the check_dhcp and check_dns in the same folder that's having issues for me? As it isnt updating the dhcpd.conf.data file in the build directory and thus not updating my /etc/dhcpd.conf.
> -----Original Message-----
> From: Josh Schonstal [mailto: schonstal at osuosl.org<mailto:schonstal at osuosl.org>]
> Sent: Thursday, October 11, 2007 11:23 AM
> To: Brad Morgan
> Cc: Nielson, Adam; maintain at osuosl.org<mailto:maintain at osuosl.org>
> Subject: Re: [Maintain] Error updating dhcp
> Brad Morgan wrote:
> > Yes and no. I suppose there is no reason that the modules can't be
> > installed by default so they show up in the UI and whatnot. However
> > these modules can't be enabled because they require a bit of
> > configuration in order to work.
> I believe the reason they are not installed by default is because they are backend modules, but not core modules. This means that anyone who is using Maintain may not necessarily want to use it for dhcp or dns (though I don't really know why you wouldn't want to at this point). In theory, you should be able to chose the backend modules you want to use, and when there is a case in which there are multiple modules to chose from (ie a djb module and a bind module for dns) you won't want one installed by default because there are multiple modules to chose from.
> Really, I think it should be alright to have the default dns and dhcp modules installed by default; then we could make it necessary for them to be enabled (and they would show up in the UI). Then the user could chose to enable it if they would like, or they could install an alternate backend module and they would be able to enable that one instead. This would allow easier use in the default case; however, this also means that if you don't want the default modules around and you want exclusively your custom/alternate modules installed, you would have to uninstall the modules that are installed by default.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the maintain