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

    FOG 1.6.0.158 - Multicast error (session has already started with 0 clients)

    Scheduled Pinned Locked Moved Solved FOG Problems
    6 Posts 2 Posters 40 Views
    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.
    • M
      Mikeee89
      last edited by Mikeee89

      Hi everyone,

      I’m running FOG 1.6.0.158 in a Hyper-V environment on an isolated (internal) network. My DHCP server is Windows Server 2022, and the boot file is ipxe.efi. I’ve tried this on two different Hyper-V hosts; on the second host I also installed the latest dev-branch version, and the issue occurs on both 1.6.0.158 and the dev-branch.

      The problem: I create a multicast session with 2 clients and a 10-minute timeout. Then I PXE boot the machines and try to join the multicast session, but I get the message: “That session has already started and can no longer joined.” Meanwhile, the FOG web UI shows 0 connected clients under Tasks / Active Multicast Tasks.

      I installed FOG using the default standard install mode (–install-mode standard), and at the end of the installation I let the installer open the required ports in firewalld. The OS is AlmaLinux 9.8, and SELinux is set to permissive. Both servers are fresh installs on a clean AlmaLinux 9.8 system, not upgrades from 1.5. I’ve attached 2 screenshots and a few lines from the multicast log.

      Any help solving this would be greatly appreciated.

      Thanks,
      Miklós

      fog1.6_multicast_log.txt

      fog1.6_pxe_error_message.png

      fog1.6_task_management UI.png

      P.S. If you need any other logs, or the status of the services or the multicast session, just let me know and I’ll post them in a reply.

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

        @Mikeee89 Thanks for the log, it shows the cause. The first line of the udp-sender command has --max-wait 10. That value is seconds, not minutes.

        The Session Timeout field on the Multicast page asks for minutes, but FOG stored the number as seconds. So your 10-minute session waited only 10 seconds after it started. After that, the PXE menu treats the session as already started and refuses the join, even with 0 clients connected.

        The fix is in https://github.com/FOGProject/fogproject/pull/2114 and goes to dev-branch.

        Until you update, either of these works on your current install:

        • Enter the timeout in seconds. For 10 minutes, enter 600.
        • Or leave the timeout blank. FOG then uses the global setting FOG_UDPCAST_MAXWAIT (in minutes) and converts it correctly.

        Cancel the stuck session first, then create a new one.

        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

        M 1 Reply Last reply Reply Quote 0
        • M
          Mikeee89 @Mikeee89
          last edited by Mikeee89

          PS: i used this dev-branch version: 1.6.0.208

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

            @Mikeee89 Thanks for the log, it shows the cause. The first line of the udp-sender command has --max-wait 10. That value is seconds, not minutes.

            The Session Timeout field on the Multicast page asks for minutes, but FOG stored the number as seconds. So your 10-minute session waited only 10 seconds after it started. After that, the PXE menu treats the session as already started and refuses the join, even with 0 clients connected.

            The fix is in https://github.com/FOGProject/fogproject/pull/2114 and goes to dev-branch.

            Until you update, either of these works on your current install:

            • Enter the timeout in seconds. For 10 minutes, enter 600.
            • Or leave the timeout blank. FOG then uses the global setting FOG_UDPCAST_MAXWAIT (in minutes) and converts it correctly.

            Cancel the stuck session first, then create a new one.

            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

            M 1 Reply Last reply Reply Quote 0
            • M
              Mikeee89 @Tom Elliott
              last edited by

              @Tom-Elliott

              The issue affects both FOG 1.5.10.2534 and FOG 1.6. Version 1.5.10.2518 is not affected. The error no longer occurs when entered as seconds. Thanks for the help.

              Tom ElliottT 1 Reply Last reply Reply Quote 0
              • M Mikeee89 has marked this topic as solved
              • Tom ElliottT
                Tom Elliott @Mikeee89
                last edited by

                @Mikeee89 Good to hear that seconds work. The fix is now merged into dev-branch, so a dev-branch update makes the field take minutes again.

                1.5.10.2518 and 1.5.10.2534 have the same multicast code, so this bug cannot be in one and not the other. 1.5 has no per-session timeout. Its session waits FOG_UDPCAST_MAXWAIT minutes (10 by default).

                Can you post the udp-sender line from /opt/fog/log/multicast.log on the 1.5.10.2534 server? The --max-wait value on the first stream shows what that server waited.

                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

                M 1 Reply Last reply Reply Quote 0
                • M
                  Mikeee89 @Tom Elliott
                  last edited by

                  @Tom-Elliott I checked again. I was mistaken; FOG 1.5 was not affected. Thanks again for the help.

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

                  34

                  Online

                  12.8k

                  Users

                  17.7k

                  Topics

                  157.5k

                  Posts
                  Copyright © 2012-2026 FOG Project