Hi!
Are there any limit of how many services can be defined for a Platform?
Sometimes I loose the ability to create a new entry, like adding a ping service f.e.
I can add one (ping) for another Platform, but many times I can only add Clobber and Process plugins for linux Platforms especially.
I guess it isn't a limit, since in a situation like this deleting a ping service doesn't mean I can add another instead. I can modify one which already exists, and maybe next time I will also be able to add, but sometimes I just see an almost empty list.
A use right mouse button over the Platform's name while the Platforms page is open, and navigate down to the Import line.
Attila
Le 19/11/2013 13:33, Attila Heidrich a écrit :
Hi!
Are there any limit of how many services can be defined for a Platform?
Sometimes I loose the ability to create a new entry, like adding a ping service f.e.
I can add one (ping) for another Platform, but many times I can only add Clobber and Process plugins for linux Platforms especially.
I guess it isn't a limit, since in a situation like this deleting a ping service doesn't mean I can add another instead. I can modify one which already exists, and maybe next time I will also be able to add, but sometimes I just see an almost empty list.
A use right mouse button over the Platform's name while the Platforms page is open, and navigate down to the Import line.
Attila
Hi,
I'm not sure I get you. I have no issue when I try to import multiple "Port" or "Ping" services.
Can you please post a reproduction scenario with details on the platforms used?
Thanks, Thomas
Am 19.11.2013 18:38, schrieb Thomas Segismont:
Le 19/11/2013 13:33, Attila Heidrich a écrit :
Hi!
Are there any limit of how many services can be defined for a Platform?
Sometimes I loose the ability to create a new entry, like adding a ping service f.e.
I can add one (ping) for another Platform, but many times I can only add Clobber and Process plugins for linux Platforms especially.
I guess it isn't a limit, since in a situation like this deleting a ping service doesn't mean I can add another instead. I can modify one which already exists, and maybe next time I will also be able to add, but sometimes I just see an almost empty list.
A use right mouse button over the Platform's name while the Platforms page is open, and navigate down to the Import line.
Attila
Hi,
I'm not sure I get you. I have no issue when I try to import multiple "Port" or "Ping" services.
Can you please post a reproduction scenario with details on the platforms used?
Maybe Attila experienced the same behavior as I see sometimes with RHQ 4.9.0.
The list of importable items is reduced to two items (Cobbler and Twitter, if I remember correct) without any reason. Switching to another menu item and back to the inventory sometimes helps. Sometimes only a logout and a new login brings back the full list of importable items.
Just my 2 cents.
Elmar
Le 19/11/2013 19:10, Elmar Knipp a écrit :
Maybe Attila experienced the same behavior as I see sometimes with RHQ 4.9.0.
The list of importable items is reduced to two items (Cobbler and Twitter, if I remember correct) without any reason. Switching to another menu item and back to the inventory sometimes helps. Sometimes only a logout and a new login brings back the full list of importable items.
Just my 2 cents.
Elmar
This problem sounds familiar but we could not find a BZ for it. Apparently it has been fixed in master, indirectly from another commit.
Thomas
Hi!
usually I can import several ones ones too, but sometimes the I experience the one Elmar also described.
My subject could be confusing, since I can deploy any number of "process" any time, but sometimes this is the only plugin I can select to import, so no way to import a new (let's say) ping service.
Restarting the browser usually helps, but it is really annoying.
Attila
2013/11/20 Thomas Segismont tsegismo@redhat.com
Le 19/11/2013 19:10, Elmar Knipp a écrit :
Maybe Attila experienced the same behavior as I see sometimes with RHQ
4.9.0.
The list of importable items is reduced to two items (Cobbler and Twitter, if I remember correct) without any reason. Switching to another menu item and back to the inventory sometimes helps. Sometimes only a logout and a new login brings back the full list of importable items.
Just my 2 cents.
Elmar
This problem sounds familiar but we could not find a BZ for it. Apparently it has been fixed in master, indirectly from another commit.
Thomas
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
I've been going through the 4.8 to 4.9 upgrade with varying success.
First, Never saw a mention of python 2.5+ as a requirement and it appears to be. This install is on a CentOS 5.8 server which didn't have it in the base yum repo. Added 2.6 via EPEL. Might want to note that.
I believe RHQ 4.9 still supports java 6, but the 4.8 tool appears to require java 7. I got version mismatch errors.
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/cassandra/tools/NodeCmd : Unsupported major.minor version 51.0
Solved with install of JDK 1.7
Now I get the following. Any direction on how to solve the Bad Request?
-------------------------- Running CQL script to disable table compression ./disable_compression.cql:9:Bad Request: Cannot ALTER <table system_auth.credentials> ./disable_compression.cql:9:text could not be lexed at line 1, char 56 ./disable_compression.cql:10:Bad Request: Cannot ALTER <table system_auth.permissions> ./disable_compression.cql:10:text could not be lexed at line 1, char 56 ./disable_compression.cql:11:Bad Request: Cannot ALTER <table system_auth.users> ./disable_compression.cql:11:text could not be lexed at line 1, char 50 ./disable_compression.cql:12:Bad Request: Cannot ALTER <table system_auth.users> ./disable_compression.cql:12:text could not be lexed at line 1, char 50 ./disable_compression.cql:14:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:14:text could not be lexed at line 1, char 53 ./disable_compression.cql:15:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:15:text could not be lexed at line 1, char 55 ./disable_compression.cql:16:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:16:text could not be lexed at line 1, char 55 ./disable_compression.cql:18:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:18:text could not be lexed at line 1, char 20 ./disable_compression.cql:19:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:19:text could not be lexed at line 1, char 20 ./disable_compression.cql:20:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:20:text could not be lexed at line 1, char 20 ./disable_compression.cql:21:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:21:text could not be lexed at line 1, char 20 ./disable_compression.cql:22:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:22:text could not be lexed at line 1, char 20 ./disable_compression.cql:23:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:23:text could not be lexed at line 1, char 20 ./disable_compression.cql:24:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:24:text could not be lexed at line 1, char 48 ./disable_compression.cql:25:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:25:text could not be lexed at line 1, char 45 ./disable_compression.cql:26:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:26:text could not be lexed at line 1, char 45 ./disable_compression.cql:27:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:27:text could not be lexed at line 1, char 51 ./disable_compression.cql:28:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:28:text could not be lexed at line 1, char 45 ./disable_compression.cql:29:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:29:text could not be lexed at line 1, char 51 ./disable_compression.cql:30:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:30:text could not be lexed at line 1, char 61 ./disable_compression.cql:31:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:31:text could not be lexed at line 1, char 54 ./disable_compression.cql:32:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:32:text could not be lexed at line 1, char 56 Rebuilding data files for system keyspace Rebuilding data files for system_traces keyspace Rebuilding data files for system_auth keyspace Rebuilding data files for rhq keycap Shutting down the RHQ Storage node 23:20:15,030 INFO [org.jboss.modules] JBoss Modules version 1.2.0.CR1 Stopping RHQ storage node... RHQ storage node (pid=11287) is stopping... kill 11287: No such process 23:20:16,598 ERROR [org.rhq.server.control.RHQControl] Failed to stop services [Cause: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)] Removing patch file Table compression has been disabled for all keyspaces. You are now ready to upgrade your RHQ installation.
The patch script temporarily replaces <rhq-server-dir>/rhq-storage/lib/apache-cassandra-1.2.4.jar with a patched version that will allow the script to make schema changes to the system keyspace. You might want to check that the patched JAR file is in fact being used. You could add the following on line 67 of rhq48-storage-patch.sh,
echo `md5 $RHQ_SERVER_DIR/rhq-storage/lib/apache-cassandra-1.2.4.jar`
The checksum should be 274cb7c00558ba7bd742da1c8910869e
On Nov 20, 2013, at 7:21 AM, Matt Warren mwarren@hnw.com wrote:
I've been going through the 4.8 to 4.9 upgrade with varying success.
First, Never saw a mention of python 2.5+ as a requirement and it appears to be. This install is on a CentOS 5.8 server which didn't have it in the base yum repo. Added 2.6 via EPEL. Might want to note that.
I believe RHQ 4.9 still supports java 6, but the 4.8 tool appears to require java 7. I got version mismatch errors.
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/cassandra/tools/NodeCmd : Unsupported major.minor version 51.0
Solved with install of JDK 1.7
Now I get the following. Any direction on how to solve the Bad Request?
Running CQL script to disable table compression ./disable_compression.cql:9:Bad Request: Cannot ALTER <table system_auth.credentials> ./disable_compression.cql:9:text could not be lexed at line 1, char 56 ./disable_compression.cql:10:Bad Request: Cannot ALTER <table system_auth.permissions> ./disable_compression.cql:10:text could not be lexed at line 1, char 56 ./disable_compression.cql:11:Bad Request: Cannot ALTER <table system_auth.users> ./disable_compression.cql:11:text could not be lexed at line 1, char 50 ./disable_compression.cql:12:Bad Request: Cannot ALTER <table system_auth.users> ./disable_compression.cql:12:text could not be lexed at line 1, char 50 ./disable_compression.cql:14:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:14:text could not be lexed at line 1, char 53 ./disable_compression.cql:15:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:15:text could not be lexed at line 1, char 55 ./disable_compression.cql:16:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:16:text could not be lexed at line 1, char 55 ./disable_compression.cql:18:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:18:text could not be lexed at line 1, char 20 ./disable_compression.cql:19:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:19:text could not be lexed at line 1, char 20 ./disable_compression.cql:20:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:20:text could not be lexed at line 1, char 20 ./disable_compression.cql:21:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:21:text could not be lexed at line 1, char 20 ./disable_compression.cql:22:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:22:text could not be lexed at line 1, char 20 ./disable_compression.cql:23:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:23:text could not be lexed at line 1, char 20 ./disable_compression.cql:24:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:24:text could not be lexed at line 1, char 48 ./disable_compression.cql:25:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:25:text could not be lexed at line 1, char 45 ./disable_compression.cql:26:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:26:text could not be lexed at line 1, char 45 ./disable_compression.cql:27:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:27:text could not be lexed at line 1, char 51 ./disable_compression.cql:28:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:28:text could not be lexed at line 1, char 45 ./disable_compression.cql:29:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:29:text could not be lexed at line 1, char 51 ./disable_compression.cql:30:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:30:text could not be lexed at line 1, char 61 ./disable_compression.cql:31:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:31:text could not be lexed at line 1, char 54 ./disable_compression.cql:32:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:32:text could not be lexed at line 1, char 56 Rebuilding data files for system keyspace Rebuilding data files for system_traces keyspace Rebuilding data files for system_auth keyspace Rebuilding data files for rhq keycap Shutting down the RHQ Storage node 23:20:15,030 INFO [org.jboss.modules] JBoss Modules version 1.2.0.CR1 Stopping RHQ storage node... RHQ storage node (pid=11287) is stopping... kill 11287: No such process 23:20:16,598 ERROR [org.rhq.server.control.RHQControl] Failed to stop services [Cause: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)] Removing patch file Table compression has been disabled for all keyspaces. You are now ready to upgrade your RHQ installation.
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
Thanks, that fixed that problem. On to others.
Not sure if I'm in an incomplete state or not. I've run the steps of the script but now likely in the wrong order. Does that matter? The initial script runs completed the nodetool steps but failed on parts of the cqlsh file. With this fix, I ran the cqlsh manually and it completed without error.
Is there in any harm in running the whole patch file again after partial success and failures?
What I find now in attempting the rhqctl upgrade is that it stalls with a series of these errors:
16:13:41,794 INFO [org.rhq.cassandra.schema.TopologyManager] Starting to execute UpdateGCGrace task. 16:13:41,794 INFO [org.rhq.cassandra.schema.AbstractManager] Applying update file: org.rhq.cassandra.schema.UpdateFile@5ab41ea 16:13:41,797 INFO [org.rhq.cassandra.schema.AbstractManager] Statement:
ALTER COLUMNFAMILY rhq.metrics_index WITH gc_grace_seconds = 0
16:13:41,814 INFO [org.rhq.cassandra.schema.AbstractManager] Shutting down existing cluster connections 16:13:41,822 ERROR [org.rhq.enterprise.server.installer.InstallerServiceImpl] Could not complete Cassandra schema installation: unconfigured columnfamily metrics_index: com.datastax.driver.core.exceptions.InvalidQueryException: unconfigured columnfamily metrics_index at com.datastax.driver.core.exceptions.InvalidQueryException.copy(InvalidQuery Exception.java:35) [cassandra-driver-core-1.0.2.jar:]
[snipped the full stack]
It then stalls waiting with:
16:28:24,764 INFO [org.rhq.server.control.command.Upgrade] Still waiting for server to start...
I can see that the server started seemingly fine from server.log (except for this first line):
16:27:47,446 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 58) HQ121006: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "dev01.hnw.com". If this new address is incorrect please manually configure the connector to use the proper one. 16:27:47,447 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 16:27:47,491 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010406: Registered connection factory java:/JmsXA 16:27:47,533 INFO [org.hornetq.ra] (MSC service thread 1-8) HornetQ resource adaptor started 16:27:47,534 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorS ervice$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra 16:27:47,538 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] 16:27:47,648 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:6990/management 16:27:47,648 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:6990 16:27:47,648 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.Alpha1 (AS 7.2.0.Alpha1-redhat-4) started in 5203ms - Started 151 of 210 services (58 services are passive or on-demand)
I typically run RHQ on a specific IP of this server and the properties file has that declared.
If this error is related to the unclean casandra data patch, I can hopefully fix that. I wonder if it's just the issue of the IP for the "Invalid host value detected for netty connector" But then, how do I set an IP value for this org.hornetq.jms.server?
Thanks, Matt
On 11/25/13, 9:46 AM, "John Sanda" jsanda@redhat.com wrote:
The patch script temporarily replaces <rhq-server-dir>/rhq-storage/lib/apache-cassandra-1.2.4.jar with a patched version that will allow the script to make schema changes to the system keyspace. You might want to check that the patched JAR file is in fact being used. You could add the following on line 67 of rhq48-storage-patch.sh,
echo `md5 $RHQ_SERVER_DIR/rhq-storage/lib/apache-cassandra-1.2.4.jar`
The checksum should be 274cb7c00558ba7bd742da1c8910869e
On Nov 20, 2013, at 7:21 AM, Matt Warren mwarren@hnw.com wrote:
I've been going through the 4.8 to 4.9 upgrade with varying success.
First, Never saw a mention of python 2.5+ as a requirement and it appears to be. This install is on a CentOS 5.8 server which didn't have it in the base yum repo. Added 2.6 via EPEL. Might want to note that.
I believe RHQ 4.9 still supports java 6, but the 4.8 tool appears to require java 7. I got version mismatch errors.
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/cassandra/tools/NodeCmd : Unsupported major.minor version 51.0
Solved with install of JDK 1.7
Now I get the following. Any direction on how to solve the Bad Request?
Running CQL script to disable table compression ./disable_compression.cql:9:Bad Request: Cannot ALTER <table system_auth.credentials> ./disable_compression.cql:9:text could not be lexed at line 1, char 56 ./disable_compression.cql:10:Bad Request: Cannot ALTER <table system_auth.permissions> ./disable_compression.cql:10:text could not be lexed at line 1, char 56 ./disable_compression.cql:11:Bad Request: Cannot ALTER <table system_auth.users> ./disable_compression.cql:11:text could not be lexed at line 1, char 50 ./disable_compression.cql:12:Bad Request: Cannot ALTER <table system_auth.users> ./disable_compression.cql:12:text could not be lexed at line 1, char 50 ./disable_compression.cql:14:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:14:text could not be lexed at line 1, char 53 ./disable_compression.cql:15:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:15:text could not be lexed at line 1, char 55 ./disable_compression.cql:16:Bad Request: system_traces keyspace is not user-modifiable. ./disable_compression.cql:16:text could not be lexed at line 1, char 55 ./disable_compression.cql:18:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:18:text could not be lexed at line 1, char 20 ./disable_compression.cql:19:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:19:text could not be lexed at line 1, char 20 ./disable_compression.cql:20:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:20:text could not be lexed at line 1, char 20 ./disable_compression.cql:21:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:21:text could not be lexed at line 1, char 20 ./disable_compression.cql:22:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:22:text could not be lexed at line 1, char 20 ./disable_compression.cql:23:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:23:text could not be lexed at line 1, char 20 ./disable_compression.cql:24:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:24:text could not be lexed at line 1, char 48 ./disable_compression.cql:25:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:25:text could not be lexed at line 1, char 45 ./disable_compression.cql:26:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:26:text could not be lexed at line 1, char 45 ./disable_compression.cql:27:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:27:text could not be lexed at line 1, char 51 ./disable_compression.cql:28:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:28:text could not be lexed at line 1, char 45 ./disable_compression.cql:29:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:29:text could not be lexed at line 1, char 51 ./disable_compression.cql:30:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:30:text could not be lexed at line 1, char 61 ./disable_compression.cql:31:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:31:text could not be lexed at line 1, char 54 ./disable_compression.cql:32:Bad Request: system keyspace is not user-modifiable. ./disable_compression.cql:32:text could not be lexed at line 1, char 56 Rebuilding data files for system keyspace Rebuilding data files for system_traces keyspace Rebuilding data files for system_auth keyspace Rebuilding data files for rhq keycap Shutting down the RHQ Storage node 23:20:15,030 INFO [org.jboss.modules] JBoss Modules version 1.2.0.CR1 Stopping RHQ storage node... RHQ storage node (pid=11287) is stopping... kill 11287: No such process 23:20:16,598 ERROR [org.rhq.server.control.RHQControl] Failed to stop services [Cause: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)] Removing patch file Table compression has been disabled for all keyspaces. You are now ready to upgrade your RHQ installation.
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
There is no harm in running the patch script again. Can you do the following and share the output,
Make sure start_rpc in cassandra is set to true If start_rpc was false restart the storage node after saving cassandra.yaml in terminal run, export CQLSH_HOST=<your_hostname> cqlsh -u rhqadmin -p rhqadmin use rhq; describe table metrics_index;
On Nov 25, 2013, at 4:42 PM, Matt Warren mwarren@hnw.com wrote:
uncon
Should this be done in the 4.8 server directory or the new 4.9? 4.9 has not successfully completed the install process.
There is no harm in running the patch script again. Can you do the following and share the output,
1. Make sure start_rpc in cassandra is set to true 2. If start_rpc was false restart the storage node after saving cassandra.yaml 3. in terminal run, export CQLSH_HOST=<your_hostname> 4. cqlsh -u rhqadmin -p rhqadmin 5. use rhq; 6. describe table metrics_index;
On Nov 25, 2013, at 4:42 PM, Matt Warren <mwarren@hnw.commailto:mwarren@hnw.com> wrote:
uncon
Run against the 4.8 server install.
On Nov 26, 2013, at 8:05 AM, Matt Warren mwarren@hnw.com wrote:
Should this be done in the 4.8 server directory or the new 4.9? 4.9 has not successfully completed the install process.
There is no harm in running the patch script again. Can you do the following and share the output,
- Make sure start_rpc in cassandra is set to true
- If start_rpc was false restart the storage node after saving cassandra.yaml
- in terminal run, export CQLSH_HOST=<your_hostname>
- cqlsh -u rhqadmin -p rhqadmin
- use rhq;
- describe table metrics_index;
On Nov 25, 2013, at 4:42 PM, Matt Warren <mwarren@hnw.commailto:mwarren@hnw.com> wrote:
uncon
rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users@lists.stg.fedorahosted.org
-
Attila Heidrich -
Elmar Knipp -
John Sanda -
Matt Warren -
Thomas Segismont