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

    Wiki errors - "Troubleshooting a multicast"

    Scheduled Pinned Locked Moved
    General
    3
    25
    3.9k
    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.
    • george1421G
      george1421 Moderator @3mu
      last edited by

      @3mu Looking at the code (I’m not a programmer) but it looks like the multicast task service is what creates the udp-send task and command syntax. I still haven’t found what database record is used to source the interface name.

      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!

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

        @3mu @george1421 Those settings were used in the past but nowadays FOG tries to determine the interface no matter what setting you have from the system. I know we should have removed those settings at some point but I guess someone forgot. Code where interface is being determined for multicast: 1, 2, 3

        @3mu Please run the following command as root and post output here: /sbin/ip route
        The IP address configured for the storage node might play a role here too. Please post the IP set for the storage node as well.

        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

        3 1 Reply Last reply Reply Quote 0
        • 3
          3mu @george1421
          last edited by

          @george1421 - Current uptime was 1 day 14 hours. I have just now:

          • Cleared all tasks, rebooted and created a new multicast task - the log file still says “–interface dev”.
          • Cleared the tasks, changed the multicast interface to “eth0” (which doesn’t exist) and created a new multicast task - same result.
          • Cleared the tasks, rebooted and created a new multicast task - same result.

          The only things running on this server are FOG and dnsmasq. It is a VM under KVM and has 4GB RAM and a single processor. I have done a single in-place upgrade from 1.5.7 since my original install. I did have to recover the MySQL password (I was distracted and lost the new password before I could record it), but I recovered it without issue.

          I have also updated the fogservice.class.php and FOGSnapinReplicator.service files as per the Interface not ready, waiting for it to come up post.

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

            @3mu said in Wiki errors - "Troubleshooting a multicast":

            I have also updated the fogservice.class.php and FOGSnapinReplicator.service files as per the Interface not ready, waiting for it to come up post.

            Good point. I just remembered that too.

            Please run the following command as root and post output here: /sbin/ip route
            The IP address configured for the storage node might play a role here too. Please post the IP set for the storage node as well.

            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 0
            • 3
              3mu @Sebastian Roth
              last edited by 3mu

              @Sebastian-Roth said in Wiki errors - "Troubleshooting a multicast":

              /sbin/ip route

              default via 10.0.0.138 dev ens3 proto dhcp src 10.0.0.203 metric 100
              10.0.0.0/24 dev ens3 proto kernel scope link src 10.0.0.203
              10.0.0.138 dev ens3 proto dhcp scope link src 10.0.0.203 metric 100
              

              (run under sudo)

              Storage Node config:
              Storage_node_config.PNG

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

                @3mu said in Wiki errors - "Troubleshooting a multicast":

                default via 10.0.0.138 dev ens3 proto dhcp src 10.0.0.203 metric 100

                Here we’ve got it. You seem to have configured your network interface ens3 via DHCP - looks like it from the output. While our code should not fail to find the right interface I still wonder why you would configure a servers IP via DHCP!?

                Just configure the same IP but static in Linux network settings, restart your FOG server and it will most probably work!

                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

                3 1 Reply Last reply Reply Quote 0
                • 3
                  3mu @Sebastian Roth
                  last edited by

                  @Sebastian-Roth - I look after a network with over 600 servers at work. The ones that cause me problems are the ones with static IP addresses - generally because somebody makes a typo when they are configuring an interface. We also do a lot of migrations, mergers and other changes, so reserved addresses in DHCP make that much easier, as well as enforcing consistency and a basic level of self-documentation. DHCP also makes it easier to deploy in environments where the user does not have control of the network.

                  I’m sorry for taking up your time, @george1421, and thank you both.

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

                    @3mu I will be looking into fixing this issue! Though I can’t promise you when the next release will be out. Would you want me to post the fix here so you could manually add it?

                    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

                    3 1 Reply Last reply Reply Quote 0
                    • 3
                      3mu @Sebastian Roth
                      last edited by

                      That would be great, thanks @Sebastian-Roth. I’m happy to test.

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

                        @3mu Sorry for the delay. I just had a play with this and I think it’s best to go for a simple fix: https://github.com/FOGProject/fogproject/commit/21460c1d8ba7dae1b2988b9287c188595ce01e9d

                        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

                        3 2 Replies Last reply Reply Quote 0
                        • 3
                          3mu @Sebastian Roth
                          last edited by

                          Thanks, @Sebastian-Roth. I’ll test as soon as I finish sorting out a few disasters - hopefully in the next day.

                          1 Reply Last reply Reply Quote 0
                          • 3
                            3mu @Sebastian Roth
                            last edited by

                            @Sebastian-Roth - Sorry for the delay - some other unrelated issues and then a pandemic to deal with! The fix works perfectly.

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

                            204

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project