@WourN The installer should have taken care of it for you (but most people installing fog tend toward fresh which means they’re likely installing CentOS 7). Basically, those commands downloaded and installed the repositories FOG is supposed to be installing for you.

Nvm, I tried another kernel, Version : 4.1.2 and it worked.
Case closed

@lonnie776 while I am glad that youve taken the steps to find and correct a problem, I feel you may want to look at the latest fog has to offer. First we’ve, and by we I mean @Joe-Schmitt , rewritten the fog client and it is much more secure and less resource intensive on the server. As an overall result the client is much faster than the old client and has many more features to work with. I’d highly recommend updating and using this new client for any system.

Just to update you, I have just tested updating the image in fog 1.1.2 which uses part clone to capture and the progress bar is now working. 😉

Thanks for the help, appreciated. 🙂

That’s a possibility, but I think the best option for you is to chmod the /images folder.

Normal ownership of the entire folder is:

rwxrwxrwx

If you run as root user [code]chmod -R 777 /images[/code] it should work.

There is one other thing to be aware of is that the way the files move from /images/dev to /images is through ftp.

Make sure your GUI has the appropriate username and password under both of these options:

Storage Management->All Storage Nodes->{YOUR STORAGE NODE (usually DefaultMember)->Management Username and Management Password
AND:
Other Information->FOG Settings-> FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD

The username should be set as fog

The password should be set on the fog server as root user with:
[code]passwd fog[/code]

Then whatever password you set is inserted into the password fields.

ehm, it seems like we fixed it on our own.

The server was set up with DNS and gateway, which we really dont need since it is in local network.
We removed DNS and gateway from the IPv4 settings, rebooted the server and it is no longer delaying.

Thanks for the replies anyway!