@RipAU said in After update of Fog Trunk - PHP Errors:

Hopefully its ok I am loading this thread up with screenshots of issues?

It’s perfectly fine as long as it’s related to FOG.

@Jbob
Setting the “runwith” to cmd.exe did work to run it. Thanks for the help.

That makes sense, but why did it run the first time and not the second time then? Both times it was a batch file, with no “runwith” specified. Obviously it did not run correctly the first time, but it didn’t give an error. I know I run bat scripts quite often with FOG and don’t set the “runwith” argument. I guess I am going to definitely start adding it in as it can cause issues at times.

Thank you, I updated and the client is back. However, I am still unable to get the service working due to that same “invalid host certificate error”. I will start a new thread for that.

@Sebastian-Roth @george1421

I’ll try to get a video/screenshots of the situation shortly.

As far as trying an updated FOG and/or a custom kernel… I’ll add it to my queue, but it may be a while before I can get to it; I’ll try to keep you posted.

@Tom-Elliott, @Sebastian-Roth all working! 🙂 🙂 🙂
The image already is deploying!

Thank you guys!
Solved!

@K.Hays said in Fog: multicasting across subnets:

That’s awesome actually i didn’t know that. How many computers can fog do max in this way, do you think?

As many as you wish. I limit mine to 2 to keep things moving along quickly - that way no computer takes hours, but each one takes about 5 minutes and they take turns. This is also easier on the server’s HDD as well.

For image deployment to many hosts at once using unicast, the server’s HDD speed is critical, along with it’s network speed. The switch’s internal throughput is also important.

Also Confirmed.

@ch3i
Salut !
Ecoute ce matin ça fonctionne en upload/download, je ne sais pas comment.
J’ai toujours le message d’erreur “Device busy” à l’upload mais ça passe outre et ça fonctionne…

@Wayne-Workman
Still have the error, after redefined storage node 😕

@Wayne-Workman
Yeah i know my setup is not a regular configuration, but now it works with nfs server on windows , in upload / download. As you know there are more chances to encounter a problem in upload… ^^

@martinm Using postdownload scripts might be an option (depending on what things you wanna change). Just give it a try, it’s not hard. Search the forum and you will find an example. Regarding IP and hostname change you can look into this or give it a couple more days till the new client will be available on linux (which would give you even more options like running snapin tasks on the clients!).

@Sunks said:

they should all get DHCP during the PXE boot…

Definitely if your network setup is fine. Maybe give us some more information. Spanning tree? VLANs? Clients in different subnets?

As well, please let us know which errors you see on the clients when they fail to PXE boot! Post a picture or send us the exact error code you see.

@Tom-Elliott Yes, it is
00:0c:29:bf:57:4a
If you don’t mind, could you teamviewer and check ? Thanks!

@Sebastian-Roth
Yeah, i understand. Trust me i tried to do a lot of times, analyse logs and permissions and work on issues with an unix professor but we don’t found for NFS…
No problem, still working!

@Wayne-Workman Thank you!! That modification worked.

Good news, I have my 1.2.0 Fog server up again. After building my own ipxe kernel most of my machines can pxe boot properly. I used the bios and uefi @Sebastian-Roth made in that post and both seem to work. Its not asking me for the tftp IP any more and just registered/imaged/deplayed a few machines 😄

Download kernels pre-made just for FOG.

I would not advise replacing the inits - as the new inits would likely break everything in 0.32.

There is a guide on how to do that here:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

@Wayne-Workman It already is, if you update.

A cool little way I track what is going on for the clients when that is happening (That @Tom Elliott showed me )

Open powershell and type: get-content -wait C:\fog.log (or wherever you have the log stored.)

this will let you see what it is doing while it is doing it. Depending on the error it can lead you in the right direction.

@Wayne-Workman

Hi,
I tried to follow this procedure 3 or 4 times, it never worked… 😞
i got blocked when trying to access /images2, IO error everytime!

So i wanna try everything else to export fog storage…