It’s Ok ! i’ve added manualy the MAC adress and Hostname in FOG server under Create a New host and its done 🙂

Thanks you very much for your help 🙂

@chadman00 While I don’t like to jump right into capturing network traffic, I think its going to be the easiest way to understand if you have the filters setup right with dhcp.

place a target computer on the same subnet as your fog server and dhcp server for the best picture of what is going on then follow this tutorial: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Take that pcap and look at it with wireshark. Looks at the OFFER response from your dhcp server. Make sure the boot file name is correct. If you are lost looking at the pcap upload it to a google drive and share it as public and post the link here and one of us will look at it to see if your dhcp server is responding correctly.

The persistent groups plugin is most likely still working.

First, understand how it works.

It’s a simple trigger that’s generated but the trigger gets it’s template from a default host assigned to that group.
The template host name must be the same of the group’s name. In that host, you define your wanted group settings. Then, when you add a “real” host to the group, it will obtain the information in that group.

Ticket can be closed for me.
I’ve captured a completely new image, before doing so, I’ve shrunk the disk, just to make sure.
Deployment is now working as expected for me.
Thanks for your assistance.

I don’t know how we can possibly help you.

You haven’t told us what you’ve tried doing, what’s not working, or any thing. You give us, quite literally:

“I installed it, what do I do now?”

The best I can do is give you our User Guide, located here:
https://wiki.fogproject.org/wiki/index.php?title=FOGUserGuide

@Sebastian-Roth said in Fog 1.5.5 - Snapin replication loop:

dev-branch

Thanks!

is the drive encrypted?

@Tom-Elliott I just had a look trough the code and added debug statements. Looks like the $foglang array is being initialized with string values before language is being set (setlocale). Have you got an idea when language support fully worked? I mean it does work for many of the texts but it doesn’t for $foglang texts.

I am wondering if we should move the setlocale stuff from ProcessLogin to FOGPageManager. What do you think?

We need a bit more information to know where to start

What version of FOG are you using What version of the FOS kernels are you using What target hardware are you using (manufacturer and model)

If you manually register this target computer, then schedule a capture or deploy (doesn’t matter) but before you schedule the task check the debug check box then schedule the task. PXE boot the target computer and after a few enter key presses you will be dropped to a linux (FOS) command prompt. At the FOS command prompt key in lsblk then take a clear picture of the results and post them here.

@jcabuco scenario 2: is your network or at least that port setup for STP? If so, can you enable rapid or fast initialization of stp, sometimes called port fast or rstp?

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 Please test the newly compiled 4.15.2 kernels you find here: https://fogproject.org/kernels/new/

Let us know if those help in speeding up the process and still don’t have the other rcu_sched stall issue.

Hi Sebastian,

It may take me a couple of days to get a response back to you. As soon as I can, I’ll do another upload and update you.

@PITSKing said in New FOG install, now can't find old image files in FOG:

If I get it wrong and it fails, can I simply edit the Image Type after the Image is created?

Yes you can! Compression level does not play a role on deploy but Compression type does, gzip vs. Zstd…

Upgrading the Kernel fixed this issue. I am not sure what version he upgraded to but I can now image these new computers. Thank you for your help @george1421

@dooleyrd We need the FOG log from one of the host’s failed attempts before we can tell you anything. It’s normally at C:\fog.log Please don’t snip a tiny piece from this file, but give us a whole client iteration - or the whole file.

@fenix_team Check for Apache errors that are written during an attempt to see logs via the UI. Also check free space on your fog server.
Also, just as a general rule you can re-run the fog installer when you have issues, it’s pretty good at fixing them. As always, I recommend a snapshot/backup before making changes.

Sounds good. Thanks.
I’ll give it a whirl and let you know the outcome / results. Apprec’ 😉

spanning tree, spanning tree la la la la la (jingle bells)
I’m saying this from 2 months 😄
I’m glad to read you saying it ^^

@lacaca Again, please post a picture of the error. We can’t help you otherwise.

Thanks @Sebastian-Roth