Announcement

Collapse
No announcement yet.

Issue with Clustering function

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Issue with Clustering function

    Hi Mod,

    I have an error when trying cluster as picture below. Firewall is still opening on both NxFilter, how can I fix that?
    Click image for larger version  Name:	image.png Views:	0 Size:	39.0 KB ID:	2028

  • #2
    Whatever it is, something blocks TCP/19004 on your master node. Try 'telnet master-node-ip 19004' on your slave node's cmd.

    Yod didn't add any IP on 'System > Clustering > Slave IP'? If you added your slave IP there, it might appear with a different IP to your master node. In that case, you may see some log on your master node side.

    Comment


    • #3
      Yes, you're right. I don't know why TCP 19004 not working on my server (19003, 19002, and other ports are still normal). It's really strange, do you have any suggestions?
      Click image for larger version

Name:	image.png
Views:	138
Size:	63.7 KB
ID:	2032
      Attached Files

      Comment


      • #4
        On your master node, do you see 'MM, NodeListener started.' in your log file when you restart it?

        Comment


        • #5
          And did you change 'Run Mode' on 'System > Clustering' on your master node? You have to restart it when you change it.

          Comment


          • #6
            Yes, I saw it when restart.
            Click image for larger version

Name:	image.png
Views:	146
Size:	12.8 KB
ID:	2036

            Comment


            • #7
              Originally posted by support200 View Post
              And did you change 'Run Mode' on 'System > Clustering' on your master node? You have to restart it when you change it.
              Yes. I already change Run mode to 'Run as Master'

              Comment


              • #8
                Then try 'telnet localhost 19004' on your master node.

                Comment


                • #9
                  Originally posted by support200 View Post
                  Then try 'telnet localhost 19004' on your master node.
                  I tried to reboot my machine and finally port TCP 19004 went up, When I restart slave node, log on master node received the status of slave node. But on the GUI, I didn't see any slave node status.
                  And I can't go to the slave node GUI anymore.

                  Click image for larger version

Name:	image.png
Views:	175
Size:	325.7 KB
ID:	2041Click image for larger version

Name:	image.png
Views:	154
Size:	34.5 KB
ID:	2042
                  Attached Files

                  Comment


                  • #10
                    Slave node doesn't have GUI as you need to change settings on your master node GUI. Even if you log in, you only can change 'Run Mode'. The stats on master node updates once in a minute.

                    Comment


                    • #11
                      Originally posted by support200 View Post
                      Slave node doesn't have GUI as you need to change settings on your master node GUI. Even if you log in, you only can change 'Run Mode'. The stats on master node updates once in a minute.
                      Yes, but I can't even see the login page. When slave node joins the cluster, I cannot use any function because all the ports automatically closed as below
                      Click image for larger version

Name:	image.png
Views:	137
Size:	84.0 KB
ID:	2046
                      Attached Files

                      Comment


                      • #12
                        And on Master node GUI, I still don't see any status of slave node even though 30mins pass by.
                        Click image for larger version

Name:	image.png
Views:	149
Size:	36.3 KB
ID:	2048

                        Comment


                        • #13
                          You need to see this kind of log once in a minute on your master node, 'NodeListener.SockHandler.dealHello, line =..'.

                          I just installed a cluster and I can login to slave node GUI without a problem. Of course, there's only 'System > Clustering' menu.

                          Why don't you just stop your firewall for testing?

                          Comment


                          • #14
                            Finally, I found what causes the issue - 2 machines have the same 'hostname' so whenever the slave node connects to master node simply slave node lost all the connections (slave node connects to themselves I guess).
                            Btw thanks for your instant support <3
                            Last edited by trongnotfound; 05-15-2023, 03:28 AM.

                            Comment


                            • #15
                              Good to hear that. Will be helpful to others.

                              Comment

                              Working...
                              X