Bug 1073990 - cannot access postgres 9.2 internal statistics
Summary: cannot access postgres 9.2 internal statistics
Keywords:
Status: CLOSED DUPLICATE of bug 1079361
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- Other
Version: JON 3.2.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: DR01
: JON 3.2.2
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 988800
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-07 15:45 UTC by Mike Foley
Modified: 2014-05-07 14:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 988800
Environment:
Last Closed: 2014-05-07 14:39:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mike Foley 2014-03-07 15:45:15 UTC
+++ This bug was initially created as a clone of Bug #988800 +++

Description of problem:
postgres statistics cannot be retrieved from 9.2 server.

Version-Release number of selected component (if applicable):
RHQ is 4.8 "factory" version, no elements has been changed over the distribution

How reproducible:
just use the postgresql server plugin

Steps to Reproduce:
1. inventory a postgres server (server version should be 9.2)
2. look at the metrics
3. say "wow!"

Actual results:
any data but "active backend" results "no-data" or something unusable (1119% for the CPU usage and 99GB for Virtual memory usage)

Expected results:
pls look at the attached screenshot

Additional info:

http://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.2#pg_stat_activity_and_pg_stat_replication.27s_definitions_have_changed

org.postgresql.util.PSQLException: ERROR: column "current_query" does not exist
  Position: 41
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
	at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
	at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
	at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:283)
	at org.rhq.plugins.postgres.PostgresServerComponent.invokeOperation(PostgresServerComponent.java:361)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)

Comment 2 Thomas Segismont 2014-05-07 14:39:15 UTC

*** This bug has been marked as a duplicate of bug 1079361 ***


Note You need to log in before you can comment on or make changes to this bug.