Developers

@imagingmaster21 Ahh, now I get what you mean. Thanks for letting us know.

@imagingmaster21 Well we need more information to be able to help. Any error messages at the end when a client finishes?

So chatting with @Joe-Gill We narrowed down what the problem.

First, the backstory.

So Multicast tasks would work for some machines, but not all. And, to add to that, it was always the same machines that failed to work. If the machines that failed were subsequently put into their own group, they would multicast without issue.

This lead me to ask if the machines that would fail were on a different switch from the rest of the machines, and indeed @Joe-Gill found out that this was the case. They are using Meraki switches and they replaced a few of them. Those that were replaced do not work fluidly with the older switches in place.

@Joe-Gill keep me truthful here, but this is the gist of this information.

I’m assuming, for the log you posted, there were only 27 hosts in that group that needed the tasking?

Sorry for reasking the questions you’ve already answered, just trying to understand the whole situation.

@joe-gill So you’re saying some machines work fine, not all of them though?

Are you on the working branch? Can you show us the /var/log/fog/multicast.log file?

@joe-gill try setting the fog setti mg for multicast rendezvous to the up of the fog server you are expecting the data to be sent from. This isn’t a typical case for use of this but it has had to be used in a few environments.

@snaggel have you ensured selinux is set to permissive or disabled? Firewalls similarly?

@tneuber the fog.log typically resides on the root of the drive. I see you have it opened to program files, what about at c:\fog.log