Missing fogsettings file path forward
-
Debian 8, FOG 1.2.0
I am not looking for an answer as to why the files is missing but what is the best path forward from 1.2.0 to 1.3.ish using git.
- I have a duplicate server, databse, etc. Confirmed working.
- foginstall.log and Config.class.php has values I recognize.
Only installation failure I see is * Starting FOG Multicast Management Server…Failed! - The server has been running since the original install when 1.2.0 was released.
- I can log into mysql with the user id.
- dhcp.conf backup, I do some Macintosh stuff.
Options
I am looking at recreating the .fogsettings with known data and runinng install. If I do this do I delete the Variables I do not know?
Would a migration be better? backup and restore of the database?
Call it quits and just build a new box. -
@Foaming My opinion would be to always build a new box and then copy over your images. This gives you the most up to date OS as well as a clean build of FOG.
-
@george1421 I second this notion.
I have a 32 bit Ubuntu 10.04 on FOG 0.32 that is moth balling at the moment.
I did clone the hard drive a few times with clonezilla and try to upgrade it… I spent FAR less time building a new server and importing new images. But I like to do things the hard way from time to time, just to see if it’s possible.
I did get the operating system upgraded fine. The move from x32 to x64 left a lot of things broken (packages wouldn’t install, etc.) and I couldn’t get to the images via pxe or web gui.
It seemed to work fine before I moved from x32 to x64 when I upgraded 10.04 to 14.04, but I digress: If you moth ball the server, you have something to fall back on in a pinch.
-
@Jaymes-Driver said in Missing fogsettings file path forward:
If you moth ball the server, you have something to fall back on in a pinch.
This right here is the key. If an upgrade fails you have to either rebuild the server or revert to a previous backup. If you spin up a new server you have your legacy fog server available if things go sideways as you’re getting the new server up and into shape.
-
Thank You. Was hoping for the waving of the magic wand. We have been using FOG way back to FOG .20ish days. Was on .32 forever until the server was a victim of a power surge. 1.2.0 is the replacement for us and have been using it since 1.2.0 stable was released. We are getting alot of XP and Vista boxes (University Environment). This is the primary driver for the newer versions. Current Vista images are not resizable images and the XPs were RAW/dd images.
I have worried over this more than it would take to build the new box. This is a xen host and I have a functional guest VM of FOG 1.2, a verified copy of that guest. So I will give this post a few days and proceed with creating a mockup of the .fogsettings and upgrade because the worse thing that can happen is that I will learn something:) As all of us, time is limited. I do have student labor and should turn them loose on building new servers for their experience.
-
@george1421 and @Jaymes-Driver fyi, this is what I’ve been referring people to: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
It’s step-by-step procedures for moving from an old server to a new one using the most linux-noob friendly methods I could think of, and has links throughout it to other relevant resources.
-
Update, I created the .fogsettings file and updated. It would not let me update the schema so I added the MySQL credentials (instead of leaving them blank) and update was successful. Things, host, users, images, etc, look good from the FOG webpage. I will do some testing next week. This is a XEN guest so I have copies. We have not imaged yet, (purpose of upgrade was for XP and Vista imaging). DBAN errors out with a chaining error, we use HTTP to load DBAN. I will do some testing next week.
Thank you for your help. In our environment starting from scratch is easy but then we would not be as familiar with our install.