Fog Upgrade Problems

[Tom Elliott]

@garysaxon Please run the git form.

sudo -i
cd /opt/fogproject
git pull
git checkout dev-branch
git pull
cd bin
./installfog.sh -y

[george1421]

@garysaxon Taking this a slightly different direction: What operating system is the FOG server using?

The commands you are using ARE the right ones. So the error message is not easy to understand. We need to look about for another reason.

Once you try Tom’s commands the next step is seeing what is in the .fogsettings file.

[garysaxon]

@Tom-Elliott

Same error with those commands

[Tom Elliott]

@garysaxon
What’s output of:

cat /opt/fog/.fogsettings | grep 'osid='

[garysaxon]

@george1421

I am using ubuntu 14.04

[george1421]

@Tom-Elliott OK, I think we got it going now.

We first tried to get it installed before lunch. The install was running super slow and the OP had to leave for a bit so we just let it run. When he came back the install failed and the fog installer failed to write the .fogsettings file.

So I deleted the installer logs and reran the installer. This time the installer ran to completion and the db schema was updated. We were able to log into the web console and I confirmed that the storage node was configured with the same password as we gave the installer. At this time fog appears to be installed and running correctly with all of the expected services up and running.

You may need to see if you can trap what was going on with the .fogsettings file. The file existed but was empty ( 0 ) bytes. That empty byte file is where I suspect the “Sorry, answer not recognized” message was coming from (nothing to parse).

[Tom Elliott]

I don’t know why .fogsettings file was 0, but this is certainly the problem. There’s 2 points where the “Sorry, answer not recognized” pops up.

First, if the OSID of the installer system is not available it will print the message and exit out as you saw.

Second, If the (Yes, No) wasn’t answered it would give the same thing.

[garysaxon]

@george1421 Hey George, this is Hamilton, on behalf of Gary, I work with him at this site. Although the management console comes up and you can log into it, we are having trouble pulling down images. We can register the host to the server and select an image, but the pc just reboots again. The last message it gives is “Attempting to deploy image, using partclone”

Thanks in advance,

-Hamilton

[george1421]

@garysaxon How was the image captured? It sounds like partclone is getting a file it doesn’t like so it just blows up.

After you get the “Attempting to deploy image, using partclone” is there any other message? Or does it just reboot?

On your fog server can you run this command and post the results here
ls -la /images/<image_name> You will need to replace <image_name> with the actual name of the image you are trying to deploy.

Also in that image directory there should be a file called d1.partitions can you run this command cat /images/<image_name>/d1.partitions and post it here.

And finally does partclone start at all? Does it get to a certain point and then blow up?

[garysaxon]

@george1421

*The image was captured using partclone

*It just reboots, there is not additional error message

*ls -la /images/SENIOR2017FINAL results:
"No such file or directory

*But when I run “ls -la /images/”…I see the list of images and i see SENIOR2017FINAL

*Partclone does not start at all

[george1421]

@garysaxon said in Fog Upgrade Problems:

*ls -la /images/SENIOR2017FINAL results:
"No such file or directory

Well this is going to be a problem. If you are trying to deploy an image and the files don’t exist then partclone is not going to be happy.

[Tom Elliott]

I would think something was either lost, or another disk/volume was mounted as the /images in the past.

THe Folder is not enough. You may need to re-capture the image first.

[garysaxon]

@Tom-Elliott There is an image inside the folder. It is named the same thing as the folder itself.

[george1421]

@garysaxon I sure would like to see the results of the following commands.

ls -la /images
ls -la /images/<image_name>

And then a screen shot of the image definition in the fog management gui.