hypermike
Contributor
Contributor

New upgrade instructions for going from beta 3.0 xxx to beta 3.0 yyy CLIENT

In looking at the latest instructions for upgrading from BEta 3.0 24x to 260 it looks like
the instructions need to use the installer and NOT just the new agent . Can I download the
260 agent tar file only and upgrade to this new version on a client ONLY system . NOT the
HYPERIC server system ????
0 Kudos
4 Replies
cwitt_hyperic
Hot Shot
Hot Shot

The hyperic-hq-installer files are for the server installation. More specifically, these bundles contain HQ server, agent, and shell. You need this installer only for the server system. For your agent systems, you can use the much smaller hyperic-hq-agent bundles specific to the platform architectures on which you are installing.
hypermike
Contributor
Contributor

I dont see a setup script for clients. I guess you have to blow everything away and install
the newer client as one did the original. Also the fact that you cant upgrade the server without
creating new directories (affects many things and a better way should have beed devised).
Startup scripts ,links , home directories (since root cant run hyperic )of the owner of hyperic directory muust change affecting password and shadow files). NOT good. When instructions
for installing the beta was created one should have been told to create a build1 directory under the hyperic directory to start with.
0 Kudos
cwitt_hyperic
Hot Shot
Hot Shot

You are correct about the agent upgrade installation. There is no setup script. One need only run the agent, and set it up as you did initially. It is possible for agent properties to survive upgrades, but one must plan for this by creating .hq/agent.properties according to the HQ Agent Configuration documentation (http://support.hyperic.com/confluence/display/DOCSHQ30/HQ+Agent+Configuration).

From your description, it sounds as if you made the installed HQ server directory the home directory of the user running the server instead of configuring the server directory to be a subdirectory of the home directory. I can see how this might cause some headaches. The installer should ask the installation path for the server (e.g. /home/hq), and then put a sever-3.0.0 directory within that path (e.g. /home/hq/server-3.0.0). If you follow this course, it should have no implications on passwd and shadow files, or on the home directory of the user configured to run the software.

Start-up scripts and other things referencing the server directory would break in the scenario where the directories change names during upgrade, but this can be mitigated through the use of a symbolic link that points to the current server directory for such things relying on the path. For example, creating a symbolic link to server-3.0.0 called server-current, then referencing server-current for things like start-up scripts, etc. In this example, changes to where your start-up scripts look to start HQ can be made by updating the server-current symbolic link after the upgrade is complete.

For the betas that have been upgradeable (i.e. 236 to 242), I've simply been shutting down the old server, moving that directory out of the way by renaming it, then performing the `setup.sh -upgrade`. During the process you are asked where the server you are upgrading from is located, you then tell it the renamed directory path of the old server, and it finds your database and performs the upgrade as expected.

I know that documentation is going to continue to be updated prior to moving 3.0.0 beyond beta, so we will certainly examine the installation instructions as a point for further clarification. Thank you for sharing your experience.
hypermike
Contributor
Contributor

Does this mean I cant upgrade 242 to 260???
I thus lose all alerts, accounts,graphs that I created this month ???

Beta 3, Build 260
Due to a number of major changes Beta 3 must be installed from scratch. Beta 3 can not upgrade from earlier Beta releases.
0 Kudos