Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-1602

Multicraft: Notify Multicraft that it should reselect the IP:Port

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 3.4.2
        • Fix Version/s: 3.4.3, 3.5.0-b1
        • Component/s: Modules
        • Labels:
          None

          Description

          Currently, the module relies on Multicraft to determine the server IP and Port. However, if the daemon changes and no socket address is specified (e.g. no dedicated IP), then Multicraft continues to use the socket address that it generated when the server was created. This could be, for instance, on daemon ID 1. Thus, the socket address is no longer valid for the given daemon.

          Daniel from Multicraft advised that specifying no value (empty strings) for both the IP and Port fields will force Multicraft to reselect a new socket address based on the current daemon.

            Issue Links

            relates to

            Bug - A problem which impairs or prevents the functions of the product. CORE-3223 Multicraft: IP not updated when daemon is changed

            • Major - Major loss of function.
            • Closed

              Activity

              Hide
              Permalink
              tyson Tyson Phillips (Inactive) added a comment -

              While the IP/Port is now reset to fix this issue, if a port is not set when a service is created, it will be determined twice. Once when the server is created, and once again to fix the potential issue related to this task. Because it can be set twice, Multicraft will increment the port twice.

              e.g. If adding two Multicraft services, once could be created on port 25565, and the other immediately following it would be on 25567. 25566 is skipped

              Show
              tyson Tyson Phillips (Inactive) added a comment - While the IP/Port is now reset to fix this issue, if a port is not set when a service is created, it will be determined twice. Once when the server is created, and once again to fix the potential issue related to this task. Because it can be set twice, Multicraft will increment the port twice. e.g. If adding two Multicraft services, once could be created on port 25565, and the other immediately following it would be on 25567. 25566 is skipped

                People

                • Assignee:
                  tyson Tyson Phillips (Inactive)
                  Reporter:
                  tyson Tyson Phillips (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    25/Mar/15