FOG 1.5.4 Multicast sessions immediately end.
-
@sebastian-roth here is the other thread. https://forums.fogproject.org/topic/11799/1-5-2-on-debian-multicast-session
-
I just made a new server with a new fog install and I have the same problem
Where can I find a copy of FOG that didn’t have this issue; because it’s the main reason we use it for imaging. We have 2000 machines to do.
Unless it’s somehow the image file? Does anything in the image capture change between versions?
-
@solkre Mind checking out the working branch? I’ll like to know if my refactoring of the multicast code will help you out here.
I was aware multicast sessions being a PITA, and I had already refactored for 1.6. It was a tedious process to try to do the same for 1.5. I’ve been busy. I decided to attempt correcting the issues with 1.5 based code using the refactorization used in 1.6. I did some very basic testing and things appear to be working. I did not test normal multicast at all, just the session style MC tasks as that is what I was aware of as being broken. -
Just chiming in here that I also have this problem with a new FOG server install. Multicasts instantly end as soon as they’re started. For me not a huge issue, as I’m usually only imaging 20ish computers at a time, but it’s definitely not a problem isolated to @Solkre.
Philip
-
@flipwalker Can you try the working branch?
-
@tom-elliott Since I just rebuilt one of my physical machines(thanks unnamed agency for delaying my harddrive order for 3 months and causing my RAID to fail) I can probably throw up another virtual server and try the working branch. Never used it though, get it through Github also? If I clone my current VM, can I just upgrade it with the working branch?
Philip
-
@flipwalker Yes.
The instructions are here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG#Getting_FOG
The
git checkout dev-branchwould be changed togit checkout working -
Sounds good. I’ll get working on that and let you know what I find.
Philip
-
@tom-elliott Here to report that the working branch appears to have fixed the issue. Currently have two clients imaging off of a multicast.
As a continuation of this: Are there any known things you’ve broken in the working path that means I shouldn’t just update my production server with it and have the added ease of functional Multicast?(Yes, I understand its the working path and no promises can be made, just asking if there’s any known issues.
Philip
-
@flipwalker as this is the only change I think you’re okay.
-
@tom-elliott Updated the production server and it is now multicasting. As a side note though I tried to start a ‘test’ session of multicast, the same name I had used pre-update, and it did the same thing(started and instant ended). But if I picked a new name that I hadn’t used before, it appeared to start and wait for connections normally.
Philip
-
This post is deleted!
