UNSOLVED Trouble Copying Image to other Fog Servers

  • I am running Fog on 7 Servers with 3 nodes each on Ubuntu 16.04. I created an image at one site and it downloads fine but when I copy the image to another fog server it does not download. i used scp -r to copy the image from one fog server to another then I :

    sudo chown fog:root -R /images/Win7Masterv4
    sudo chmod 777 -R /images/Win7Masterv4

    Then I added the image name to the Fog server and tried to download it but it says the file does not exist. I don’t know if it is a rights issue or if the file is corrupt when I move it to one of the other fog servers but it just wont work. Prior 1.5.0 I never ran into a problem moving images between each server so I am unclear what broke.

  • Moderator

    @FlareImp I guess you need to elaborate a bit more on how your whole network is structured for us to be able to understand and give appropriate information.

  • @sebastian-roth said in Trouble Copying Image to other Fog Servers:

    ls -alR /images/

    Sorry, that was a typo, the name of the image is Win7MasterNoIEv4 on both the WebGUI and the Folder itself.

    Here is the output of the Node:

    total 8240392
    drwxr-xr-x 2 fog fog        4096 May 23 13:15 .
    drwxrwxrwx 7 fog root       4096 May 23 13:15 ..
    -rwxr-xr-x 1 fog fog     1048576 May 23 13:15 d1.mbr
    -rwxr-xr-x 1 fog fog     8512734 May 23 13:15 d1p1.img
    -rwxr-xr-x 1 fog fog  8428579682 May 23 13:19 d1p2.img
    -rwxr-xr-x 1 fog fog         190 May 23 13:15 d1.partitions

    The Fog Server:

    total 8240392
    drwxrwxrwx 2 fog root       4096 May 22 15:13 .
    drwxrwxrwx 7 fog root       4096 May 22 15:13 ..
    -rwxrwxrwx 1 fog root    1048576 May 22 14:46 d1.mbr
    -rwxrwxrwx 1 fog root    8512734 May 22 14:46 d1p1.img
    -rwxrwxrwx 1 fog root 8428579682 May 22 15:13 d1p2.img
    -rwxrwxrwx 1 fog root        190 May 22 14:46 d1.partitions

    I was able to delete the image from the node and let it sync through the FogImageReplicater service and it worked fine. The problem is I still do not have a way to copy my images to the main fog server at Site B from other sites. I have to pull the machine at site B and take it back to site A so it can upload the image directly then take it back to site B. I have 5 other sites that the image can be rsync’ed to and it works with no issues.

  • Moderator

    @flareimp Just read through this again an noticed that you wrote Win7Masterv4 in your first post but the screenshot says Win7MasterNoIEv4?!

    But thing is, if you had the name wrong it wouldn’t get as far as trying to write an image file to disk at all I suppose.

    Can you please post the output of ls -alR /images/ from a storage node and the master node on site B?

  • I took the Fog server from Site B to Site A and uploaded the image directly with no issues. I then took it back to site B and it had no issues deploying. I then reconnected Nodes 1, 2, and 3 to the fog server in site B, gave it time to replicate, then tried to image from the storage nodes. I received the same issue shown in the screen shot above.

  • @sebastian-roth it does not show any kind of blue screen. It shows the screen just before partclone takes off then goes to the error shown above.

  • @tom-elliott After that screen it just runs through the PostDownloadScript sequence then reboots and the task it removed from Fog as though it completed.

  • Moderator

    @FlareImp Usually just before that black “A warning has been detected” screen you have the blue partclone screen with valuable information on it. Can you try again and take a picture of that?

  • @flareimp it says warning does it continue after that? Warning should cause the imaging process to reset. If I had to guess there is an error after the warning?

  • @wayne-workman sorry, here is a screenshot. the odd part is I uploaded the image at 2 other sites and the image works fine. It still does not work at 3 other sites though. The image shows what each of them are doing. The Image name is Win7MasterNoIEv4 on both the folder name and the image name in the GUI. The name was copy-pasted so the characters all match.

    0_1525376989731_20180503_142743 (2).jpg

  • @flareimp The next step is to post a screenshot or photo of the error. A lot of times experienced fog users can see more in the screenshot.

  • @wayne-workman the image path and image name are both identical.

  • @flareimp The image path is case sensitive. Set this correctly via the web interface -> image management.