Just wanted to drop a line and say that the image type doesn’t have any bearing on how FOG Image Replication works.

@kevin-talbot Basic troubleshooting dictates that we first check if this problem affects other images. Do you have other images you can try to deploy to see if you get the same problem?

I’ve seen this several times. When the write rate starts to slowly drop down to nothingness, that means that the transfer has actually stopped. It stopped the moment the speeds started gradually declining. The displayed write speed is just an average, not actual.

Following along with what Tom said below, you just need to write a postdownload script to do the work you need done. Get started with that here:
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script
Try your best to do it yourself. If you need help, ask here.

@christian99x For OS compatibility, the manufacturer has only listed Windows: https://www.asus.com/ae-en/Motherboards/P5W_DH_Deluxe/specifications/

I would start this troubleshooting by seeing if a Ubuntu live disk will even boot with this motherboard.

@oasis All snapins run on windows as the SYSTEM user, and all snapins run on Linux as the root user. If your script runs manually but not through FOG, this generally means your script has issues running as SYSTEM.

@christian99x What is the make/model of the host?

7mb/min is like crippled turtle speed. I think you meant Gb/min. Also you didn’t give us any of the details we always need, like FOG Version and host model. What makes you think anything is even wrong? Does the capture complete?

@sourceminer Depends on what you’re referring to. If you make a master into a non-master, you can then make another non-master into a master. And I don’t see any problems with changing what location a storage node is assigned. Perhaps you should give us some more details about the problem.

@fall711 said in FOG offline installation:

The problem is that centos repo system use random host with different IP address and some are not allowed.

You can easily specify exactly what mirror you want to use by commenting out the mirrorlist directive inside of all the /etc/yum.repos.d/*.repo files and instead using the baseurl directive. Here’s a writeup on it, there are many others online too:
https://www.centos.org/forums/viewtopic.php?t=20390

Just pick a mirror nearby you, and explicitly define that. You will need to do the same for the remi repository as well:
https://www.centos.org/download/mirrors/
http://rpms.famillecollet.com/

There is never a problem that cannot be solved.

@michalm This is great, I think you’ve found and solved a known-bug. Can you submit a pull request with the changes to the FOG working branch on github please? https://github.com/FOGProject/fogproject/tree/working

@redbob Do you have any post-init scripts?

@redbob Does the image deploy OK? The field you are referring to is called ‘Captured’ and that’s just a datetime in the DB, and shouldn’t have any impact on functionality.

@redbob I’ve updated the wiki to include details for creating a user in FOG in 1.4.0 and 1.5.0. Future readers can find that information here: https://wiki.fogproject.org/wiki/index.php?title=Password_Central#Web_Interface

@redbob Then create a new user as I suggested in the below post, it should not have any restrictions on it since it’s a new user.

@redbob Then you probably need to delete the FOG user and then recreate it via SQL. The commands for that should be:

mysql -D fog
DELETE FROM `users` WHERE `uName` = 'fog';
INSERT INTO `users` (`uName`,`uPass`,`uCreateBy`,`uType`) VALUES ('fog','$2y$11$g0Hu8OaOStuPk7WWYGh6Wu4PLlZDZGOkzMwEEAk.rZMrI9IdDwno.','localAdmin','0');
quit

Alternatively, you can create a brand-new username bob like this:

mysql -D fog
INSERT INTO `users` (`uName`,`uPass`,`uCreateBy`,`uType`) VALUES ('bob','$2y$11$g0Hu8OaOStuPk7WWYGh6Wu4PLlZDZGOkzMwEEAk.rZMrI9IdDwno.','localAdmin','0');
quit

The password for those hashes is just password

@brian-david How large is the snapin file? Can you try to re-upload it to the fog server please? You should be able to ‘edit’ the existing snapin and browse to the file via the GUI and click save, which causes it to be re-uploaded. Also - after you re-upload, check the size of the snapin on the FOG server with this command: ls -laht /opt/fog/snapins

@brian-david Can you check to see if that file exists? C:\Program Files (x86)\FOG\tmp Also, can we get more of the fog.log file?

@redbob Also you might try this: https://wiki.fogproject.org/wiki/index.php?title=Password_Central#Web_Interface

@redbob said in Cannot enter FOG Web Interface: “Not Allowed Here”:

I cannot access Ondrej repository due to firewall issues!!!

You should request that the site be allowed. This is an open source repository for used for Linux package install and patching purposes - there’s no reason to block it.