Invalid Multicast session
-
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.
-
I’ve just confirmed that Multicast works fine in RC-17.
-
This post is deleted! -
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?
-
@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.
-
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. -
I was able to upgrade to RC19 and am able to multicast still. So this is resolved.
-
I am seeing the same issue with a fresh install of Ubuntu 16.04 and RC19. Any suggestions?
-
@LJedi What is the output of
command -v udp-sender? -
@Wayne-Workman here is the output
/usr/local/sbin/udp-sender -
@LJedi Can you look through this? https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast
-
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).
