Hi all,
I'm using Hyperic HQ Server 4.2.0 running on CentOS 5.4 to monitor WebLogic Admin 8.1 running on CentOS 4. I'm able to connect agent to server and monitor system performance (CPU, memory, some applications etc). AutoDiscovery is working beautifully, detecting all my WebLogic's domains as well as the paths of log files and startup scripts, leaving to me the simple task of setting username and password for admin server access. But when I change these properties and click OK, all that I get is the following error message, after waiting several minutes:
The configuration has not been set for this resource due to : Agent error: Unable to connect to <IP of WebLogic Admin server>:2144: Read timed out
I certified that the 2144 TCP port is opened on the WebLogic Admin server, and so if it is accessible from the Hyperic HQ server. All other resources (CPU, memory, network etc) are being monitored, so I can't understand why Hyperic says that can't connect to agent.
I appreciate any suggestions on what I can do to discover what is the matter. If I must to provide more information, like log files content, just ask for it.
Thanks,
Davidson Paulo
I'm using Hyperic HQ Server 4.2.0 running on CentOS 5.4 to monitor WebLogic Admin 8.1 running on CentOS 4. I'm able to connect agent to server and monitor system performance (CPU, memory, some applications etc). AutoDiscovery is working beautifully, detecting all my WebLogic's domains as well as the paths of log files and startup scripts, leaving to me the simple task of setting username and password for admin server access. But when I change these properties and click OK, all that I get is the following error message, after waiting several minutes:
The configuration has not been set for this resource due to : Agent error: Unable to connect to <IP of WebLogic Admin server>:2144: Read timed out
I certified that the 2144 TCP port is opened on the WebLogic Admin server, and so if it is accessible from the Hyperic HQ server. All other resources (CPU, memory, network etc) are being monitored, so I can't understand why Hyperic says that can't connect to agent.
I appreciate any suggestions on what I can do to discover what is the matter. If I must to provide more information, like log files content, just ask for it.
Thanks,
Davidson Paulo