Invalid Multicast session

[rbaldwin]

Okay, I’m able to multicast with FOG using the version of the FOG software(1.3 RC 13) a colleague who could multicast has.

All the following were done as root, by first using the command “sudo -i” to become root.

1. I stopped all the FOG services.

Find the FOG services:
ls -lah /etc/init.d/FOG*

Stop Them:
service FOGImageReplicator stop
service FOGMulticastManager stop
service FOGPingHosts stop
service FOGScheduler stop
service FOGSnapinReplicator stop

2. I deleted the fog user
   deluser fog

Uninstalled FOG using these instructions:
https://wiki.fogproject.org/wiki/?title=Uninstall_FOG

3. Finally I removed the /opt/fog folders and /etc/fog and /var/www/html/fog
   rm -f -r /opt/fog
   rm -f -r /etc/fog
   rm -f -r /var/www/html/fog

4. Then I went to my git checkout path, where I have FOG git repo and checked out the commit a college has that can multicast.
   cd /root/fogproject
   git checkout 249cda491927fff27967cf9c5b8cb371b49837d0

5. Finally I reinstalled FOG
   cd /root/fogproject/bin
   ./installfog.sh

When installation finished I now had FOG 1.3 RC13, I was able to create a multicast task. When the task was started it showed up on the Task Scheduler> Active Mutlicast task screen and as a process.

ps -ef | grep udp-sender

Output:
root 21694 18671 0 11:04 ? 00:00:00 sh -c cat /images/baseW5xxwin764vmw12Aug2016/d1p1.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 600 --portbase 64654 --full-duplex --ttl 32 --nokbd --nopointopoint;
root 21696 21694 0 11:04 ? 00:00:00 /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 600 --portbase 64654 --full-duplex --ttl 32 --nokbd --nopointopoint

I then booted a host and the multicast session started without any issues.

[Tom Elliott]

@rbaldwin Now can you try upgrading?

I’m thinking older remnants (unbeknownst to all of us at this point) were causing the issues you were seeing to begin with.

[rbaldwin]

@Tom-Elliott

I’m hesitant to upgrade now that it’s working. Maybe Monday. I did try fresh installs of both 1.3.0-RC-15 and1.3.0-RC-16 during this process without any luck resolving the issue. Only a fresh install of RC13 resolved the issue.

[Wayne Workman]

I’ve just confirmed that Multicast works fine in RC-17.

[rbaldwin]

This post is deleted!

[rbaldwin]

@Wayne-Workman

Was anything changed in how FOG starts the udp-sender between RC15,16 and 17? You did a fresh install of RC17 on Ubuntu 14.04 and were able to create a Multicast task? And use that task to image a system?

[Tom Elliott]

@rbaldwin The issue, as I see it, is what is to be considered “fresh”.

Your other “fresh” layouts, to my knowledge, didn’t clear out all the other stuff.

[Wayne Workman]

I just used my pre-existing FOG setup at home to test it, I’m using CentOS 7. The commands involved in multicasting don’t differ from one OS to the other though. They all use udp-sender.

The way I just tested is, I put one host in a new group, then through Group Management I picked that group, picked Basic Task, and chose multicast. Then I confirmed the task. The task showed up in Task Management, the host automatically turned on via WOL, and was able to start laying the image on the disk via PartClone just fine.

I also confirmed that udp-sender was infact being used by watching top, udp-sender would be the top-consuming process in top while Partclone was going, and between partitions it’d drop down off the list.

[rbaldwin]

I was able to upgrade to RC19 and am able to multicast still. So this is resolved.

[LJedi]

I am seeing the same issue with a fresh install of Ubuntu 16.04 and RC19. Any suggestions?

[Wayne Workman]

@LJedi What is the output of command -v udp-sender ?

[LJedi]

@Wayne-Workman here is the output /usr/local/sbin/udp-sender

[Wayne Workman]

@LJedi Can you look through this? https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast

[Tom Elliott]

Found the secondary issue of the “multicast session is invalid”.

Basically I missed one point by not including a space where it needed one.

This is now (properly) fixed and patched up so people doing fresh installs will be fine, and people doing upgrades (that had the issue originally) will magically be fixed when they install the latest (when rc 20 gets pushed).