Difference between revisions of "4.2.4 Upgrade"

From Zenoss Wiki
Jump to: navigation, search
m (Daniel Robbins moved page 4.4.4 Upgrade to 4.2.4 Upgrade)
(Upgrading to Zenoss 4.2.4)
Line 1: Line 1:
 +
 
== Upgrading to Zenoss 4.2.4 ==
 
== Upgrading to Zenoss 4.2.4 ==
  
 
I found the instructions for performing an upgrade to 4.2.4 were rather diffuse.
 
I found the instructions for performing an upgrade to 4.2.4 were rather diffuse.
  
There are some comments on the wiki page here - [http://wiki.zenoss.org/Install_Zenoss]
+
There are some comments on the wiki page here - [http://wiki.zenoss.org/Install_Zenoss Install Zenoss]
 +
 
 
The main instructions are in the installation guide which you can get which is referenced on the above page - {{doc|for=Zenoss Core 4.2.x|title=Zenoss Core 4 Installation Guide}}
 
The main instructions are in the installation guide which you can get which is referenced on the above page - {{doc|for=Zenoss Core 4.2.x|title=Zenoss Core 4 Installation Guide}}
 +
 +
These instructions say you need to install the new utility called ZenUp (which I believe is still beta code at August 9th 2013).  It references the Zenoss Service Dynamics ZenUp Installation and Administration manual (and this is not a hyperlink) and obviously is less than appropriate for Core users; however, there is a good ZenUp reference here on the wiki at [http://wiki.zenoss.org/ZenUp ZenUp].
 +
 +
I started from a community script installation of Zenoss 4.2.3 on CentOs 6.3.  Start from Chapter 5 of the installation Guide.  These are my comments / updates on those instructions.
 +
 +
* You should definitely have taken a Zenoss backup before you get to upgrading but..... there is a bug with 4.2.3 that prevents zenbackup from running cleanly. The fix (as the zenoss user) is:
 +
** mysql -u root
 +
** GRANT SELECT ON mysql.proc to zenoss;
 +
 +
* additional notes to the ZenUp wiki item:
 +
** Installing ZenUp creates a zenup user with a home directory of /home/zenup
 +
** The zenup utility is installed under /opt/zenup/ under the bin directory so any zenup command run as the zenoss user needs to be:
 +
*** /opt/zenup/bin/zenup <parameter>
 +
 +
* rpm commands all have the --nodeps parameter which I feel is dangerous.  Omitting this shows what will be broken.  In my case, it was only the installed Zenoss so went ahead with the --nodeps override
 +
** Note that I had postfix installed which ended up broken but before the second upgrade I did, I found that postfix was already broken before starting!
 +
 +
* On checking for installed java, I had jre-1.6.0_31-fcs.x86_64    (which I assume is not correct?? so I removed it)
 +
* Accessing both the Java code and MySQL requires an Oracle login id
 +
 +
 +
[[Category:Deployment]]

Revision as of 18:17, 9 August 2013

Upgrading to Zenoss 4.2.4

I found the instructions for performing an upgrade to 4.2.4 were rather diffuse.

There are some comments on the wiki page here - Install Zenoss

The main instructions are in the installation guide which you can get which is referenced on the above page - Zenoss Core 4 Installation Guide

These instructions say you need to install the new utility called ZenUp (which I believe is still beta code at August 9th 2013). It references the Zenoss Service Dynamics ZenUp Installation and Administration manual (and this is not a hyperlink) and obviously is less than appropriate for Core users; however, there is a good ZenUp reference here on the wiki at ZenUp.

I started from a community script installation of Zenoss 4.2.3 on CentOs 6.3. Start from Chapter 5 of the installation Guide. These are my comments / updates on those instructions.

  • You should definitely have taken a Zenoss backup before you get to upgrading but..... there is a bug with 4.2.3 that prevents zenbackup from running cleanly. The fix (as the zenoss user) is:
    • mysql -u root
    • GRANT SELECT ON mysql.proc to zenoss;
  • additional notes to the ZenUp wiki item:
    • Installing ZenUp creates a zenup user with a home directory of /home/zenup
    • The zenup utility is installed under /opt/zenup/ under the bin directory so any zenup command run as the zenoss user needs to be:
      • /opt/zenup/bin/zenup <parameter>
  • rpm commands all have the --nodeps parameter which I feel is dangerous. Omitting this shows what will be broken. In my case, it was only the installed Zenoss so went ahead with the --nodeps override
    • Note that I had postfix installed which ended up broken but before the second upgrade I did, I found that postfix was already broken before starting!
  • On checking for installed java, I had jre-1.6.0_31-fcs.x86_64 (which I assume is not correct?? so I removed it)
  • Accessing both the Java code and MySQL requires an Oracle login id