OK, I fixed the Apache/HTTPD issue. After much, much, much searching I found this site for a fix and it worked for me.
http://awsadminz.com/httpd-service-main-process-exited-kill-cannot-find-process/
Should I post a separate tutorial as a fix for this issue?
As for the kernel thing, I tried a different PC and it is working fine. I guess I’ll have to figure that one out.

@Tom-Elliott
Ok, this thread is solved. After I deleted everything I was able to login. Thanks again guys.

Well, I’m not sure what happened but I tried to restart it yesterday and then it wouldn’t boot up. Something about no controller. Anyway, I guess CentOS 7 gives you the ability to boot from a last known good configuration and when I did that everything worked. I updated FOG and Apache2 went through without a hitch. Sorry to waste your time, thanks guys.

@Tom-Elliott said in Can't update GIT or FOG to newer versions.:

rpm --nodeps -e git; yum -y install git

OK, that went through successfully and I am updated with git and FOG. Thanks again Tom.

So this post can be solved, everything is working. I created an image and then redeployed it. Now on to looking into sysprep. Thanks guys.

@Wayne-Workman ok. I wish we could have come out with an answer. I guess it was just a PMS moment.

@ManofValor Yep clonezilla to a local usb hard drive. For the physical machines that is the easiest route.

although wasteful, this command should fix it:

cd /;rm -rf /opt/svn;mkdir /opt/svn;cd /opt/svn;setenforce 0;systemctl restart firewalld;for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service; done;systemctl restart firewalld.service;systemctl enable firewalld;yum install svn -y;svn co https://svn.code.sf.net/p/freeghost/code/trunk;cd trunk/bin;./installfog.sh

Also - you can permanently disable SELinux by editing the /etc/selinux/config file.

@Wayne-Workman Code added.

@ManofValor I think Tom’s guess is right, It makes sense.

To be honest, there appears to be absolutely nothing wrong with any of the network configuration on your FOG server.

We can test to see if Tom’s guess is right or not. If this CentOS 7 was installed with a GUI, it came with Firefox. Use firefox to try to visit our forums. If you can, Tom is right - and it also means that only ports 53, 80, and 443 are allowed into your network. IF this is the case, you’ll need your boss to loosen the straps so you can get your FOG server going - after that, he can tighten em down again. Or he can create rules that allow the FOG server full access to the internet. If it were up to me, I wouldn’t have a firewall that prevents work from being done. Do you guys have a demilitarized zone the fog server can be placed in temporarily so it can be installed and configured?

@Wayne-Workman I’ve checked and asked my boss, who built our system from the ground up, and we are not behind a proxy.

@Tom-Elliott Thx, that worked but now it finishes (I guess) and just loops. Ill post a seperate thread on that.