Installation woes: dhcp...Failed!

[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

[kbramhall]

@Arrowhead-IT That is good to know. I am pretty sure all we need is to push IPs from a given IP pool to each of these devices.

[Tom Elliott]

@kbramhall All of this banter is going to go nowhere if the network you’re trying to install this thru does not have Internet access.

[kbramhall]

@Tom-Elliott If the FOG server is on-net with the devices won’t that make an internet connection unnecessary?

[Tom Elliott]

@kbramhall YEs, but not during the installation process.

The installer needs to download the files to do the install to begin with.

[kbramhall]

@Tom-Elliott The CentOS machine currently has internet access that’s how I downloaded the installer.

[Tom Elliott]

I’m confused.

Are you downloading the installer, then disconnecting internet?

[Tom Elliott]

Basically,

Does the internet work? Is it installing other packages, but failing to install dhcp?

I need clear concise answers.

Forgive my methods, but understand:

The CentOS machine has internet, it’s how I downloaded the installer, vs. The FOG Server is on Net with the clients, is not concise.

I’m assuming, at this point, the CentOS machine you are referring to is the same as your FOG Server?

[kbramhall]

@Tom-Elliott Sorry about that. Yes, the CentOS server is the what we’re running FOG on. I’ll just say FOG server moving forward to avoid any confusion. Yes it is successfully downloading other packages (httpd, php, php-cli, php-common, etc) but is not downloading the dhcp package. It has internet connectivity and will for the remainder of the setup. Once everything is up and running we’ll remove the internet connection and put it on an isolated subnet physically connected to the devices it needs to connect to.

[kbramhall]

@Tom-Elliott I attempted to go through the installer and saying no to DHCP and DNS but if failed to install tftp-server this time. Attached is the foginstall.log file.0_1450298881023_foginstall.log

[george1421]

To not add too much more noise to this thread. It looks like yum isn’t able to resolve the external repositories dns names.

On this fog server, you set a static IP address, did you remember to update /etc/resolv.conf with the DNS servers the FOG server will use to query for internet names?

Since you have direct internet access can you ping www.google.com? Or one of the repositories mirrors.gigenet.com?

[JJ Fullmer]

@kbramhall Considering that you only just set this up, maybe it’s worth trying a different distro. I’ve had better experiences with ubuntu server and fog then cent OS. But I am more familiar with debian so I might be biased.
But maybe it’s an issue with the OS install.
What happens when you run

yum update

?
If that doesn’t seem to connect to anything, then
What does your resolv.conf say?

cat /etc/resolv.conf

Might be a dns server thing. That’s sometimes the issue when you can’t seem to install a package

[Wayne Workman]

@george1421 @Arrowhead-IT Good point. Right now I think we’ve got it narrowed down to either a DNS issue or a proxy issue.

[JJ Fullmer]

@Wayne-Workman said:

@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.

@Wayne-Workman ooooh! I like that idea!

[Tom Elliott]

@Arrowhead-IT, @Wayne-Workman, @kbramhall, @george1421 I notice a few issues in the log. First is a typo (Staring Redhat install) that has no impact. But further down line 1: …/lib/redhat/functions.sh n#: or something very similar. @kbramhall how set are you to using 1.2.0? Would you be willing to try trunk? I think it may help out tremendously in the install process. Of course please verify /etc/resolv.conf has the proper dns info.

[JJ Fullmer]

@kbramhall said:

@Tom-Elliott I attempted to go through the installer and saying no to DHCP and DNS but if failed to install tftp-server this time. Attached is the foginstall.log file.0_1450298881023_foginstall.log

I took a look at the install log and noticed this bit

../lib/redhat/functions.sh: line 1: n#: command not found

I’ve seen that before. You need to both make sure that you’re running as the root user and make sure you’re running the install script from the bin folder.
i.e. cd into where you downloaded/untarred the fog installer and then

cd bin
./installfog.sh

I figured out when making the automated update scripts that you can’t run it with the full path like
/home/fog/installFoder/bin/installfog.sh
because it use the trailing … to get to some included scripts. So you have to start the script from its happy home.

Also, what happens when you try to install the packages that failed manually?
I would try them one at a time. It looks like these ones…

yum install tftp-server
yum install xinetd
yum install vsftpd
yum install gcc
yum install gcc-c++
yum install lftp

And I just had another thought, are you sure the firewall is completely disabled? I just remembered a recent experience where a fresh install cent OS wouldn’t do internet things until I flushed the iptables.
Which if memory serves is

iptables -F
or
iptables -f

Hopefully something there helps

[kbramhall]

@george1421 Yep, I can ping friendly names like mirrors.gigenet.com and google.com

[kbramhall]

@Arrowhead-IT As we’re troubleshooting I’m thinking it is definitely something with our internal networking configuration. The DNS servers we are using include google’s 4.2.2.2 and an internal DNS server.