JON Agent Automatic Upgrade Fails from 2.3 to 2.3.1

Solution Verified - Updated -

Issue

  • After upgrading from 2.3 to 2.3.1, the JON agent fails to upgrade because it is trying to write a file outside of the directory that it is installed in.  The JON agent on our servers is installed in /opt/jboss/rhq-agent and the JON agent tries to write the upgrade jar file to /opt/jboss, rather than /opt/jboss/rhq-agent or some other valid temporary location.  Is there a way to control where the installer tries to put the upgrade jar file, since we have intentionally removed the write but from /opt/jboss on our servers?

Environment

  • JBoss Operations Network (JON) 2.3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content