Unable to upload images

[Doctrg]

@Tom-Elliott No, I’ve been getting the update using:
sudo -i
wget http://downloads.sourceforge.net/project/freeghost/FOG/fog_1.3.2/fog_1.3.2.tar.gz
tar xzf fog_1.3.2.tar.gz
cd fog_1.3.2/bin
./installfog.sh

[Tom Elliott]

Try this please:

wget --no-check-certificate http://mastacontrola.com/fog_1.3.4.tar.gz
tar xzf fog_1.3.4.tar.gz
cd fog_1.3.4/bin
./installfog.sh -y

[Doctrg]

@Tom-Elliott This fixed the reboot/join issue. Thought I’d mention that it did not fix the upload issue as forecast.

[Tom Elliott]

@Doctrg Okay,

I’ve updated the code base in an attempt to have it print out the actual so we could further see how to help you out.

You will probably need to remove the old installer folder.

you could ensure all is well if you cd to /opt first.

Possibly the steps would look like:

cd /opt/
rm -rf fog_1.3.4
wget --no-check-certificate http://mastacontrola.com/fog_1.3.4.tar.gz -O fog_1.3.4.tar.gz
tar xzf fog_1.3.4.tar.gz
cd fog_1.3.4/bin
./installfog.sh -y

Cancel the current upload tasking if you haven’t already.
If you can run the capture task again but select the “Schedule as Debug before confirming” boot the system you’re trying to get the image from.

It will ask you to press [Enter] twice. Then it will drop you into a shell.

From there you can run:
fog

You will have to press enter a bunch of times, but it should allow us the time we need during the completion of the upload that is currently failing.
It also means you don’t have to try to beat the clock to capture the picture.

[Tom Elliott]

Once you get the picture, please post it here so we can be of more assistance.

[Tom Elliott]

@Doctrg I’ve added a enabler/disabler feature set to the working-1.3.4 branch. This feature set just allows you to check a box in the FOG Settings that tells us if the service is allowed to run or not. The master daemon of the service is still running, and will still checkin based on its sleep time.

[Doctrg]

@Tom-Elliott I hope this is what you were looking for.

[Tom Elliott]

@Doctrg Now press enter and you will see a TON more information please post that pic too?

[Doctrg]

@Tom-Elliott Here ya go.

[Tom Elliott]

Mind trying:

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

Also, is somebody in a terminal sitting in /images/LABNURS236?

If somebody is cded to the directory it would also explain why it’s unable to remove/move things. The folder is “busy” and can’t be removed.

Another test of things might be to run

chattr -i /images/LABNURS236

[kibade]

@Doctrg Might be worth trying https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Try_to_get_a_file_with_Windows:
I found my fog user password had changed, showed up on a simple ftp open test.

Also under storage management on the web GUI, double-check your paths.

[Doctrg]

@Tom-Elliott I did some poking around last night and I changed a couple of things. The first thing I changed was in my .fogsettings. My default and one of my storage nodes did not have the username= entry. I added that and instead of “username” “password”, changed the quotes to apostrophes ‘username’ ‘password’. This gave me a different error this morning, which I did not expect so I did not capture the error. However, the error pointed saying that the ftp location did not exist. So I went into the Fog Settings through the web gui and saw that ftp path on all of the storage nodes was set to \images. I changed that to \images and I was able to get my capture task to clear out and the uploaded files are in the correct image folder and not sitting in dev.

[Tom Elliott]

@Doctrg I think you’re trying to say you changed to \images to /images?

[Doctrg]

@Tom-Elliott Sorry, no. I changed it from double \ to a single \ .

[Tom Elliott]

@Doctrg Why are there backslashes? Is the images location on a windows server? For FTP, even on windows boxes, the slashes should be / not \.

[Doctrg]

@Tom-Elliott Whoops… You’re right. They are forward slashes.

[Tom Elliott]

@Doctrg So FTP is a fickle creature. Linux, itself, doesn’t care about //images vs. /images but FTP apparently does.

This shouldn’t occur on new installs, though I can’t guarantee it won’t.

Is it then safe to solve the thread? You’ve provided all the details for others to look for and show that things appear to at least work for now.

[Doctrg]

@Tom-Elliott I believe everything else is working fine for now.