Unable to upload images
-
@Tom-Elliott said in Unable to upload images:
@Doctrg If I had to guess you will need to run through:
Tom this always confused me, if this is an FTP issue why the heck is it saying can’t update the database. It would be really swell if it would complain about the real problem to help with debugging.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
@Tom-Elliott I just ran through this test on both Windows and Mac. Both succeeded without an issue.
-
@Doctrg The question is, can (from a windows machine or another linux server) you connect to the FOG server using a ftp client with the user ID and password listed in the storage node configuration.
The issue is there is a linux user called
fogthat is different than the webgui admin user calledfog. What we’ve seen is the linux userfog’s password gets out of sync with what is displayed in the master storage node configuration. -
@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.
-
@Doctrg Interesting, then this may be then what the error is reporting. If so I sit here with egg on my face. 99% of the time when this error is thrown the client can’t connect to the fog server via ftp to move the file from /images/dev/<mac_address> to /images/<image_name>
-
@george1421 I am also able to move, for an example, d1.mbr from the /images/dev/<mac> to /images/<imagefolder> using FTP.
-
@george1421 The reason it doesn’t say FTP is because there’s actually multiple actions that happen. If it’s not FTP (which sounds like it isn’t here) then it could be the Disk Space of the FOG Server.
The “Updating Database” is more of a “We have to do a bunch of actions and I wasn’t really thinking about all those actions when the init scripts were created so here’s your all or none type message”.
Seeing as FTP appears to be okay, there could be a permissions issue meaning if you run:
chmod -R 777 /images(Changing /images to your actual nfs image storage location) things should work.If disk space is the issue, then you’ll likely need to add more space or figure out what is eating it.
-
@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.
-
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.
-
Do you have multiple storage nodes?
-
@Tom-Elliott We have 3 other storage nodes.
-
@Doctrg Are you using the location plugin? If so did you drop it and reinstall it after upgrading to 1.3.0?
-
@Doctrg is there another master node?
-
@george1421 We are not using the location plugin, that we know of.
-
@Tom-Elliott We only have the 1 master node.
-
@Doctrg All three storage nodes are at the same location or subnet?
-
@Doctrg said in Unable to upload images:
@Tom-Elliott We only have the 1 master node.
As its defined on the master FOG server?
-
@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.
-
@Doctrg On the current system that you’ve tested everything, can you verify that the image is uploaded to the /images/dev/<macofuploadinghost> location?
-
@Tom-Elliott I can confirm that it does upload to that file location.
