Fog download image fails

[wlsnfmly]

@Jaymes-Driver The problem is that the file doesn’t exist. In checking the /bin folder for a file called fog.download, there is nothing there. nor is there a fog.upload folder either.

[Tom Elliott]

@wlsnfmly The fog.* scripts exist in the init’s not on your physical fog server.

He’s referring to your images directory though in regards to permissions.

Please run (on the fog server):

sudo touch /images/.mntcheck
sudo touch /images/dev/.mntcheck
sudo chmod -R 777 /images

[wlsnfmly]

@Tom-Elliott Did that, no luck, here is a screen shot of the error we are receiving.

[george1421]

@wlsnfmly In addition to what Tom posted. From the fog server I would run the following command to confirm the nfs shares are in place showmount -e 127.0.0.1 The output should show you both /images and /images/dev

<edit>Based on your last post, I’m more interested in seeing the output of the showmount command than before</edit>

[wlsnfmly]

@george1421 It does show both directories.

[george1421]

@wlsnfmly Well that explains a bit more of what is going on.

On your FOG server you have /images and /images/dev shared.

But your error message says the client computer can’t connect to 10.1.20.127:/storage1 (you are trying to connect to the /storage1 share on the device 10.1.20.127)

What is the host 10.1.20.127?

[wlsnfmly]

@george1421 that is my fog servers ip address

[george1421]

@wlsnfmly Ok then, please tell me why the client wants to connect to <fog_server_ip>:/storage1 but you only are sharing <fog_server_ip>:/images and <fog_server_ip>:/images/dev from your fog server?

It sounds like you made a change to the fog server’s storage node settings. What were you trying to accomplish. (your answer will help us pick the best path for you).

[wlsnfmly]

@george1421 I didn’t personally make any changes during the upgrade. However, I did upgrade from 1.2.0 to 1.3.4, would that have caused the issue? is there a quick fix? the permissions on storage1 show 777 and images are the same

[george1421]

@wlsnfmly So you have a directory off the root of your fog server with /storage1 and /storage1/dev names?

Could you post s screen shot of these commands?
ls -la /
ls -ls /storage1

[wlsnfmly]

@george1421 Here are two images to check. One shows why it is looking for those files, from the fog config page. The second is the one you have requested.

[george1421]

@wlsnfmly Switching to chat, look at the little speech bubble up by the FOG tool tray at the top of the browser window.

[george1421]

@george1421 Might I ask you to post the output of this command too?
df -h I want to make sure that /storage1 share isn’t being used for something else.

[wlsnfmly]

@george1421

[george1421]

@wlsnfmly Ah ok, just a suspected. You have your images on a different drive than where the OS is stored (that is a good thing).

To fix your issue then: edit this file /etc/exports

Change the 2 lines in there from /images to /storage1

So your lines should look like this:

/storage1 *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/storage1/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

Save the file then run this command: sudo exportfs -a
Then confirm that the shares have been changed with: showmount -e 127.0.0.1

The shares should have now changes from /images to /storage1

If that is the case then restart imaging your target computer.

[wlsnfmly]

@george1421 This has fixed the issue at hand. Thank you for your assistance.

[george1421]

@george1421 If this all proves out to work there are two last things you need to to.

1. Edit the file /opt/fog/.fogsettings There is a line in there called listed as

storageLocation='/images'

You need to change it to:

storageLocation='/storage1'

Then run the installer program again (once your imaging is complete). That will just realign everything for you. When the update is done, reboot the fog server. When the fog server comes up reconfirm that showmount -e 127.0.0.1 still shows your /storage1 share as being shared.