Frequently Asked Questions
common questions, issues, and fixes
Copyright © 2012 Red Hat, Inc.
Abstract
1. General
- Q: What is the difference between JBoss Operations Network and RHQ?
- Q: Is there a publicly available issue tracker system to search for bugs and submit enhancement requests?
- Q: What databases are supported?
- Q: Why can't I start JBoss ON with Java 5?
- Q: How can I find what my user preferences are?
- Q: What is the syntax for regular expressions used within JBoss ON?
- Q: How often does JBoss ON check the availability of resources?
- Q: Why is the JBoss ON agent waiting at startup?
- Q: How do I install a supported version of PostgreSQL on Red Hat Enterprise Linux?
- Q: How can I run SQL commands against the JBoss ON database from the JBoss ON console?
- Q: Is JBoss ON supported on VMWare?
- Q: To help debug Out Of Memory conditions, how do I get the agent or server to dump heap when it runs out of memory or on demand?
http://
server.hostname:7080/admin/test/sql.jsp
page, run this SQL command:
select id, name, string_value from rhq_config_property where configuration_id = (select configuration_id from rhq_subject where name = 'your-user-name')
rhq.agent.plugins.availability-scan.period-secs
setting. The default is 30 seconds. For performance reasons, it should never be lower than 30 seconds. It is possible to extend the scan interval by setting a new interval as one of the ADDITIONAL_JAVA_OPTIONS
values. For example:
RHQ_AGENT_ADDITIONAL_JAVA_OPTS="-Drhq.agent.plugins.availability-scan.period-secs=45"
If the agent returns this message at start up, it means that the agent is known to the server under one name but is sending a different name when it starts:
Cause: [org.rhq.core.clientapi.server.core.AgentRegistrationException:The agent asking for registration is trying to register the same address/port [172.31.7.7:16163] that is already registered under a different name [example]; if this new agent is actually the same as the original, then re-register with the same name]
--clean
and give the correct name.
This is an agent state where the server cannot be reached because the server is down or because a firewall has blocked the traffic. Make sure port 7080 on the server machine is reachable from the agent's machine. You can check this through a web browser.
An error saying that the server cannot ping the agent's endpoint means that the agent can communicate with the server, but the server cannot communicate with the agent. This may mean that the agent port is blocked by a firewall.
The server has rejected the agent registration request. Cause: [org.rhq.core.clientapi.server.core.AgentRegistrationException:Server cannot ping the agent's endpoint. The agent's endpoint is probably invalid or there is a firewall preventing the server from connecting to the agent. Endpoint: socket://172.31.7.3:12345/....
This usually means that the server has a different security token than the one the agent was sending. This could have resulted from the java preferences entry being mangled, for example, by testing with different agent versions or VMs.
11:40:48,454 WARN [CommandProcessor] {CommandProcessor.failed- authentication}Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response= [false]; config=[{rhq.security-token=1217855913569-109582636-403140853869881172, rhq.send-throttle=true}]; params= [{targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService, invocation=NameBasedInvocation[getLatestPlugins]}]
--clean
option.
Here, the agent successfully starts, but there may be other agent communication problems, like no monitoring data are sent. Trying to ping the agent command line can return an error like the following:
sending> ping Pinging... Failed to execute prompt command [ping]. Cause: org.rhq.enterprise.communications.command.server.AuthenticationException:Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.security- token=1214208960346-102975580-7334156733284942657, rhq.send-throttle=true}]; params=[{targetInterfaceName=org.rhq.enterprise.communications.Ping, invocation=NameBasedInvocation[ping]}]
Make sure the IP address of your computer can be reverse-mapped to the computer name, and that this name maps back to the same IP address. This needs to be true for all your hosts.
$ dig -x 172.31.7.7 [...] ;; ANSWER SECTION: 7.7.31.172.in-addr.arpa. 86400 IN PTR example $ $ dig example [...] ;; ANSWER SECTION: example 74030 IN A 172.31.7.7
- Log into http://rhn.redhat.com with your RHN/JBoss credentials.
- Add the Red Hat Application Stack v2 channel.
- Update the system:
sudo yum update
- Then update PostgreSQL specifically:
sudo yum install postgresql-server
Thedata
directory is installed in/var/lib/pgsql/data
. JBoss ON supports PostgreSQL 8.2.4 and later 8.2.x versions and all releases of PostgreSQL 8.3, 8.4, and 9.0. - Install and configure the JBoss ON server as normal.
http://server.example.com:7080/admin/test/sql.jsp
RHQ_AGENT_ADDITIONAL_JAVA_OPTS
or RHQ_SERVER_ADDITIONAL_JAVA_OPTS
variables).
-XX:+HeapDumpOnOutOfMemoryError -XX:+HeapDumpOnCtrlBreakTo drop the heap dump file in a particular location, add a path:
-XX:HeapDumpPath=locationSee the SUN JVM Debugging Options for more info.