Multicast tasks not creating properly
-
Could you, possibly, try a newer revision.
-
Will do, I’ll post back when I get a chance.
-
We’ve upgraded to a newer revision (2774) and in testing it appears to be working properly. We haven’t used it in production yet but I don’t foresee it being a problem. Thanks again Tom!
-
Back to having the same issues in our labs today, multicast tasks from back in May popping up rather than the tasks we’ve created, tasks just hanging. The revision upgrade doesn’t seem to have fixed it.
-
Any words of advice? We’ve tried different images, different storage nodes, etc. and the same issue happens every time. We’ve been forced to unicast labs which can be a very time consuming process, obviously.
-
[LIST]
[]Newest revision is 2868. Please make sure you update then be sure that all old multicast tasks are killed. Then start a new task.
[][url]http://fogproject.org/wiki/index.php/Multicasting[/url]
[*]I don’t use multicasting but I will help muddle through it.
[/LIST]
To kill multicast tasks:
[CODE]sudo service FOGMulticastManager stop
sudo killall udp-sender
sudo killall udp-sender
sudo killall udp-sender
sudo service FOGMulticastManager start[/CODE] -
Attempted this but still no luck. The first multicast task in the attached screenshot is the one I just created, the second one is an old task from June that is completely unrelated (different location, image, storage node). The machines just hang at the first PartClone screen and go no further. If I kill the unrelated task most or all of the active tasks for that multicast are killed as well.[ATTACH=full]1593[/ATTACH]
[url=“/_imported_xf_attachments/1/1593_screenshot.144.jpg?:”]screenshot.144.jpg[/url]
-
Have you upgraded your version to be on the latest SVN as Wolf has suggested?
-
FOGMulticastManager does not start correct on server reboot (at least for me on svn 2756 or some previous svn numbers). I have to remember to stop/then start the service every time I restart my server. I’d love to to get a permanent solution for this.
[CODE]sudo service FOGMulticastManager stop
sudo service FOGMulticastManager start[/CODE](sudo service FOGMulticastManager restart will not do it).
-
Again, have you tried the latest svn?
-
My apologies for the delayed response, yes we are up to 2868 and same story unfortunately.
-
Can you afford to remove the old taskings?
(These commands will completely remove all multicast sessions and associations)
[code]truncate table multicastSessions;
truncate table multicastSessionsAssoc;[/code]Then kill all the udp senders that may be running on the server?
[code]sudo killall udp-sender
sudo killall udp-sender
sudo killalludp-sender
sudo service FOGMulticastManager restart[/code] -
I was able to run those commands this morning and now what is occurring is the systems in the multi-cast task are showing up in Task Management > Active Tasks momentarily and then they are gone, so they all boot onto the hard drive because there is no task for them. I’m not seeing the old multi-cast tasks like we saw before but the machines aren’t connecting to any tasks now.
-
Anything else I can try? I’m starting to get some heat on this and I would really rather not downgrade or start from scratch…
-
Do you have to use multicast? You can still create a unicast task (Download) using the group and deploy. Multicast is just a particular method of deployment.
-
We do have to use multicast, especially for our labs with 10+ computers. We are limited to resources for our storage nodes and our network where if we’re unicasting any more than 8-10 computers at once it takes way too long.
-
An update: multicast is now working again. Doing some digging into the logs I found error messages on the multicast tasks which revealed that there were brackets in the image folder name which udp-sender didn’t like. So to recap:
- Tom’s advice on truncating the multicast tables fixed the original issue.
- Removing the brackets from the image folder name fixed the second issue.
- I’m an idiot.
Thanks all for your help. Happy fogging!
-
Can you give us the example of your image folder path/name for future reference of this issue?
-
Absolutely, the folder name was something along the lines of:
\images\IMAGENAME(2015)
-
[quote=“Jacob Gallant, post: 40567, member: 26524”]
3. I’m an idiot.
[/quote]Hi,
How you solve this problem ?
Regards,
Ch3i
