5 Replies Latest reply on Feb 14, 2018 4:49 AM by Attachment Scanner

    BCM Agent Communication Issue with Master

      Share This:

      Hi All

       

      We have install BCM on single node where Master (Relay) & DB is present and now deployed agent at 10 Machines but getting below error in agent log file.

      ==============================================================================================

      2015/07/10 16:28:27 AgentIdentity                    W   [2828] Relay module did not returned required information. Will check locally...

      2015/07/10 16:28:27 AgentIdentity                    I   [2828] Core: IP address found [192.168.4.101/24] (Local)

      2015/07/10 16:28:27 AgentIdentity                    W   [2828] Current parent is out of sync

      2015/07/10 16:28:27 Identity                         I   [2828] User name is currently defined (Support-PC\Support)

      2015/07/10 16:28:28 Identity                         I   [2828] Primary user name is currently defined for the 24 hours(s) period with counter 144 (Support-PC\Support)

      ================================================================================================

       

      Changed the mentioned parameter from host-name to IP address in Relay.ini file of Master as well as client also...

      ==============================

      ParentName=192.168.4.168

      ParentPort=1610

      ==============================

       

      StaticParentName=192.168.4.168

      StaticParentPort=1610

      =============================

       

      Note : We are able to telnet & ping from both side.

       

      Attached is the agent log file, please help us to resolve it.

       

      Thanks

        • 1. Re: BCM Agent Communication Issue with Master
          Julien Devienne

          Hello,

           

          A master should never have a parentname in its relay.ini. The first thing to do is to stop the service of the master then delete that parentname and anything that is set on "sequence=". Then restart the master.

           

          You say you are able to telnet on the port 1610 and on the port 1611 from the client to the master? If so, please check if "PAC=" and "SSL=" are set to the same value in your client and your master ../config/mtxagent.ini.

           

          Have a good day

          • 2. Re: BCM Agent Communication Issue with Master

            Julien Devienne

             

            Thanks for the response, Modified suggested parameters but no luck, attached are the logs from master/client.

             

            Please help me to resolve the same issue.

             

            Thanks

            • 3. Re: BCM Agent Communication Issue with Master
              Dominik Kress

              Hi Anay,

               

              You should recreate the zip of the log files where both log files contains the same time stamp (client is from 20.6 and master is from today) and please add the mtxagent.ini from your client.

               

              You wrote the the ip address of your master server is 192.168.4.168 as in the provided master.log file the master ip address is 192.168.51.50. Does the master server have multiple NICs installed?

               

              Based on the master.log file it looks like there are issues with the SSL certificate:

               

              -----

              2015/07/11 22:47:08 Server                           I   [5784] Received incoming connexion (TCP (local: 192.168.51.50:1610, peer: 192.168.51.1:51610)) of priority 1: handling at once

              2015/07/11 22:47:08 Server                           I   [2868] Processing connection TCP (local: 192.168.51.50:1610, peer: 192.168.51.1:51610)

              2015/07/11 22:47:08 Server                           I   [2868] Connection is secured

              2015/07/11 22:47:08 Socket                           D   [4324] BufferedSocket: receive failed

              2015/07/11 22:47:08 Socket                           D   [4420] SslHandshake - Fatal error (SSL_ERROR_SSL)

              2015/07/11 22:47:08 Socket                           D   [4420] SslHandshake - Error details (error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate)

              2015/07/11 22:47:08 Server                           W   [2868] SSL handshake failed

              -------

               

               

               

               

              Regards,

              Dominik

              • 4. Re: BCM Agent Communication Issue with Master

                Hi Dominik,

                 

                Sorry, By mistake uploaded wrong logs.

                 

                Julien Devienne Provided Solution working now.

                 

                Thanks a lot

                • 5. Re: BCM Agent Communication Issue with Master
                  Attachment Scanner

                  UPDATE: Based on File attachment policies, attached files were removed, see FAQ for more