solved: update mysql.user set plugin=‘mysql_native_password’;

solved: update mysql.user set plugin=‘mysql_native_password’;

Fixed…

Fog Configuration --> Fog Settings --> Web Server

0_1496433184745_FOG Fix.PNG

@Junkhacker pigz !! this the error I had when I’m trying to deploy with Gzip otpion on the 1.4.0.

Thanks for this precision

@Wayne Workman

I have tried many solution to import my images from the old server to a new in 1.4.0 but nothing working.

I think the one solution is two deploy each image from the old server to a master and capture this image with the new serveur.

So I have testing this way it’s working.

Next just in case off I have created an other 1.4.0 server (yes 3 servers in the story) to test a migration between the two 1.4.0 servers with this process : https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG. All work fine.

Even if this was not the aim methode I serched to migrate my old images to the new, I think we can close this topic ?

Thanks all for help it’s very nice.

alt textGood news everyone !

One more time, FOG was not faulty but the NETWORK …
After checking again Forums on multicasting and similar problems, I’ve found the solution :

The querier switch must have an IP adress on the subnet …

Once I’ve made the change, I tested a 4 client multicast session : total success !
So I tried with a classroom of 19 clients : in 30 min ( 1.5Gbps/min, max speed with 100Mbits connections ), all images were downloaded !

So, maybe it would be interesting for others to include these advices in the wiki or the troubleshooting Multicast page :

enable IGMP snooping on VLAN concerned in all switches

Choose 1 "master switch ( for me the all gigabit one under fogserver ) and make the following only for this one :

assign an IP adress to the VLAN in the switch configuration in the subnet range enable IGMP query on the VLAN verify the switch has Active Group Addresses Enjoy !!!

Thanks again at all the FOG team

@robe2conoby Just to be clear IT Admins should never directly touch/use the linux user called fog. This is not the web ui admin account called fog (unfortunate coincidence). The linux user FOG is 100% managed by the fog installer. If someone changes this account afterwards or uses the linux fog account for system management bad things will happen.

The next time the fog installer runs it will think that it has control of this account and will reset things back to what it needs, probably clobbering your configuration. Please don’t touch or change this account.

These things already work.

See this issue to follow the flow and understand more what was done.
https://github.com/FOGProject/fogproject/issues/120

@Tom-Elliott That did it. Thanks Tom!

@dustindizzle11 Great you got this hacked… 🕶 Thanks for letting us know! Marking this solved for now. Let us know if you run into another issue with this.

@VijayBomble images in the GUI must be defined. They are not automatically populated.

Can you give us more details? Does this happen on every machine you capture from? Can you give a screenshot of the error?

Nothing changed in regards to that. I suspect, however, it was related to a ton of “slashes” that made the query larger than it could be to actually perform the update.

@Sebastian-Roth You’re welcome …
For info, my switches are HP Procurve and I used these links to configure them !

https://community.spiceworks.com/how_to/26481-enable-igmp-on-hp-procurve

http://whp-hou9.cold.extweb.hp.com/pub/networking/software/AdvTraff-Oct2005-59908853-Chap04-IGMP.pdf

Now, Multicast is working properly : I imaged 3 clients at 1.4 Gb/min, next I will try 10 or more !

@Tom-Elliott The issue has been resolved. I downloaded 1.4.0 SVN6069 and that install worked.

It does not matter, I fully understand. But it helped me a lot, thanks again and congratulations to all the FOG team

@Joe-Gill said in PXE Boot Problems:

I can boot the same machine type from another segment of our network fine as well.

For the first picture: So why should it be an iPXE issue then? This sounds really weird. Is this issue reproducible?

For the second picture: I suppose this model does not properly PXE boot in a different network segment, right? As George said, try different iPXE binaries (find them /tftpboot on your server) to see if one of them works…

@quinniedid There is a .msi version of the client that you could use to install the newer client with the correct address. Unsure if old client would need uninstalled first.

If you have a way to push out a PowerShell script, something like this might help.

$FOG = Get-WmiObject -Class Win32_Product | Where-Object -Property Name -EQ 'FOG Service' $FOG.Uninstall() $url = "http://<ip address>/fog/client/download.php?newclient" $outfile = "FOGService.msi" (New-Object System.Net.WebClient).DownloadFile($url, $outfile) $ArgumentList = "/i $outfile /quiet USETRAY=""0"" WEBADDRESS=""<ip address>"" WEBROOT=""/fog"" /norestart" Start-Process -FilePath MSIEXEC.exe -ArgumentList $ArgumentList -Wait Start-Service -Name FOGService Start-Sleep -Seconds 2 Restart-Computer -Force

Of course first you need to create the group itself.

From a php script this could be done with:

<?php require('/var/www/fog/commons/base.inc.php'); FOGCore::getClass( 'Group' )->set('name', 'SomeNameToNameThisGroup') ->addHost(array(1,2,3,4,5,6)) ->save();

Of course change the array(1,2,3,4,5,6) with the list of ID’s you need to associate to the group.

It sounds like the drives are on separate virtual machines in which case you need to install fog on the second one as a storage node. Not sure how current this is but here is a video about it https://youtu.be/X72WthDGwsw.

@Tom-Elliott @george1421
Ah, so simple! Thanks very much gents!