This appears to be a networking related question vs a question about the application.

Previous poster is correct. Basically you would want to enable multicast on your layer 2 devices and perhaps on your layer 3. In general, you want to control where the multicast goes, so enabling is not the end of the story.

Removing the hook sorted it nicely. Thanks for that.

@boeleke Those are the fog server’s CA and private certificate for your specific server. They must remain in place for anything concerning the fog client to work. You should not bother them to create a snapin.

thanks guys for replay i was really busy to follow up the post
i will provide a photo soon as i restart the server next time

You may also find this helpful: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

@Cammy-Webster It’s fine. Part of being a moderator is being able to link to obscure threads 🙂

@JGeear There isn’t a call to shutdown the interface. The SIGTERM, Shutting down is the message that is saying it is shutting down.

Trinity rescue CD 3.4 : NOT WORKING : kernel panic

kernel http://IP-FOG/fog/service/ipxe/trinity3.4/kernel.trk || read void initrd http://IP-FOG/fog/service/ipxe/trinity3.4/initrd.trk || read void imgargs initrd.trk ramdisk_size=65536 root=/dev/nfs vga=788 trknfs=IP-FOG:/home/tftpboot/trinity3.4/ ip=dhcp splash=verbose pci=conf1 trkmenu timeout 100 || read void boot || read void

UDF-fs : No partition found(1)
No filesystem could mount root , tried ext3 ext2 ext4 cramfs squashfs vfat …
kernel panic - not syncing : VFS: Unable to mount root fs on unknown-block(8,1)

@Deimos Update to trunk and adding choices is MUCH simpler, as well as “cancelling” other tasks.

https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

The new client will not work with FOG 1.2.

If you want to use the new client, I’d highly recommend you upgrade to trunk.

https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

While I do understand hesitation of upgrading to an “development” version, I can assure you this version works with the new client as the new client and FOG where built together with a lot of collaboration between @jbob and myself.

@Quazz Kudos to you for knowing what the issue was.

@Tom-Elliott
Oh ok.
I updated the kernel to “Official Published Kernels
Kernel - 4.1.2 TomElliott” and it works!
i just don’t see the “TomElliottUSB” on the kernel i selected before…!

SOLVED 🙂 !

@Wayne-Workman i wasn’t really clever in browsing this forum with my phone, so I thought hey Google may just pop with the answer quicker but I will certainly use that link for my reference for future mishap.

Thanks bud (Y)

using the method wayne posted would give you the complete database, including the hosts and image info. if you didn’t want to do a complete database restore, you could pull the data you wanted from it anyway.

@Tom-Elliott Nevermind, I’m an idiot. I think I found it. I got it. I forgot to change your place holders. Please consider this issue resolved.

@Tom-Elliott said in FOG Issued Reboot Not Happening:

Task reboot not working properly should now be fixed properly. There’s a slight issue in the new client where the call it get’s to “recheck” for tasking it it calls a different url. That url wasn’t returning any data. A Hotpatch has been made that should correct this for you.

Thanks Tom!

Path correct , problem with & in the script and how it stored

@plegrand Any news on this?

Yes, you fixed it 🙂