Registration and deployment problems
-
I think the easiest way might be a new install since what I have isn’t working anyway. Do you think my old images will still work? its not a big deal to upload new ones, just curious. I’m gonna try setting up a new VM with 14.04 and 1.2.0. Being a VM shouldn’t be an issue right?
-
@jcook if you have images from a 0.32 install, they can work with newer versions of fog. you’ll just need to enable a couple legacy support settings. many of us run fog servers in VMs.
-
Thanks for the response, just wanting to make sure I get my ducks in a row before I got started. Once I have the server up and running I will report back.
Thanks
-
@jcook VM is no issue. I run all of my fog servers as VMs.
You can run fog 1.2.0 if you wish, or just install the FOG trunk version directly on the ubuntu system. I would recommend that you not upgrade but start with a fresh FOG system and then import your images. You will have to reregister all of your workstations. If you have a couple of hundred systems maybe we can work on an import process to save time. Its cleaner because of the differences between the two environments to just start over with a clean system.
Make sure you allocate enough space for all of your images in the new environment. FOG itself doesn’t use any more (real) space. But your images and snapins do.
-
I have FOG 1.2.0 installed. I use to go to “myfogservername/fog” to access the UI. Now when I navigate there I get 404 not found. if i just go to “myfogservername” it gives me the it works message. Any thoughts?
-
@jcook Is it 404 or 500? There is a significant difference.
-
Its a 404.
-
I restarted the install the fog files were missing. Seems to be good now…not sure what happened.
-
After the 2nd install I rebooted the VM. When I try to go the web UI now it asks me update the schema, but when I do it fails. I think the database was already there and now there are issues. Since I have moved beyond my original question should I just start a new thread?
-
Sorry for so many relies, seems to be an issue with mysql, after a restart of the service I’m able to log into the web UI.
