Zenoss Core 4.2.5
Zenoss Core 4.2.5, our latest stable version, is now available! Installation instructions and download links can be found below.
Supported Operating Systems
Zenoss Core 4.2.5 runs natively on the following Linux-based operating systems:
- CentOS 64-bit 6.x (recommended) or 5.x
Community Supported Operating Systems
HOWTO, Filing Bugs
Unofficial support for Debian and Ubuntu can be found on Hydruid's blog. 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.
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.
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 --no-check-certificate https://github.com/zenoss/core-autodeploy/tarball/4.2.5 -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:
# ./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.
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:
- VMWare virtual machine image
- VMWare Workstation for Microsoft Windows or Linux
- VMWare Player for Microsoft Windows or Linux (free)
- VMWare Fusion for Macintosh
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
Core 4 Videos
Looking for an earlier version of Zenoss? See our Legacy Zenoss page.