Installation woes: dhcp...Failed!

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

[kbramhall]

@Tom-Elliott Hey Tom, we are not dead set to use 1.2.0 we just figured we’d download the latest from the FOG project website

[JJ Fullmer]

@kbramhall said:

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

Isn’t google dns server 8.8.8.8 and 8.8.4.4 ?
And if you’re using public dns’s maybe try opendns and see if that makes a difference
208.67.220.220 and 208.67.222.222

When you say internal network config, do you mean at the network infrastructure level or with the FOG server OS?
If you think its the local network, do you have any other cent OS boxes, and if so are they able to install the packages?

@kbramhall said:

@Tom-Elliott Hey Tom, we are not dead set to use 1.2.0 we just figured we’d download the latest from the FOG project website

Welcome to Fog, where if Tom were to release every stable release of the development branch it would be worse than Ccleaner updates.
1.2.0 was the last time something was labeled stable. I use the trunk in production and rarely have any issues, and you get new features all the time! And if there ever is a problem it’s fixed in a snap. Only issue with your configuration and the trunk is that you wouldn’t have internet, so you wouldn’t be able to install and updates. Which overall would be fine, I’m one of the crazies on the bit torrent sync to the source files because I can’t wait the 20 seconds it takes Tom to hit the commit button.

Anyway to install the trunk you’ll need git, svn, or btsync. Git is probably the easiest, svn is on sourceforge.net and they’ve gone down like 5 times in the last 3 months. There’s instructions on the wiki here https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

[kbramhall]

@Arrowhead-IT That’s a good idea. I’ll see if there is another test box I can try using. I did try those DNS servers and still having problems (also my mistake 4.2.2.2 is Level 3 not Google). I’ll speak with our networking team and one of our Sr Sys Admins and see if they have a second to look over the system. Thanks for all of your help and speedy responses @Tom-Elliott, @Arrowhead-IT , @george1421 and @Wayne-Workman

[Tom Elliott]

@kbramhall just going on a limb but I don’t think it’s directly related to dns but rather, based on the network structure, maybe limiting outgoing/incoming requests? Maybe firewall on the incoming side of things? The fact that it fails during mirror lookups makes me think transfer requests aren’t being allowed?

[kbramhall]

@Tom-Elliott Looks like there was something wrong with yum. I did a basic yum clean all and that seemed to solve my issues with connecting to the mirrors. I’m progressing through the installation now. Thanks again for all of your help everyone!