3 Replies Latest reply on Jul 21, 2014 3:34 PM by pgeorge1

    Domain Alert - Node elected as master gateway

    5Forty7 Active Member

      Hi All,

       

      We got the below alert from the domain but looks like the everything is backup and running.

      Node [node01_bxginformatica] is elected as the master gateway node for domain [Domain_bxginformatica].

       

      We do not have an Administrator and I'm trying to troubleshoot the issue.


      The Node log has the below error.

      2014-07-20 23:43:53,988 ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[LGS_10024] Log request failed due to the following error [[DTF_0001] An error occurred in the underlying transport layer: [java.util.concurrent.ExecutionException: org.beepcore.beep.core.BEEPException: [sendMSG]: Channel is in [7] state.]].].


      I'm attaching the logs and any pointers on what the issue is will be helpful.

       

      Appreciate all the help.

       

      Tx, T

        • 1. Re: Domain Alert - Node elected as master gateway
          Active Member

          Hi,

           

          Below reponse would help you understand the ERROR and its severity.

           

          ERROR [Monitor Guaranteed Message Logger Thread] [CCM_10322] While logging messages to the Log Service, the following error occurred: [[DOM_10022] The master gateway node for the domain is not available. Electing another master gateway. Wait for the election of the master gateway node to  complete. If the problem persists, verify that the master gateway node is running.]. Fix the errors written to the node.log file.

           

          The most common causes are:

          During Domain startup when services have already started while the Master Gateway election is still ongoing. In this case, the error can be safely ignored and should not occur again once the Master Gateway node has been elected.

          and

          During a failover where the Master Gateway node has just gone down and a new one has not been elected.

          If another Master Gateway node can be elected in the domain, all services will automatically become available again and will resume normal operation.

          In this case, the error itself can be safely ignored, although you might want to investigate the reason for the failover.

           

          If the domain does not become available and the error continues to occur, check $INFA_HOME/tomcat/logs/node.log on all configured Gateway Nodes in this domain to identify why no Gateway could be elected. This could indicate an issue with the network or the domain database.

           

          Thanks,

          Yuva

          • 2. Re: Domain Alert - Node elected as master gateway
            5Forty7 Active Member

            Thanks Yuva for the reply.

             

            We are only a one node domain.

            This does not happen during the domain start-up. All our services have been up and running fine.

             

            How can we identify what is causing the node election while it was already available before. Do the attached logs suggest any specific reason for the node being re-elected as the master gateway? Are there any other logs that I can look for this information?

             

            If this was a DB connectivity or network issue, wouldn't the logs capture it?

             

            T

            • 3. Re: Domain Alert - Node elected as master gateway
              pgeorge1 Guru

              Please refer to the document:

              https://mysupport.informatica.com/infakb/whitepapers/4/Pages/1/158429.aspx

               

              You will need to set the MasterDBRefreshInterval option as shown here.

              Please look for the paragraph that starts with "From PowerCenter 9.5.1 onwards, even single gateway nodes would go down with the DOM_10094 error message if node process fails to update the Master election table for 12 times."