Install Zenoss

Zenoss Core 5.2

Zenoss Core 5.2, our latest version, is now available!

DOWNLOAD the Zenoss Core 5 Install and Configuration Kit!

Documentation

Note: Install guide, administration guide and other docs such as releases notes for minor versions can be found here.

Installation

The traditional way to install Zenoss is to follow our Zenoss Core 5.1 Installation Guide. The Installation Guide will guide you through the process of installing Zenoss Core 5.1 on a 64-bit version of Red Hat Enterprise Linux 7/CentOS 7. Note that all the files required by the Installation Guide are in Yum/Docker repo's, and no longer require manual download.

Supported Operating Systems

Zenoss Core 5.x runs natively on the following Linux-based operating systems:

Red Hat Enterprise Linux 64-bit 7.x

CentOS 64-bit 7.x

Errata

This is a section for community errata on the 5.0 install process

• INSTALLING all files are now in Yum/Docker repo's. To find the artifacts you need, please consult the Install Guide
• INSTALLING enable serviced/docker services: systemctl enable serviced; systemctl enable docker
• PERFDATA Performance data is retained for 90 days by default, to adjust this see pp110 of the Admin Guide
• UPGRADING Future updates/upgrades will assume base zenpacks are installed. Removing them may break the update/upgrade

RedHat/Centos

• INSTALLING user must be member of wheel group, if he needs access to Control Center: usermod -aG wheel $USER
• INSTALLING command for Install and start the Dnsmasq package is incomplete, execute command: yum install -y dnsmasq
• INSTALLING check if rpcbind is started before serviced start, if rpcbind is not started, then use workaround (https://jira.zenoss.com/browse/CC-903):

systemctl start rpcbind && echo "systemctl start rpcbind" >> /etc/rc.d/rc.local && chmod +x /etc/rc.d/rc.local

Zenoss Core 4.2.5

Supported Operating Systems

Zenoss Core 4.2.5 runs natively on the following Linux-based operating systems:

• Red Hat Enterprise Linux 64-bit 6.x (recommended) or 5.x

• CentOS 64-bit 6.x (recommended) or 5.x

Community Supported Operating Systems

• Ubuntu Linux 12.04 thru 14.04
• Debian Linux Debian 7

HOWTO, Filing Bugs

Unofficial support for Debian and Ubuntu can be found in Github (on Hydruid's blog. The link to Hydruid's Blog is dead! but here is the link to the Wayback Machine version from 25 June 2014.) For help please ask in #zenoss on irc.freenode.net, or in the forums. These scripts are not supported by Zenoss. To report bugs, or submit fixes please submit them on the Github project.

• Ubuntu and Debian Instructions

Manual Installation

The traditional way to install Zenoss is to follow our Zenoss Core 4 Installation Guide. The Installation Guide will guide you through the process of installing Zenoss Core 4.2 on a 64-bit version of Red Hat Enterprise Linux 5.x or 6.x, using RPMs that you download from SourceForge:

Download RPMs for Installation, from SourceForge:

• RHEL/CentOS 6 64-bit: Zenoss Core RPM (includes Core ZenPacks)

• RHEL/CentOS 5 64-bit: Zenoss Core RPM (includes Core ZenPacks)

Please see the Zenoss Core 4 Release Notes for relevant information related to manual installation.

Auto-deploy Installation

Note: Updated for 4.2.5
The simplest way to install Zenoss Core 4.2 on a newly-deployed RHEL/CentOS 64-bit 5/6 system is to use our auto-deploy script, which downloads all required files for you. To use the script, first set up a new server running one of our supported operating systems. Then, as root, run the following commands:

# wget https://github.com/zenoss/core-autodeploy/tarball/4.2.5 -O auto.tar.gz
# tar xvf auto.tar.gz
# cd zenoss-core-autodeploy-*

Note: This version of the auto-deploy script no longer works as the pre-requisite chain has changed. See below.

Now, you have the option of editing zenpack_actions.txt, which defines all ZenPacks that will be installed by default (all Core ZenPacks). If you would like to avoid installing certain ZenPacks, then remove the corresponding lines from this file and save it.

Now you are ready to install Zenoss Core 4.2.5:

# ./core-autodeploy.sh #do not use ''tee'' or similar, /opt/zenoss/log/install.log will be created by the script.

Note: In some cases your ZenPacks will fail to load after the initial install. If so, see AutoDeploy - ZenPack Operation Errors

As part of the install process, your Zenoss installation will be secured, and you will be asked if you would like to set a secure root password for MySQL. It is strongly recommended that you do so.

The auto-deploy script will automatically download and install all required dependencies, as well as Zenoss Core 4.2. After the script completes successfully, use your favorite Web browser and head to port 8080 of your new server (for example, http://127.0.0.1:8080), and then set the Zenoss administrator password and create your initial user account using the Web interface.

Next, you'll want to Add a Device to Zenoss.

If you encounter issues with the auto-deploy script, please report them on the Discussion page.

Note: Updated auto-deploy script for CentOS and Ubuntu.

Consult the forum article http://www.zenoss.org/forum/146626 for versions of the auto-deploy script updated in December 2016. Both CentOS and Ubuntu versions are provided by following the links to GitHub where the master branch is for CentOS and the ubuntu branch is for Ubuntu. Zenoss 4.2.5 is installed along with the zenup utility and the latest (as of December 2016) update, SUP 671.

Fix for upgrade to 4.2.5

If you used the 4.2.4 community script to install, it uses a security script to ensure passwords are changed from the default values. This can cause a problem when upgrading as you may find that the 4.2.5 RPM copies over the secure passwords set by the security script in some files. To fix this, simply copy the secure password to global.conf, and elsewhere as needed.

A list of the files/variables where this password is used is provided below:

global.conf:zodb-password
global.conf:amqppassword
global.conf:zep-password
global.conf:hubpassword
zenjmx.conf:#  zenoss., default: 
zenjmx.conf:#hubpassword
zenwinperf.conf:#  zenoss., default:
zenwinperf.conf:#hubpassword
zodb_db_main.conf:    passwd
zodb_db_session.conf:    passwd

Fix for upgrade to 4.2.5 zenhub username/password combination is incorrect

After upgrading to 4.2.5, and following the steps above, and you still get "CRITICAL zen.pbclientfactory: zenhub username/password combination is incorrect!" when trying to model a device.

As Zenoss user:

cat /opt/zenoss/etc/global.conf | grep 'hubpassword' hubpassword yourrandompasswordhash

edit /opt/zenoss/etc/hubpasswd change admin:password to admin:yourrandompasswordhash

Restart Zenoss zenoss restart

Fix for Sticking JDBC Connections in 4.2 SP1

Getting these error messages?

org.springframework.transaction.TransactionSystemException: Could not roll back JDBC transaction; nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.Connection was implicitly closed by the driver.

Run the following as the zenoss user, or upgrade to 4.2.5:

$ zeneventserver-config -u zep.jdbc.pool.test_on_borrow=true
$ zeneventserver restart

Zenoss Virtual Machine

Alternatively, a pre-built Zenoss virtual machine image can be used to evaluate Zenoss:

• Zenoss 4.2.5 VMWare virtual machine image
  • VMWare Workstation for Microsoft Windows or Linux
  • VMWare Player for Microsoft Windows or Linux (free)
  • VMWare Fusion for Macintosh
  • VMware ESXi
    • Note: requires conversion using vCenter Converter Standalone, but first you need to edit the ".vmx" file :
      

scsi0:0.filename = "zenoss_core-4.2.5-2108-x86_64.vmdk"

fileSearchPath = "."

Source Code

Zenoss Core 4.2.5 source code is browseable at http://dev.zenoss.org/trac/browser/tags/zenoss-4.2.5.

Sources can be checked out with the following command:

$ svn co http://dev.zenoss.org/svn/tags/zenoss-4.2.5

Legacy Zenoss

Looking for an earlier version of Zenoss? See our Legacy Zenoss page.

Supported Zenoss versions

Visit End of Maintenance Dates page to see, which Zenoss version is still supported.