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

    FOG multicast issue: udp-sender not starting

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    6
    21
    9.2k
    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.
    • Wayne WorkmanW
      Wayne Workman @AndersenJ
      last edited by Wayne Workman

      @AndersenJ said:

      @Wayne-Workman I tried Fedora 21 a few days ago and got precisely the same result.

      Then something isn’t right - plain and simple. You can’t try two completely different distributions on the same machine and the same unmanaged switch and something not be screwy…

      Better question is… has multicast via FOG ever worked in your environment?
      Are you setting any custom multicast settings?

      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
      • Tom ElliottT
        Tom Elliott
        last edited by

        I don’t know how to put this any more simply. Hopefully you all will understand.

        Dev/1.3 FOG will attempt to use the interface specified on the Master Storage Nodes of the relative systems. So Please start by checking the interface name on the Storage Nodes that are the “masters” for the groups they are in. This is done through the storage management page on the GUI.

        If for SOME reason or other the storage node’s interface field is unable to be received the fallback is the FOG_UDPCAST_INTERFACE. This is again just a fallback, that should basically never even be able to happen. The FOG_NFS_ETH_MONITOR file was only used for bandwidth tracking but since moving the nodes to contain their own relevant interface setting, I’ve basically eradicated any need for this setting.

        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

        A 1 Reply Last reply Reply Quote 2
        • N
          nengelhardt
          last edited by

          Okay. So here’s what’s happening for me and what I suspect is happening for @AndersonJ as well. @tom-elliott was right, the setting was wrong under “storage management”>“DefaultMember”>“interface”. So the udp-sender would start, then end itself when it realized it was started with an invalid interface. Thanks for the help, everyone.

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

            @Tom-Elliott It’s a good guess that this would be the problem, but I just checked and my interface is set correctly to ‘eth0’ in the location you described, and in all others I could find. As far as I can tell, udp-sender is never starting in the first place.

            It is worth noting that I have had multicasting work in the past; last time it worked was August 12th. I’m pretty sure I didn’t change any settings at that time, nor did an update to FOG or any other software instigate it. The server isn’t even connected to the internet.

            Also relevant: I just re-checked my logs; the server hasn’t updated any of the files in /opt/fog/log/ since that day. I thought that failed attempts at least would be in there.

            Tom ElliottT 1 Reply Last reply Reply Quote 0
            • Tom ElliottT
              Tom Elliott @AndersenJ
              last edited by

              @AndersenJ What is the output of ip addr or ifconfig where the Ethernet name is listed for the relevant IP Address of your fog server?

              You saying your server’s interface is eth0 doesn’t simply make it so. I’m not aware of Fedora 21 setting an interface to eth0, I don’t recall any eth setting being specified from Fedora 14 and up. Again I could be wrong and this is where the commands I requested would be of most use.

              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

              A 2 Replies Last reply Reply Quote 0
              • A
                AndersenJ @Tom Elliott
                last edited by

                @Tom-Elliott I’m actually back to using Mint 17.2 now, since I had the same multicasting problem with Fedora as I had using Mint. ifconfig returns eth0 and lo. Not sure what it was when I was using Fedora, but I assure you I did check to make sure the interface I was using actually existed.

                1 Reply Last reply Reply Quote 0
                • A
                  AndersenJ @Tom Elliott
                  last edited by

                  @Tom-Elliott I figured out the issue: it was my ethernet adapter. I plugged in a USB 2.0 ethernet adapter, changed my interface settings to use it, and multicasting worked perfectly (at USB 2.0 speeds). It was the Dell Latitude E6530 ethernet adapter which wasn’t working.

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

                    @AndersenJ said:

                    @Tom-Elliott I figured out the issue: it was my ethernet adapter. I plugged in a USB 2.0 ethernet adapter, changed my interface settings to use it, and multicasting worked perfectly (at USB 2.0 speeds). It was the Dell Latitude E6530 ethernet adapter which wasn’t working.

                    ha. I knew something was screwy.

                    I’m very happy you figured it out.

                    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
                    • I
                      inst
                      last edited by

                      i have the same problem ! is there a solution here ?

                      A 1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @inst Only very seldomly issues are exactly the same in such complex environments. Espacially as this post is about a year old I kond of doubt that you have exactly the same version of FOG running in the same kind of environment. So please do us a favour and open a complete new topic and explain your problem in detail to us (step by step on how you get to the error, plus pictures and screenshots will help a lot).

                        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

                        1 Reply Last reply Reply Quote 1
                        • A
                          AndersenJ @inst
                          last edited by

                          @inst It turned out to be a hardware issue. The solution was to use different hardware. If this doesn’t fix it for you, I too would suggest opening a different thread.

                          1 Reply Last reply Reply Quote 2
                          • 1
                          • 2
                          • 1 / 2
                          • First post
                            Last post

                          166

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project