@Tom-Elliott Ok. I was able to manually delete the folder. I then had a spark in the brain to try something. I created a new image and unchecked replicate image. It was able to upload the image correctly. I then put the check mark back in to replicate the image and it failed. So it seems that since we are not replicating our images we should uncheck that because it seems to be the issue.

@Tom-Elliott I’m not trying to change those images and they are on one of the other storage nodes. There’s the option in the Image Management to set the image as Protected.

@Tom-Elliott No, but there are 2 images that I have set to locked to make sure no-one else can make changes or delete them.

@Tom-Elliott 0_1484688152981_error_log I’ve attached the error log, however the access log has not been modified since June 2016.

@Tom-Elliott Unfortunately I’m getting the same failure after running chown -R fog:root /images.

@Tom-Elliott I can confirm that it does upload to that file location.

@george1421 We have the 1 master node and 3 storage nodes on different subnets. At the moment we are trying to fix uploading to the master node and then we will update the other storage nodes from 1.3.0 to 1.3.2.

@Tom-Elliott We only have the 1 master node.

@george1421 We are not using the location plugin, that we know of.

@Tom-Elliott We have 3 other storage nodes.

I do want to mention that this started last week when we went from 1.2.0 to 1.3.0. If that has any merit.

@Tom-Elliott said in Unable to upload images:

I just ran chmod -R 777 on /images and tried to upload. I got the same results. It’s not a storage space issue due to 1.58 TB available and the image being uploaded is about 30 GB.

@george1421 I am also able to move, for an example, d1.mbr from the /images/dev/<mac> to /images/<imagefolder> using FTP.

@george1421 I was able to connect via FTP from Windows using the fog username and the same password that is showing in the storage node configuration and the password is showing to be the same in the .fogsettings file.

@Tom-Elliott I just ran through this test on both Windows and Mac. Both succeeded without an issue.

I just did the update to 1.3.2 and tested uploading the image again. I am still getting the attached results.

Server

• FOG Version: 1.3.0
• OS: RedHat
  *SVN: 6050

Description

We just updated to 1.3.0 last week and we are having issues uploading images. I am getting the attached image error when the imaging process is trying to update the database. We have checked the permissions and all username/password fields that we know of and everything looks like it should be working.

Forgive me if this has been answered, but I am trying to put together a silent install to push out to all of my lab computers the new client. I saw a link in a previous discussion, https://portal.fogproject.org/projects/fog-client/wiki/Command_Line_Installation, but the link is not working. I also noticed that the new client is not using the method of a config.ini file like the legacy client uses. Are reboots now forced without having to edit the ini to set it to force reboots?