Install Zenoss

From Zenoss Wiki
This is the approved revision of this page, as well as being the most recent.
Jump to: navigation, search

Zenoss Core 5.0[edit]

Zenoss5 core 2.png
Zenoss Core 5.0, our latest stable version, is now available!

Installation instructions and download links can be found below.

Supported Operating Systems[edit]

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

Red-hat.png Red Hat Enterprise Linux 64-bit 7.x
Centos logo.png CentOS 64-bit 7.x
Ubuntu-logo.png Ubuntu Linux 12.04 thru 14.04


Manual Installation[edit]

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

Auto-deploy Installation[edit]

Zenoss5 core autodeploy script installation.gif
Community provides also auto-deploy script for Zenoss Core 5 / Resource Manager 5. Example of installation log and a few images of installation are also provided.
Please read Github README before use. The latest version of auto-deploy script for Zenoss Core 5 / Resource Manager 5 is available on:

Github logo.png
Supported OS: Red Hat 7 / CentOS 7 / Ubuntu 14

Virtual Appliance[edit]

Zenoss provides an .ova virtual appliance for 5.0. This appliance contains everything you need to get started testing Zenoss.

Bulbgraph.png Note: Zenoss recommends that the appliance be used for testing/lab only


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

  • INSTALLING all files other than the ova appliance are now in Apt/Yum/Docker repo's. To find the artifacts you need, please consult the Install Guide
  • INSTALLING adding an additional DNS server to /etc/issue/docker (Ubuntu) or /etc/sysconfig/docker (RHEL/CentOS)
  • INSTALLING enable serviced/docker services: systemctl enable serviced; systemctl enable docker
  • ZENPACK after installing or uninstalling a ZenPack first stop all running services (there should be 5) and then start Zenoss
  • 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
  • NTP WONT INSTALL ON 14.04 run apt-get dist-upgrade and reboot before trying to install ntp
  • INSTALLING user must be member of sudo group, if he needs access to Control Center: usermod -aG sudo $USER
  • 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 (

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

ZenPacks that Don't work Yet[edit]

All the Docs[edit]

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

Typical issues when starting the ova image[edit]

When you start the ova image for the first time there will be some remaining steps to be done until you can access to zenoss via your browser

No network configuration[edit]

The ova won't have any ip set on the first run, you will have to set it manually

vi /etc/sysconfig/network-scripts/ifcfg-eth0


vi /etc/sysconfig/network
No services running[edit]

Once you know that you've internet, you have to restart the serviced daemon so it can pull the docker images that contain the different services.

 systemctl stop serviced && systemctl start serviced

You should be able to see the system at https://server_ip

Control Center Templates[edit]

A Control Center Templates are a definitions of services, which can be installed/deployed into your Control Center. They can provide whole ecosystem of applications, which can be also fully integrated with your Zenoss 5 instance.

  • Zenoss Searcher - fancy, fully responsive web user interface with all available ZenPacks
  • Zabbix - agent monitoring system, which can be used for monitoring of your Zenoss
  • Elasticsearch cluster - base component of Elasticsearch/Logstash/Kibana log monitoring
  • Grafana 2 for Zenoss 5 - commercial template/Docker image for the best metric visualization and dashboards integrated with your Zenoss

Zenoss Core 4.2.5[edit]

Supported Operating Systems[edit]

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

  • Red-hat.png Red Hat Enterprise Linux 64-bit 6.x (recommended) or 5.x
  • Centos logo.png CentOS 64-bit 6.x (recommended) or 5.x

Community Supported Operating Systems[edit]

HOWTO, Filing Bugs[edit]

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, or in the forums. These scripts are not supported by Zenoss. To report bugs, or submit fixes please submit them on the Github project.

Manual Installation[edit]

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:

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

Auto-deploy Installation[edit]

Bulbgraph.png 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 -O auto.tar.gz
# tar xvf auto.tar.gz
# cd zenoss-core-autodeploy-*

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:

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

Bulbgraph.png 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,, 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.

Fix for upgrade to 4.2.5[edit]

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:

zenjmx.conf:#  zenoss., default: 
zenwinperf.conf:#  zenoss., default:
zodb_db_main.conf:    passwd
zodb_db_session.conf:    passwd

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

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[edit]

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[edit]

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

  • VMwareWorkstationLogo.png 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[edit]

Zenoss Core 4.2.5 source code is browseable at

Sources can be checked out with the following command:

$ svn co

Core 4 Videos[edit]

Legacy Zenoss[edit]

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