upgrading fog on a standalone network
-
@fredlwal Unfortunately you need internet access (temporarily) while FOG is being upgraded. Once the upgrade is complete then you can return fog to an isolated network. Be aware you can accomplish this with a second nic in your FOG server too. As long as the fog installer can get to the internet to pickup the latest files you should be OK.
-
How would I go about saving my standalone network settings and then changing it back after the upgrade? For example turn off dhcp and static ip and just pull from the internal network.
-
@george1421 fredlwal less than a minute from now
How would I go about saving my standalone network settings and then changing it back after the upgrade? For example turn off dhcp and static ip and just pull from the internal network. -
@fredlwal What OS is your fog server running?
-
@Wayne-Workman ubuntu server 14
-
@fredlwal Do you have the capabilities to add a second network card for the duration of the upgrade?
I just remembered, there is a chance of a negative impact if you change IP addresses after fog is (re)installed. You may also need to download Wayne’s script for updating the FOG IP settings while you are connected to the internet.
-
@fredlwal If you don’t have a gui installed, the configuration you would change is in
/etc/network/interfaceshere are a few good links on it:
https://www.cyberciti.biz/faq/setting-up-an-network-interfaces-file/
https://wiki.debian.org/NetworkConfiguration
http://manpages.ubuntu.com/manpages/precise/man5/interfaces.5.html
http://askubuntu.com/questions/431682/how-do-i-use-etc-network-interfaces-instead-of-network-managerIf you can manage to successfully change your OS’s IP and get it on the network with internet, you would then run the newer fog installer, then bring it back to the standalone network. You can either follow this article to change the IP settings in FOG back to the stand-alone stuff, or you can use the updateIP tool to do it for you which would also correct dhcp on the box too.
Changing FOG Server IP addresses isn’t light work for someone who’s not done it before, hence the tool.
For ease, like George said it’d be easier to just put in a second NIC so this is solved in the future more easily.
-
@Wayne-Workman I was able to turn on the second network card and now i’m on. what’s the article for upgrading the fog?
-
@fredlwal said in upgrading fog on a standalone network:
what’s the article for upgrading the fog?
It’s always been this: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk
-
How do I get certs to push down to the server so I can get this to work?
-
@fredlwal What certs are you talking about? No certs are needed to clone the git repository.
-
@Quazz CA certs
-
@fredlwal I’m guessing git is complaining?
Try doing
git config --global http.sslVerify falseThen try cloning the repository again.
-
@Quazz @Wayne-Workman that part worked but now the repository failed during installation , here is a screen shot.
https://goo.gl/photos/Pi32rSCFdQstQcPw8 -
@fredlwal Please run
apt-get install software-properties-commonAnd try again.
If it still doesn’t work, please post the error-log in the your git folder/bin/error_logs/ here
-
@fredlwal Sounds like you have a proxy or web filter that is doing some sort of wild DNS redirecting or web caching. others have had this issue in the past with the same two errors you just described.
-
@Quazz for some reason I don’t see error_logs folder, where else could I look?
-
@fredlwal Within your
~/project/bindirectory you should haveerror_logsdir containing log files:~/project/bin/error_logs/... -
@Sebastian-Roth Assuming the OP used git to replicate the fogproject repository as well as followed the instructions from the wiki page. Would the proper path be /opt/fogproject/bin/error_logs to find the log files?
-
According to the screenshot the OP posted…