4 Replies Latest reply on Aug 21, 2009 11:00 AM by Ian Springer

    Why it takes so lang to registrate by running ./rhq-agent.sh

    Thomas Chang Apprentice

      Hi all,

      I am going to register an agent and run

      ./rhq-agent.sh -l
      


      After I entered the parameters/values I got:

      ...
      The setup has been completed for the preferences at node [/rhq-agent/default].
      The agent will now wait until it has registered with the server...
      ...
      


      But it doesn't go further and hang there.

      Someone can tell why?

        • 1. Re: Why it takes so lang to registrate by running ./rhq-agen
          Ian Springer Master

          At this point, the Agent is trying to connect to the Jopr Server and register. A few things to check:

          1) Is the Jopr Server running?
          2) Are the address and port you specified for the Server correct?
          3) Can the Agent reach the Server address/port? - no firewalls blocking it, etc. Try telnet'ing to the Server address from the Agent box, e.g.: "telnet 192.168.79.34 7080"
          4) If you used a hostname for the Server address, can the Agent machine resolve that hostname, either via DNS or the hosts file? Try "nslookup jonserver.example.com" from the Agent box.
          5) Check the JON Server log to see if it logged anything regarding that Agent attempting to register.

          • 2. Re: Why it takes so lang to registrate by running ./rhq-agen
            Thomas Chang Apprentice

             

            "ips" wrote:
            At this point, the Agent is trying to connect to the Jopr Server and register. A few things to check:

            1) Is the Jopr Server running?
            2) Are the address and port you specified for the Server correct?
            3) Can the Agent reach the Server address/port? - no firewalls blocking it, etc. Try telnet'ing to the Server address from the Agent box, e.g.: "telnet 192.168.79.34 7080"
            4) If you used a hostname for the Server address, can the Agent machine resolve that hostname, either via DNS or the hosts file? Try "nslookup jonserver.example.com" from the Agent box.
            5) Check the JON Server log to see if it logged anything regarding that Agent attempting to register.


            I use LINUX.

            1) The Jopr Server is running. I type jboss status and I get:

            [jon@s001is35 jon]$ jboss status
            RHQ Server (pid 2810) is running
            


            2) I use /sbin/ifconfig and get:
            ...
            inet addr:130.144.163.9
            ...
            


            3) I type telnet 130.144.163.9 7080 and get:
            Trying 130.144.163.9...
            Connected to s001is35.ad001.mycom.grp (130.144.163.9).
            Escape character is '^]'.
            


            and after about a minute:
            Connection closed by foreign host.
            [test@s001is35 ~]$
            
            


            Does it mean the server can be reached?

            4) I type nslookup s001is35.ad001.mycom.grp and I get:

            [test@s001is35 ~]$ nslookup s001is35.ad001.mycom.grp
            Server: 130.144.164.45
            Address: 130.144.164.45#53
            
            Name: s001is35.ad001.mycom.grp
            Address: 130.144.163.9
            
            [test@s001is35 ~]$
            
            


            I think this is ok.

            5) I open the "rhq-server-log4j.log" and it looks as follow. Seems there is nothing regarding that Agent attempting to register.
            2009-08-21 08:27:01,925 WARN [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 32, 30, 1--7d6f5cf7:c89b:49f81a28:710239-7d6f5cf7:c89b:49f81a28:71024ff7:c89b:49f81a28:70fc97overing non-serializable XAResource < 131075, 33, 31, 1--7d6f5cf7:85c4:4a111ee1:2ddcc38-7d6f5cf7:85c4:4a111ee1:2ddcc39.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 32, 30, 1--7d6f5cf7:c89b:49f81a28:7104b3-7d6f5cf7:c89b:49f81a28:7104c5g.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 33, 31, 1--7d6f5cf7:8011:4a50da3c:41c6768-7d6f5cf7:8011:4a50da3c:41c6769
            


            • 3. Re: Why it takes so lang to registrate by running ./rhq-agen
              Thomas Chang Apprentice

              Besides, as I register the agent, should I start the (agent) jboss first?

              • 4. Re: Why it takes so lang to registrate by running ./rhq-agen
                Ian Springer Master

                It shouldn't matter in what order you start the Agent and the Server.

                Please try restarting the Agent using:

                rhq-agent.sh -lu


                Then re-enter the setup info. Make sure the IP addresses are correct for both Server and Agent. If the Agent still fails to register, copy the settings you specified when prompted and paste them in here.