Updating Fog to newer version and Pending Mac Addresses
bmick10 last edited by
Just wondering a couple things. We are currently on version 1.3.5-RC-11. Is it beneficial to update to newer version? Would like to get to most stable version instead of most recent if possible. So If I do the following command(see below) like I did to get to 1.3.5-RC-11 will it give me 1.5.10 or what version will it give me. I read the most stable version is 1.4.4 at this time. Any info on this would be great. Also, if a command to use to just get 1.4.4 would be great also if that is what I need to do. I have had to reinstall 1.3.5-RC-11 a couple times because of database schema was wrong. Reason why this happens? No biggy, just kinda of wondering background on this or why it may happen?
git checkout dev-branch
Pending Mac Addresses. Seems to me we did not have as many of these in previous versions. So what is best way to handle these? Just allow them all? Any info on these would be awesome too!
just wondering if it is always something that breaks locally or if things can be affected by developers or fog employees.
We aren’t employees, FOG is supported entirely by a community of volunteers that help out at their own discretion, of their own accord. There’s no money involved besides donations - which are never expected but always appreciated. You can help out too, just by answering questions you can answer or writing tutorials or documentation, videos, etc. You’ll find that you will learn a ton just by reading the stuff that’s posted here.
As for if things are affected or not by the devs - if you re-run the fog installer, it would get the latest kernel and init in order to support the latest hardware - but no web-core changes or DB changes are made unless you actually go get the latest version of FOG. As for your OS, when you re-run the installer it makes sure it has the latest version of the packages it needs, everything else is left unchanged. Ubuntu is notorious for resetting customized configuration files during updates, which in turn cause problems - this is of course compounded because Ubuntu by default automatically updates and most people aren’t knowledgeable enough about Linux to rip out that functionality.
bmick10 last edited by
@sebastian-roth I found a different article on this and got my answer. Has to do with Ubuntu updates that is causing my database connection to have problems. Thanks
bmick10 last edited by bmick10
@sebastian-roth totally understand on question about random database schema problem. Here is link to original question back in April. https://forums.fogproject.org/topic/10005/your-database-connection-appears-to-be-invalid/9
I see Tom had responded and said it was a problem overnight when this happened back in April. Just wondering a little more on how program works. I understand the program to work where we download the new version OS version to server and is on premise and no updates or changes are made by anyone at FOG until I download newer versopm. Maybe I am wrong and that is not how works and with updates etc can affect my on premise server. Just maybe a lot of people were having this issue overnight and then had to do a reinstall or if developers/fog employees are working on version and changes were made it affects us. Nothing crucial just wondering if it is always something that breaks locally or if things can be affected by developers or fog employees. I can say nothing but great things and everything has worked great just wondering if way I am updating or installing affects how things work. Any info on this is great.
Pending Macs: It is safe to say just allow the Mac Addreses?
Also, if a command to use to just get 1.4.4 would be great also if that is what I need to do.
Yeah, 1.4.4 is current stable version (git branch called
master) and you should be able to update to that without much trouble like this:
cd /root/fogproject git pull git checkout master cd bin ./installfog.sh
I have had to reinstall 1.3.5-RC-11 a couple times because of database schema was wrong. Reason why this happens?
There is no way we could answer this question without having more information on what exactly was wrong. This is like asking your mechanic “My car didn’t work last summer, can you tell me what was wrong with it?”
Pending Mac Addresses
Clients using the fog-client software do report new MAC addresses to the FOG server. Those show up as pending. For example you get a new host, register that through the FOG menu as usual. Then when the fog-client comes up if does see that there is a WIFI NIC in that computer as well (just as an example) and reports that MAC address to the FOG server. Thinks like virtual network adapter from visualization software also causes pending MACs to show up.
Right now you are on the dev branch (i.e. RC11). If you want the latest stable version you need to do this.
git checkout dev-branch
git checkout master
1.5.0RC10 is the latest release and has several fixes for bugs that existed in 1.4.4. 1.5.0RC10 also has the new GUI interface (FWIW).