Those error messages means a transaction failed to get committed to the DB for some reason.
Off the top of my head, this immediately came to me:
See the top blue box:
RHQ currently supports versions 8.2.4 or later of PostgreSQL. Earlier 8.2 versions are not recommended. Postgres 8.1 is not supported."
Ted Whittington wrote:
On my test server, I am running an upgrade from JON 2.2.0GA to RHQ 4.0.1.
Note you are mixing fish with foul here. JON is the supported middleware management product from Red Hat, RHQ is the upstream open source project. There are no expectations you can upgrade between the two. Normally you would go JON2.2.0.GA -> JON2.4.0.GA or RHQ 3.0.0 -> RHQ4.0.1 for example. And even on the RHQ side because we can make significant changes in the upstream project there are no guarantees of upgradeability across versions, though we do try.
So the only scenario you can have a rock solid expectation of being able to upgrade across arbitrary versions is with the JON product.
Just an update, I could not get any version to work, even the same version with data copied (via pg_dump) from the production server. All of the installs seemed to go into a loop. Process: stop jon, stop/start postgres, delete jon directory, unzip install server (2.2.0, 2.4.0,2.4.1,3.0, 4.0, 4.0.1 all tried), psql rhq < dumpfile, start jon via rhq-server.sh, bring up localhost:7080, make change, start upgrade. EVERY one failed, even the same version (from the same install) 2.2.0GA. Process would run indefinitely (24 hours for one before I cancelled it).
We decided to install 4.0.1 and start from scratch. As a newbie I must have done something wrong, but it is scarey if I have to restore, I might not be able to do so.
Forgot the step, after restart of postgres, I dropped and created the rhq database.