Attachment 950931 Details for Bug 1157480 – upgrade output

upgrade output

upgrade.out (text/plain), 8.92 KB, created by Filip Brychta on 2014-10-27 10:22:00 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Filip Brychta

Created: 2014-10-27 10:22:00 UTC

Size: 8.92 KB

patch

obsolete

>04:47:52,722 INFO  [org.jboss.modules] JBoss Modules version 1.3.3.Final-redhat-1
>04:47:53,006 INFO  [org.rhq.server.control.command.Upgrade] Stopping any running RHQ components...
>04:47:53,887 INFO  [org.jboss.modules] JBoss Modules version 1.2.2.Final-redhat-1
>04:47:54,156 INFO  [org.rhq.server.control.command.Upgrade] The old installation components have been stopped
>Starting RHQ Storage Installer ...
>04:48:25,220 INFO  [org.jboss.modules] JBoss Modules version 1.3.3.Final-redhat-1
>04:48:25,473 INFO  [org.rhq.storage.installer.StorageInstaller] Running RHQ Storage Node installer...
>04:48:25,512 INFO  [org.rhq.cassandra.Deployer] Unzipping storage node to /home/hudson/jon-server-3.3.0.ER05/rhq-storage
>04:48:26,215 INFO  [org.rhq.cassandra.Deployer] Applying configuration changes to /home/hudson/jon-server-3.3.0.ER05/rhq-storage/conf/cassandra.yaml
>04:48:26,397 INFO  [org.rhq.cassandra.Deployer] Applying configuration changes to /home/hudson/jon-server-3.3.0.ER05/rhq-storage/conf/log4j-server.properties
>04:48:26,419 INFO  [org.rhq.cassandra.Deployer] Applying configuration changes to /home/hudson/jon-server-3.3.0.ER05/rhq-storage/conf/cassandra-jvm.properties
>04:48:26,444 INFO  [org.rhq.cassandra.Deployer] Updating file permissions in /home/hudson/jon-server-3.3.0.ER05/rhq-storage/bin
>04:48:27,063 INFO  [org.rhq.storage.installer.StorageInstaller] Updating rhq-server.properties...
>Exception in thread "main" java.lang.RuntimeException: Unable to update Storage Node [fbr-ha-st.bc.jonqe.lab.eng.bos.redhat.com] to version [4.12.0.JON330ER05]
>	at org.rhq.storage.installer.StorageInstaller.updateStorageNodeVersion(StorageInstaller.java:1085)
>	at org.rhq.storage.installer.StorageInstaller.stampStorageNodeVersion(StorageInstaller.java:1055)
>	at org.rhq.storage.installer.StorageInstaller.run(StorageInstaller.java:283)
>	at org.rhq.storage.installer.StorageInstaller.main(StorageInstaller.java:1130)
>	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.jboss.modules.Module.run(Module.java:312)
>	at org.jboss.modules.Main.main(Main.java:460)
>Caused by: org.postgresql.util.PSQLException: ERROR: relation "rhq_storage_node" does not exist
>  Position: 15
>	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:417)
>	at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
>	at org.rhq.core.db.DatabaseType.checkColumnExists(DatabaseType.java:249)
>	at org.rhq.core.db.upgrade.StorageNodeVersionColumnUpgrader.upgrade(StorageNodeVersionColumnUpgrader.java:47)
>	at org.rhq.storage.installer.StorageInstaller.updateStorageNodeVersion(StorageInstaller.java:1078)
>	... 9 more
>04:48:27,784 INFO  [org.rhq.server.control.command.Upgrade] The storage node upgrade has finished with an exit value of 1
>04:48:27,785 INFO  [org.rhq.server.control.command.Upgrade] Ignoring server upgrade, the '--from-server-dir' is a storage node only installation.
>04:48:27,786 INFO  [org.rhq.server.control.command.Upgrade] Upgrading RHQ agent located at: /home/hudson/rhq-agent
>======================================
>ANT target [backup-agent]
>Mon Oct 27 04:48:28 EDT 2014
>======================================
>[backup-agent] [echo] === BACKING UP CURRENT AGENT ===
>[backup-agent] [echo] From: /home/hudson/rhq-agent
>[backup-agent] [echo] To: /tmp/rhq-agent-update-backup
>[backup-agent] [copy] Copying 119 files to /tmp/rhq-agent-update-backup
>[backup-agent] [copy] Copied 18 empty directories to 2 empty directories under /tmp/rhq-agent-update-backup
>[backup-agent] [echo] === BACKUP OF CURRENT AGENT COMPLETE ===
>======================================
>ANT target [(default)]
>Mon Oct 27 04:48:29 EDT 2014
>======================================
>[header-for-update] [echo] 
>===== RHQ AGENT UPDATE =====
>Agent To Be Updated: /home/hudson/rhq-agent
>Version: 4.12.0.JON330ER05
>Build Number: 2cdb528
>Jar File: /home/hudson/jon-server-3.3.0.ER05/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-downloads/rhq-agent/rhq-enterprise-agent-4.12.0.JON330ER05.jar
>[update] [echo] Extract the agent distro zip from the agent update binary, place in temporary update dir
>[update] [unjar] Expanding: /home/hudson/jon-server-3.3.0.ER05/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-downloads/rhq-agent/rhq-enterprise-agent-4.12.0.JON330ER05.jar into /home/hudson/rhq-agent/update-2cdb528
>[update] [echo] Unzip the agent distro into the temporary update directory
>[update] [unzip] Expanding: /home/hudson/rhq-agent/update-2cdb528/rhq-enterprise-agent-4.12.0.JON330ER05.zip into /home/hudson/rhq-agent/update-2cdb528
>[update] [echo] Remove the agent distro zip
>[update] [delete] Deleting: /home/hudson/rhq-agent/update-2cdb528/rhq-enterprise-agent-4.12.0.JON330ER05.zip
>[update] [echo] 
>      At this point, we have the new (but raw) agent extracted to: /home/hudson/rhq-agent/update-2cdb528/rhq-agent
>      The old, existing agent (the one we are upgrading) is at: /home/hudson/rhq-agent
>      
>[update] [echo] Copy existing failover list from the old agent to the new agent
>[update] [copy] Copying 1 file to /home/hudson/rhq-agent/update-2cdb528/rhq-agent/data
>[update] [echo] Copy existing keystore and truststore files from the old agent to the new agent
>[update] [echo] Copy existing Java Service Wrapper configuration files from the old agent to the new agent
>[update] [echo] Copy Windows environment script - keep the old copy in effect and backup the new copy
>[update] [copy-with-backup] old file and new file are the same, nothing to do
>[update] [echo] Copy UNIX environment script - keep the old copy in effect and backup the new copy
>[update] [copy-with-backup] files differ, keeping old, backing up new
>[update] [echo] Copy Windows wrapper launch script - use the new copy and backup the old copy
>[update] [copy-with-backup] files differ, keeping new, backing up old
>[update] [echo] Copy UNIX wrapper launch script - use the new copy and backup the old copy
>[update] [copy-with-backup] files differ, keeping new, backing up old
>[update] [echo] Copy Java Service Wrapper configuration - use the new copy and backup the old copy
>[update] [copy-with-backup] files differ, keeping new, backing up old
>[update] [echo] Copy custom scripts that may have existed in the agent bin directory
>[update] [echo] Ensure any custom scripts that were copied retain execute permissions
>[update] [echo] Copy agent configuration file - use the old copy and backup the new copy
>[update] [copy-with-backup] files differ, keeping old, backing up new
>[update] [echo] Copy log4j configuration file - use the old copy and backup the new copy
>[update] [copy-with-backup] files differ, keeping old, backing up new
>[update] [echo] 
>      Everything is done; _update.tmp.dir/rhq-agent has our new agent.
>      The old agent is still intact, albeit with a new update subdirectory with the new agent in it.
>      Start moving things around to get the new agent in the old agent's directory.
>      If anything fails going forward, bad things will happen because the old agent will be ruined.
>      
>[update] [echo] Define where we are going to put the old agent - this is where the old agent will be backed up
>[update] [echo] Purge any previously backed-up old agent
>[update] [echo] Move the old agent to the backup location
>[update] [echo] Make sure the location where the new agent is going to be is empty
>[update] [echo] Put the new agent in its new location: [/home/hudson/rhq-agent-OLD/update-2cdb528/rhq-agent] to [/home/hudson/rhq-agent]
>[update] [echo] Clean up the temporary location where the new agent was located (but no longer is)
>[update] [delete] Deleting directory /home/hudson/rhq-agent-OLD/update-2cdb528
>[update] [echo] 
>      At this point, the new agent should now be at the old agent's location.
>      The old agent is backed up to the rhq-agent-OLD directory next to new agent
>      
>[update] [echo] chmod +x on executables under /home/hudson/rhq-agent
>[update] [echo] The agent is updated and we don't need the backup anymore, so remove the first backup we made
>[update] [delete] Deleting directory /tmp/rhq-agent-update-backup
>[update] [echo] 
>      FINISHED UPDATING THE AGENT SUCCESSFULLY!
>      The new agent is now located at: /home/hudson/rhq-agent
>      
>04:48:30,689 INFO  [org.rhq.server.control.command.Upgrade] The agent installer finished updating with exit value 0
>04:48:30,689 INFO  [org.rhq.server.control.command.Upgrade] The agent has been upgraded and placed in: /home/hudson/rhq-agent
>RHQ Server                     (no pid file) is âdown

Actions: View

Attachments on bug 1157480: 950931