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

FOG Multicast issue - stuck on starting to restore image - version 7547

Scheduled Pinned Locked Moved Solved
FOG Problems
4
57
19.7k
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.
  • S
    Sebastian Roth Moderator
    last edited by Jun 24, 2016, 2:55 PM

    @arainero

    Could not broadcast data packet to 192.168.1.255:64478 (Permission denied)
    

    Well, you might want to try disabling your firewall for the moment to see if it works…

    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 Jun 24, 2016, 5:17 PM Reply Quote 1
    • A
      arainero @Sebastian Roth
      last edited by arainero Jun 24, 2016, 11:19 AM Jun 24, 2016, 5:17 PM

      @Sebastian-Roth thank you for the suggestion. However, selinux and iptables on the server have both been turned off since FOG was installed. I checked to make sure firewalld was not running, but it is not available in CentOS 6.5. Is there a different service I should check to make sure it is not restricting it?

      I don’t believe it is router/firewall related since I’ve never had issues with multicasting with it in the past and all inter LAN traffic is allowed. I am going to triple check to make sure nothing on the router would impede multicast traffic.

      Also, is using 192.168.1.255 an appropriate setting to use for the multicast address under multicast settings? It was the only address that would work with the manual test from the wiki which was odd. When left on default (which is 0 or using 0.0.0.0) it wouldn’t work.

      W 1 Reply Last reply Jun 27, 2016, 12:47 PM Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Jun 25, 2016, 2:05 PM

        @arainero Have you done the multicast tests by hand yet? https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast#Testing_Multicast

        What happens if you leave the multicast address setting empty? In theory it should not pass the --mcast-data-address to the udp-sender tool and the tool should use the address it thinks is correct. Don’t set 0 or 0.0.0.0 but make it empty.

        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

        W 1 Reply Last reply Jun 25, 2016, 2:25 PM Reply Quote 0
        • W
          Wayne Workman @Sebastian Roth
          last edited by Jun 25, 2016, 2:25 PM

          @Sebastian-Roth We did run the manual test, when we leave the destination address blank, it doesn’t work and says it’s sending to 2xx.xxx.xxx.xxx something (can’t remember).

          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
          • S
            Sebastian Roth Moderator
            last edited by Jun 26, 2016, 1:14 PM

            As you can see here multicast has it’s very own “address space”. It’s designed to use those addresses to work properly I suppose. I guess you can use different addresses if you really know what you are doing. But using a subnet broadcast address does not sound right to me.

            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 2
            • T
              Tom Elliott
              last edited by Jun 27, 2016, 11:07 AM

              All the mcast-data-address does, to my knowledge, is tell the client what address to try to grab the UDP packets from. It’s still going to use multicast addressing to grab it. So I think @Sebastian-Roth is correct. The mcast-data-address should NOT be a broadcast/network address, but the direct location to the host trying to send the data to begin with. The mcast-rdv-address will allow you to define the actual multicast address to use for the session, and should remain in the 224 pool (though there could be any number of reasons you need to change it to something else.)

              Then again, I’m a total idiot when it comes to fully understand UDP and its actions. What I do know mcast-data-address will try to derive that ip address’s multicast address from where it’s pointing. This is NOT where you want to be trying to define the multicast network it’s going across.

              To quote the man page in regards to these two separate arguments:

              –mcast-data-address address
              Uses the given address for multicasting the data. If not specified, the program will automatically derive a multicast address from its own IP (by keeping the last 27 bits of the IP and then prepending 232).

              –mcast-rdv-address address
              Uses a non-standard multicast address for the control (rendez-vous) connection. This address is used by the sender and receivers to “find” each other. This is not the address that is used to transfer the actual data.
              By default “mcast-rdv-address” is the Ethernet broadcast address if “ttl” is 1, and 224.0.0.1 otherwise. This setting should not be used except in very special situations, such as when 224.0.0.1 cannot be used for policy reasons.

              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

              W 1 Reply Last reply Jun 27, 2016, 12:46 PM Reply Quote 0
              • W
                Wayne Workman @Tom Elliott
                last edited by Jun 27, 2016, 12:46 PM

                @Tom-Elliott @Sebastian-Roth

                Ok then. All that makes sense, I learn something new every day here.

                However - manually doing a udp-cast test without specifying an address failed, while specifying the broadcast address for this fog server’s broadcast domain worked.

                Ideas?

                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/

                T 1 Reply Last reply Jun 27, 2016, 12:47 PM Reply Quote 0
                • T
                  Tom Elliott @Wayne Workman
                  last edited by Jun 27, 2016, 12:47 PM

                  I need details on the exact steps.

                  For example, if you setup the client to receive data BEFORE the udp-sender was established, the client side will NEVER connect to anything.

                  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 Jul 4, 2016, 6:45 PM Reply Quote 0
                  • W
                    Wayne Workman @arainero
                    last edited by Jun 27, 2016, 12:47 PM

                    I’m sure that @arainero would be happy to re-do the test, and provide exact steps.

                    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
                    • A
                      arainero @Tom Elliott
                      last edited by arainero Jul 4, 2016, 12:47 PM Jul 4, 2016, 6:45 PM

                      @Tom-Elliott @Wayne-Workman

                      Sorry for the delay, here are the exact steps:

                      For testing 1 client:

                      1. Boot one computer into debug
                      2. Enter udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint into server and press enter. I now see
                      [root@fogserv ~]# udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log  --ttl 1 --nopointopoint
                      Udp-sender 20120424
                      Using full duplex mode
                      
                      
                      1. Go to client computer and type this udp-receiver. On the client this immediately shows
                      Udp-receiver 20120424
                      UDP receiver for (stdout) at 192.168.1.118 on eth0
                      received message, cap=00000009
                      Connected as #0 to 192.168.1.3
                      Listening to multicast on 232.168.1.3
                      Press any key to start receiving data!
                      
                      

                      On the server this immediately shows

                      New connection from 192.168.1.118  (#0) 00000009
                      Ready. Press any key to start sending data.
                      
                      1. I press enter on the server. Nothing happens.
                      2. I now press enter on the client. I get
                      Sending go signal
                      

                      Nothing happens on the server. I now press enter on the server and still nothing happens.

                      I CTRL-C out on the client and see [root@fogserv ~]# re-xmits=0000000 ( 0.0%) slice=0112 - 0

                      appear on the server. I CTRL-C on server and I am back to the prompt.

                      If I repeat the steps to step 4 and hit enter on the client first instead of the server I get the same results.

                      If I do the above steps again but use

                      udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint --mcast-data-address 192.168.1.255
                      
                      

                      instead of the wiki command and hit enter on the client first I see the fog settings file displayed on the client. If I repeat that and hit enter on the server first I see the settings displayed. This also works with a 2nd client computer and does not matter if I hit enter on the client or server first.

                      The --mcast-data-address 192.168.1.255 seems to be the magic argument that makes it “work” for the test scenario.

                      Was this enough to determine anything or would you want me to do anything else to help narrow it down? If anyone wants to take a look through teamviewer or what-have-you I am more than open.

                      Thanks again everyone and enjoy the 4th!

                      1 Reply Last reply Reply Quote 0
                      • A
                        arainero
                        last edited by Jul 7, 2016, 10:52 PM

                        Should I update to trunk and do the same tests or hold off on that for now?

                        1 Reply Last reply Reply Quote 0
                        • S
                          Sebastian Roth Moderator
                          last edited by Jul 8, 2016, 9:16 AM

                          @arainero What about using the options you see in the logs? cat /path/to/file | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 600 --portbase 65102 --full-duplex --ttl 32 --nokbd --nopointopoint

                          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 Jul 8, 2016, 5:20 PM Reply Quote 0
                          • A
                            arainero @Sebastian Roth
                            last edited by Jul 8, 2016, 5:20 PM

                            @Sebastian-Roth

                            If I use this modifed version of that line from the log it works.

                            cat /opt/fog/.fogsettings | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 600 --full-duplex --nokbd --nopointopoint --mcast-data-address 192.168.1.255
                            

                            I had to remove portbase and the ttl flags and add the --mcast-data-address 192.168.1.255 flag. After doing that I was able to receive the fog settings files.

                            I tried the command with just removing the portbase and ttl flags and not adding --mcast-data-address 192.168.1.255, but that didnt work.

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by Sebastian Roth Jul 8, 2016, 11:43 AM Jul 8, 2016, 5:38 PM

                              @arainero Why did you have to remove --ttl and --portbase?? I still think something is wrong with the network setup. From the udp-cast man page I get that it would default to use 232.168.1.x (where x would be the last byte of the server IP address). Possibly your switch is layer 3 switch and does not allow those “out of range” IPs?

                              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 Jul 8, 2016, 6:28 PM Reply Quote 1
                              • A
                                arainero @Sebastian Roth
                                last edited by Jul 8, 2016, 6:28 PM

                                @Sebastian-Roth I removed those to test to see if different scenarios would work. I tested with --mcast-data-address 232.168.1.255, 232.168.1.1, 232.168.1.0, etc, and those worked too.

                                I actually added --ttl 32 and that worked. It’s just when I add --portbase 65102 it stops working. I tried a few different port variations with no luck.

                                The switches in the letwork are layer 2. Multicast used to work fine and there have been no changes to the network. I will double check the switch configurations again though.

                                W 2 Replies Last reply Jul 8, 2016, 9:23 PM Reply Quote 0
                                • W
                                  Wayne Workman @arainero
                                  last edited by Wayne Workman Jul 9, 2016, 6:26 AM Jul 8, 2016, 9:23 PM

                                  @arainero are you sure fog firewall is off? Some places configure special ports for use with multicast (like mine).

                                  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/

                                  A 1 Reply Last reply Jul 9, 2016, 5:04 PM Reply Quote 0
                                  • W
                                    Wayne Workman @arainero
                                    last edited by Wayne Workman Jul 9, 2016, 6:28 AM Jul 9, 2016, 12:21 PM

                                    @arainero said in FOG Multicast issue - stuck on starting to restore image - version 7547:

                                    It’s just when I add --portbase 65102 it stops working. I tried a few different port variations with no luck.

                                    Working off of this finding - I may have a fix for you.

                                    Open up this file on your master node:
                                    /var/www/html/fog/lib/service/multicasttask.class.php

                                    Comment out line 91, do that by putting two forward slashes at the beginning of the line, like this:

                                    0_1468066820472_alter multicast.png

                                    Then restart the FOGMulticastManager like this:
                                    service FOGMulticastManager restart

                                    And then try multicast again. With any luck, it’ll work.

                                    Even if it DOES work - we need to figure out what it is about your network that’s preventing you from defining a port, I hope you understand.

                                    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/

                                    A 1 Reply Last reply Jul 9, 2016, 5:20 PM Reply Quote 0
                                    • S
                                      Sebastian Roth Moderator
                                      last edited by Jul 9, 2016, 4:23 PM

                                      @arainero said:

                                      Multicast used to work fine and there have been no changes to the network.

                                      Can’t remember how many times I’ve heard this. But those kind of things usually don’t just stop working from one day to the other. Maybe it wasn’t you who changed anything. I really hope we can find out what’s wrong here and find a solution to it. Keeping my fingers crossed. Are you absolutely sure there are only layer 2 switches between the FOG server and the clients?

                                      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 Jul 9, 2016, 5:25 PM Reply Quote 0
                                      • A
                                        arainero @Wayne Workman
                                        last edited by Jul 9, 2016, 5:04 PM

                                        @Wayne-Workman

                                        iptables and selinux are off. Firewalld is not installed either. Is there a firewall somewhere else that I have missed?

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          arainero @Wayne Workman
                                          last edited by arainero Jul 9, 2016, 11:27 AM Jul 9, 2016, 5:20 PM

                                          @Wayne-Workman I tried this with no luck, but I expected it to work as you did. I had some interesting observations.

                                          The new command I found in the multicast log was

                                          cat /images/6_16_16/d1p1.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 180 --mcast-data-address 232.168.1.0 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/6_16_16/d1p2.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 180 --mcast-data-address 232.168.1.0 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/6_16_16/d2p1.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 180 --mcast-data-address 232.168.1.0 --full-duplex --ttl 32 --nokbd --nopointopoint;
                                          

                                          As expected there were no ports involved, but the multicast still didn’t work. However, if I took the first part of it and replaced it with the fogsettings file like in the wiki test it works. (This test was the test from the wiki and not a GUI multicast)

                                          cat /opt/fog/.fogsettings | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 2 --max-wait 180 --mcast-data-address 232.168.1.0 --full-duplex --ttl 32 --nokbd --nopointopoint
                                          

                                          The only difference between the two commands is the file and the fact that I am running the second one manually through the terminal and receiving it manually with udp-receiver.

                                          Is there a different process when doing this test manually compared to when it is done through the GUI?

                                          Here is the multicast log

                                          [07-09-16 1:08:48 pm] | Task (1) Multi-Cast Task has started.
                                          [07-09-16 1:08:48 pm] | CMD: cat /images/6_16_16/d1p1.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 180 --mcast-data-address 232.168.1.0 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/6_16_16/d1p2.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 180 --mcast-data-address 232.168.1.0 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/6_16_16/d2p1.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 180 --mcast-data-address 232.168.1.0 --full-duplex --ttl 32 --nokbd --nopointopoint;
                                          [07-09-16 1:08:48 pm] | Task (1) Multi-Cast Task sending on base port: 53324
                                          [07-09-16 1:08:48 pm] | Task (1) 1 client(s) found.
                                          Broadcasting control to 224.0.0.1
                                          UDP sender for (stdin) at 192.168.1.3 on eth0 
                                          [07-09-16 1:08:48 pm] | Task (1) /images/6_16_16 image file found.
                                          Udp-sender 20120424
                                          [07-09-16 1:08:48 pm] | Task (1) Multi-Cast Task has been cleaned.
                                          [07-09-16 1:08:48 pm] | Task (1) Multi-Cast Task is new!
                                          [07-09-16 1:08:48 pm] | 1 task found
                                          [07-09-16 1:08:48 pm] | 0 tasks to be cleaned
                                          [07-09-16 1:08:38 pm] | Sleeping for 10 seconds to ensure tasks are properly submitted
                                          [07-09-16 1:08:28 pm] * No tasks found!
                                          [07-09-16 1:08:18 pm] * No tasks found!
                                          [07-09-16 1:08:18 pm] * Starting service loop
                                          [07-09-16 1:08:18 pm] * Checking for new items every 10 seconds
                                          [07-09-16 1:08:18 pm] * Starting MulticastManager Service
                                          
                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          • First post
                                            Last post

                                          220

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project