Installation woes: dhcp...Failed!

[kbramhall]

Hey All,

I’m setting up FOG for the first time and I’m having some problems with the install. Following the installation guide I end up getting all of the packages installed except dhcp. I figured I could just install the dhcp package with yum but that’s failing as well. I’m trying to get to http://xxx.xxx.xxx.xxx/fog /fog/client and /fog/management but it won’t connect.

Here is the error at the end of installation:

Error Downloading Packages:
[Errno 256] No more mirrors to try

OS: CentOS 6.5
DNS: working
Internet: accessible
LAN: accessible via SSH
Firewall: disabled

Followed all of the steps below:
Type 1 and press Enter for Fedora/CentOS installation.
Type N and press Enter for Normal installation.
Supply IP Address, it should be the static IP address we setup earlier.
Type Y and press Enter to setup DHCP Server address.
Enter the DHCP Server address. If it's going to be the FOG Server, set it to the same IP Address as the FOG Server.
Type Y and press Enter to set up DNS.
Enter the DNS Server address.
Type N and press Enter to leave the default network interface.
Type N and press Enter to disable the FOG Server to act as the DHCP Server. Type Y to enable it.
Type N and press Enter to not install additional languages, unless you want them.
Type Y and press Enter to actually begin the installation.

Any suggestions?

[Wayne Workman]

What version of FOG are you trying to install?

Are you behind a proxy server?

[JJ Fullmer]

what dhcp package are you trying to install with yum?
And, since you’re new to the install, are you sure you want DHCP on the FOG server? Do you not already have a dhcp server on your network?

[kbramhall]

@Arrowhead-IT We are utilizing this FOG server to push a basic FreeBSD image to a large number of NAS drives that will be using an isolated subnet so we figured we’d just use the FOG server to run DHCP. I’ll check with our networking team to see if they can allow the FOG server to utilize its services.

I simply tried: yum install dhcp
but that fails with the same error as the FOG install: Errno 256 No more mirrors to try.

[Wayne Workman]

@kbramhall Isolated subnet? Does it have an internet connection?

[george1421]

This post is deleted!

[JJ Fullmer]

@kbramhall
I’m not 100% sure if the package is the same in redhat as it is in debian, but in debian its
sudo apt-get isc-dhcp-server

so maybe try

yum install isc-dhcp-server

I’ve had a problem where it wasn’t installing the dhcp package on debian too on a test DHCP style install a couple weeks ago and installing the package manually fixed the problem for me. But then I ended up not using the DHCP on fog.

[kbramhall]

@Wayne-Workman Installing 1.2.0 and we are not using a proxy server.

[george1421]

ok then lets confirm a few things.

You want FOG to be the dhcp and/or dns server for your subnet? Or do you have an existing infrastructure already in place? If you have an existing infrastructure in place AND/OR you are not doing PXE booting then you can skip the dhcp and dns configurations.

[kbramhall]

@Wayne-Workman Yes it does. Once the install/services are up and running we’ll take it off of the public facing IP and throw an internal IP on it.

[kbramhall]

@george1421 We are hoping to use PXE booting for these NAS devices using this FOG server to push a FreeBSD image over an isolated subnet.

[Wayne Workman]

@Arrowhead-IT in RHEL 7 / Fedora 19+ / CentOS 7 it’s just yum install dhcp

@kbramhall I know you said you weren’t behind a proxy - but we’ve heard/seen the issue you’re describing several times and more times than not it’s because of a proxy server / web filter / firewall higher up on the network that’s blocking access to repositories and mirrors.

Can you make double sure?

[george1421]

@kbramhall How about the part, do you need FOG to be the dhcp and dns server for the subnet where it will exist? I want to ensure that you REALLY need both dhcp and dns setup. Sorry for being picky here, but since this is your first time with fog I want to ensure we know how you need it setup.

[JJ Fullmer]

@george1421 said:

ok then lets confirm a few things.

You want FOG to be the dhcp server for your subnet?

Just so you know. The reason I chose not to use DHCP with FOG is because I had the mistaken assumption that FOG would automatically manage it in some way, or that the gui would have some control over it. It does not, you’ll be doing a bunch of manual configuration. It added some small configuration and did get it passing out ip addresses, which may be enough for you. But just be aware that you’ll likely have to do some more manual configuration of the DHCP. Not that that is all that hard nor undocumented on the internet, just wanted to make sure you’re aware.

[kbramhall]

@Arrowhead-IT Unfortunately that failed as well. I’m thinking there may be an underlying networking issue that I’ll work on with our networking team. Either way even if dhcp isn’t running on this server shouldn’t I still be able to get to http://xxx/xxx/xxx/fog ?

[JJ Fullmer]

This post is deleted!

[george1421]

@kbramhall If fog doesn’t fully setup the first time then no it will not display the console login.

I would suggest that you go back from the beginning and select no for dns and no for dhcp. You can set those up later if you really need them. The packages are downloaded and installed then the database is configured then the apache settings are configured.

[Wayne Workman]

@Arrowhead-IT said:

Just so you know. The reason I chose not to use DHCP with FOG is because I had the mistaken assumption that FOG would automatically manage it in some way, or that the gui would have some control over it. It does not, you’ll be doing a bunch of manual configuration.

I guess now is as good a time as ever to say I’m working on an add-on that does just this.

[Tom Elliott]

I still feel this needs to be addressed.
@Wayne-Workman said:

@kbramhall Isolated subnet? Does it have an internet connection?

[kbramhall]

@george1421 I’ll give that a shot. Thanks