• Register
    • Login
    • Search
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Solved Multicast Issues on Centos 7

    FOG Problems
    5
    61
    33235
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      BedCruncher last edited by BedCruncher

      I am having issues with getting multicasting to work. I am currently running Centos 7 that is patched and up to date. I have also went out and installed the latest FOG Trunk version (as of today) 7264.

      I can get it to start booting and doing the image restore, but it hangs on the partclone screen “Start to restore image” . Is there anything I can try to get this working?

      EDIT:
      I’ve also went in and modified the rc.local file as specified at FOG Centos 7

      EDIT 2:
      I am running a dual NIC configuration
      Em1 is DHCP
      Em2 is static set with address 192.168.240.10 and DHCP server on that interface

      1 Reply Last reply Reply Quote 0
      • Wayne Workman
        Wayne Workman @BedCruncher last edited by

        @BedCruncher said in Multicast Issues on Centos 7:

        @Wayne-Workman

        Using one of the links, can’t remember which. I was able to get the server and client to send using the udp-sender and udp-receiver. So I know they can talk, but I had to use the command.

        udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log  --ttl 32 --nopointopoint --interface em2
        

        if I dropped the last bit off then it would still try to grab em1 instead of em2.

        An example now exists in two different places in the wiki. I want to merge the articles but it will be an involved process to do that - I’ll get it done.

        For now, here are the two articles:

        https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast
        2.
        https://wiki.fogproject.org/wiki/index.php?title=Multicast

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        1 Reply Last reply Reply Quote 0
        • B
          BedCruncher @Wayne Workman last edited by BedCruncher

          @Wayne-Workman
          God, I feel like I’m crying wolf all the time now. I disabled the firewalld service and it was hanging there as before. I then ran the commands

          systemctl stop FOGMulticastManager
          killall udp-sender
          killall udp-sender
          killall udp-sender
          mysql -u root fog
          TRUNCATE TABLE multicastSessionsAssoc;
          TRUNCATE TABLE multicastSessions;
          TRUNCATE TABLE tasks;
          quit;
          systemctl start FOGMulticastManager
          

          I then tested it, and ran the multicast test. I again ran the commands to do all that above. I rebooted and ran the above commands again to ensure I was working clean and disabled the firewall and tested and so far it seems to be working. Please disregard.

          1 Reply Last reply Reply Quote 1
          • Wayne Workman
            Wayne Workman @BedCruncher last edited by

            @BedCruncher From the behaviour you’ve been describing - I no longer believe this is a firewall issue.

            Please just turn off firewall until we can complete troubleshooting with some sort of conclusive findings:

            systemctl stop firewalld
            systemctl disable firewalld

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            B 1 Reply Last reply Reply Quote 0
            • B
              BedCruncher @Wayne Workman last edited by

              @Wayne-Workman
              I will do that really quick, but it seems like it might be a different issue with firewalld now. I got it to work again if I ran systemctl restart firewalld.service after a reboot. then it would start the imaging seemingly consistently. For some reason the rules aren’t correctly applying at boot time.

              Wayne Workman 1 Reply Last reply Reply Quote 0
              • Wayne Workman
                Wayne Workman @BedCruncher last edited by

                @BedCruncher can you turn off your firewall and see if multicast works then?

                systemctl stop firewalld

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

                B 1 Reply Last reply Reply Quote 0
                • B
                  BedCruncher @Wayne Workman last edited by

                  @Wayne-Workman
                  I am not quite experiencing the same perfect results as @dvchuyen with regards to that firewall rule. I got it to work once, but since then it’s been extremely problematic.

                   firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -m udp -p udp -m pkttype --pkt-type multicast -j ACCEPT
                  

                  verified it was in there with ipdtable-save and ran firewall-cmd --reload and systemctl restart firewalld. This was to ensure that it was all properly in there and correct. I even rebooted the server to ensure that there wasn’t something in the network service that was gumming it up. I have also deleted the tasks out of FOG and manually triggered it again and still hang.

                  Wayne Workman 1 Reply Last reply Reply Quote 0
                  • Wayne Workman
                    Wayne Workman @dvchuyen last edited by

                    @dvchuyen I’ve updated the Fedora 23 and the CentOS 7 Wiki articles.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                    Daily Clean Installation Results:
                    https://fogtesting.fogproject.us/
                    FOG Reporting:
                    https://fog-external-reporting-results.fogproject.us/

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      BedCruncher @Wayne Workman last edited by BedCruncher

                      @Wayne-Workman
                      Sorry… I reread over what I had posted and it didn’t seem clear. The command above that I had ran was “supposed” to make it permanent, but failed to do so. I had to specify it statically in the NIC interface file. I will also double check the command you posted and test to see if it persists across reboots.

                      1 Reply Last reply Reply Quote 0
                      • D
                        dvchuyen @Wayne Workman last edited by

                        @Wayne-Workman said in Multicast Issues on Centos 7:

                        Yes, I confirm the command work. I found it and solved my problem few days ago.

                        https://forums.fogproject.org/topic/7194/could-not-pxe-boot-input-output-error-when-do-multicast/31

                        Wayne Workman 1 Reply Last reply Reply Quote 1
                        • Wayne Workman
                          Wayne Workman @BedCruncher last edited by

                          @BedCruncher If you find that the command I posted - or any command - allows you to multicast, I will immediately update all firewalld documentation we have in the wiki to reflect your success.

                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                          Daily Clean Installation Results:
                          https://fogtesting.fogproject.us/
                          FOG Reporting:
                          https://fog-external-reporting-results.fogproject.us/

                          D B 2 Replies Last reply Reply Quote 0
                          • B
                            BedCruncher @Wayne Workman last edited by

                            @Wayne-Workman
                            No, I hadn’t. The command I ran was

                            firewall-cmd --permanent --zone=trusted --change-interface=em2
                            

                            that was specified at this RHEL Firewalld page page. This seems to be this link firewalld.zones.

                            So I can change mine around and try it, but I wouldn’t have managed to do that particular one myself as I’m by no means a iptables guru. I will try to apply that tomorrow to test it out and let you know.

                            Wayne Workman 1 Reply Last reply Reply Quote 1
                            • Wayne Workman
                              Wayne Workman @BedCruncher last edited by

                              @BedCruncher Great find, try this?

                              firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -m udp -p udp -m pkttype --pkt-type multicast -j ACCEPT
                              

                              Source:
                              http://superuser.com/questions/837340/how-do-i-enable-set-multicast-rules-using-firewalld-in-rhel7-centos-7

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                              Daily Clean Installation Results:
                              https://fogtesting.fogproject.us/
                              FOG Reporting:
                              https://fog-external-reporting-results.fogproject.us/

                              B 1 Reply Last reply Reply Quote 0
                              • B
                                BedCruncher @Tom Elliott last edited by BedCruncher

                                OK!!! I think we have something here. So I finally figured out that part of the problem seems to be in the firewall zone as specified in the Centos 7 Setup guide. The issue I think stems from that the public zone seems to be blocking the multicast ports. I even explicitly told the firewalld daemon to add the interface em2 to the trusted zone, but it never did unless I manually specified in the NIC interface file ZONE=trusted. This seems to be a bug of sorts in that project.

                                I suppose that you could also specify a port range for the firewalld daemon to allow through. In my case the NIC hosting the FOG Server is segregated my other network. So in this case I don’t care to have all ports open on that interface because there is no reason to block that traffic. Keep in mind the interface em1 is still in the public zone and more locked down and restricted.

                                The result seems to be that I am now able get it to consistently image across at least two devices and so far it has persisted across device and server reboots. So I think we have made a good leap in that regards. I will keep checking back here for a few days to try and update if I run into issues.

                                Thank you all for persistently fighting with me to get this rolling. I do much appreciate all you have done for me and with me.
                                @Sebastian-Roth @Wayne-Workman @Tom-Elliott

                                Wayne Workman 1 Reply Last reply Reply Quote 2
                                • B
                                  BedCruncher @Tom Elliott last edited by BedCruncher

                                  @Tom-Elliott
                                  Ok, so now we are getting somewhere. I had to run another multicast test really quickly on both of the client computers as I had earlier blown away the partition tables that were restored. That was just to have them properly put back in place. I since have ran the command that you specified on the client and am testing it for both of the stored disk images and they are restoring back. I will let it run it’s course… only take 15 minutes or less for the restore to take place and then try doing the multicast test directly and see if it hangs or not.

                                  EDIT:
                                  The manual restore for both partitions that I did worked correctly and both now boot. I will try scheduling a multicast task again and see where we are at.

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    BedCruncher @Tom Elliott last edited by

                                    @Tom-Elliott
                                    I will try the command you posted above and report back what it finds. Thanks.

                                    1 Reply Last reply Reply Quote 0
                                    • Tom Elliott
                                      Tom Elliott @Sebastian Roth last edited by

                                      @Sebastian-Roth If he’s testing real data (d1p1.img for example) it most definitely will.

                                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                      B 2 Replies Last reply Reply Quote 0
                                      • S
                                        Sebastian Roth Moderator last edited by Sebastian Roth

                                        @BedCruncher Definitely shouldn’t make a different if you are using compressed or uncompressed image data (when testing)!!! Sure pushing the image to disk is a different story but just trying to get the multicast thing running it should work either way I suppose.

                                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                        Tom Elliott 1 Reply Last reply Reply Quote 1
                                        • Tom Elliott
                                          Tom Elliott @BedCruncher last edited by

                                          @BedCruncher The troubleshooting guide forgets that the client actually does the gunzip action, not the server. So your finding makes perfect sense. To fix the client test, you first need to pull the request to a gunzip equiv as well.

                                          For example,

                                          The receiver command should be:

                                          mkfifo /tmp/pigz1
                                          
                                          udp-receiver --nokbd --portbase 50028 --ttl 32 --mcast-rdv-address <FOGSERVERIP> 2>/dev/null >/tmp/pigz1 &
                                          pigz -d -c </tmp/pigz1 | partclone.restore --ignore_crc -O /dev/sda2
                                          

                                          Of course adjust the /dev/sda to the respective file you’re trying to load.

                                          Potentially, the most important part is that of the --mcast-rdv-address as it’s what tells the client WHERE to get the broadcast stream.

                                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            BedCruncher @Wayne Workman last edited by

                                            @Wayne-Workman

                                            I followed up as I just posted on the second link and with some tweaking I was able to get somewhere on this, I believe you should be able to understand what I’ve done according to the second link and it’s testing steps.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 1 / 4
                                            • First post
                                              Last post

                                            186
                                            Online

                                            10.4k
                                            Users

                                            16.4k
                                            Topics

                                            150.5k
                                            Posts

                                            Copyright © 2012-2023 FOG Project