zenoss-4 installation steps on linux server

zenoss-4 installation steps on linux server

Here is getting Zenoss 4 up and running on  CentOS 6 server. This guide was originally tested on a freshly patched CentOS 6.3 on August 12, 2012. Zenoss 4.2 was the current version of Zenoss.

two types of installation.
1.Auto Deploy

There is a nice auto install script available now - it is recommended you use this method on a new install. Example is for Zenoss 4.2.4 - always check the Zenoss site for new versions before starting.  


# wget --no-check-certificate https://github.com/zenoss/core-autodeploy/tarball/4.2.4 -O auto.tar.gz
# tar xvf auto.tar.gz
# cd zenoss-core-autodeploy-*
# ./core-autodeploy.sh
 
Navigate to your server using a web browser:
http://server-ip:8080

2.Manual Way
Install EPEL repos. 
rpm -ivh http://fedora.mirror.nexicom.net/epel/6/i386/epel-release-6-8.noarch.rpm
yum check-update
Disable SELinux (or configure it properly)
Disable iptables (or configure it - see Firewall Ports)

Procedure

1. Setup /home/zenoss directory. 
useradd -m -d /home/zenoss -c "Zenoss User" zenoss 
chown zenoss:zenoss /home/zenoss
2. Remove conflicting packages 
rpm -qa | grep -i matahari
rpm -qa | grep -i qpid
rpm -e --nodeps <package>
3. Remove Old Mysql - if any: 
service mysql stop
rpm -qa | grep -i mysql 
rpm -e --nodeps <package>
4. Install / Update prerequisites:

Oracle Java → 1.6 Update 31 or later. 1.7 is NOT supported. The one in yum is 1.5.x. DO NOT use this version. Get 1.6. 
wget http://javadl.sun.com/webapps/download/AutoDL?BundleId=65508
chmod +x jre-6u33-linux.x64-rpm.bin*
./jre-6u33-linux.x64-rpm.bin
Test with: 
java -version
 java version "1.6.0_33"
 Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
 Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
RRDtool → 1.4.7 or later. 
wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
yum -y --nogpgcheck localinstall rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
vi /etc/yum.repos.d/rpmforge.repo and set enabled to 0. 
yum -y --enablerepo=rpmforge-extras install rrdtool-1.4.7
MySQL Community Server → 5.5.25 or later. Go to: http://dev.mysql.com/downloads/mysql → Select Oracle & Red Hat Linux 6
Download the following: 
MySQL Client Utilities (currently MySQL-client-5.5.25a-1.el6.x86_64.rpm)
MySQL Server (currently MySQL-server-5.5.25a-1.el6.x86_64.rpm)
MySQL Shared (currently MySQL-shared-5.5.25a-1.el6.x86_64.rpm)
SCP them to your server. 
yum -y --nogpgcheck localinstall MySQL*
DO NOT set mysql password.
Add the following to /etc/my.cnf (create if not already existing) 
[mysqld]
max_allowed_packet=16M
innodb_buffer_pool_size=256M
innodb_additional_mem_pool_size=20M
Start up MySQL: 
service mysql start
chkconfig --add mysql
chkconfig --level 2345 mysql on
If you see the following message when you start mysql:
A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER ! You will find that password in '/root/.mysql_secret'.
Then you will need to check the /root/.mysql_secret file for the current password. This appears to be fairly new behaviour (MySQL-server.x86_64 0:5.6.11-1.el6 )


Configure blank root password for the Zenoss installer (add the -p option to be prompted for password if you find that a password was generated for you during first mysql start): 
mysqladmin -u root password ''
mysqladmin -u root -h localhost password ''
RabbitMQ → 2.8.4 or later. 
wget http://www.rabbitmq.com/releases/rabbitmq-server/v2.8.4/rabbitmq-server-2.8.4-1.noarch.rpm
yum -y --nogpgcheck --enablerepo=epel localinstall rabbitmq-server-2.8.4-1.noarch.rpm
service rabbitmq-server start
chkconfig rabbitmq-server on
Nagios Plugins → 1.4.15 or later. 
yum --enablerepo=epel install nagios-plugins
Erlang → (was installed during rabbitmq install if you didnt notice)

6. Download the latest version of ZenOSS to your server. Current in example is 4.2. 
wget http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.0/zenoss-4.2.0.el6.x86_64.rpm/download
yum -y --enablerepo=epel --nogpgcheck localinstall zenoss-4.2.0.el6.x86_64.rpm
7. Fire up the last few services: 
service memcached start
chkconfig memcached on
service snmpd start
chkconfig snmpd on
8. Start up Zenoss - watch for errors or complaints. 
service zenoss start
9. Hit the Zenoss WebGUI at <serverip>:8080 and finish walking through the wizard to complete the install.
10. Install Zenpacks: 
wget http://sourceforge.net/projects/zenoss/files/zenpacks-4.2/zenpacks-4.2.0/zenoss-core-zenpacks-4.2.0.el6.x86_64.rpm
yum -y --nogpgcheck localinstall zenoss-core-zenpacks-4.2.0.el6.x86_64.rpm
11. Next fine tune your Zenoss installation. See Performance Tuning section.

Errors

Symlinking /usr to /local/usr or something of that nature breaks zenoss startup script.
service zenoss start
env: /etc/init.d/zenoss: No such file or directory
No skip to dashboard button off install.
Rebooted server. Fixed it - there were no errors during install when this happened.

Comments

Post a Comment

Popular posts from this blog

Understanding How ZFS Calculates Used Space

This document explains how ZFS calculates the amount of used space within a zpool and provides examples of how various ZFS features affect that calculation. DETAILS A ZFS storage pool is a logical collection of devices that provide space for datasets such as filesystems, snapshots and volumes. A zfs pool can be used as a filesystem, i.e. such as mounting/unmounting; to take snapshots that provides read-only (clones are writable copies of snapshots) copies of the filesystem taken in the past; to create volumes that can be accessed as a raw and a block device and for setting properties on datasets. Interaction of all these datasets and associated properties such as quotas, reservations, compression and deduplication (Solaris 11 only) play a role in how ZFS calculates space usage. Neither the du nor df command have been updated to account for ZFS file system space usage. When calculating zfs space usage, always use the following command. # zfs list -r -o space <pool_name...
Read more

How To Verify Remote System Controller (RSC) is Configured and Current on Sun Fire[TM] 280R/V480/V490/V880/V890 servers

Steps to Follow: How To Verify Remote System Controller(RSC) is Configured and Current 1.Check to see if the RSC software is already installed. # /usr/bin/pkginfo | grep SUNWrsc 2.If the software is installed the command should output the package name and info.   The version of the package installed in Solaris should match the version of firmware installed on the card.   `rscadm version` in Solaris will display the firmware version. 3.If the software is not installed the packages can be found on the supplemental CD that came with the Solaris Operating Environment. If you do not have the CD the software can be downloaded from MOS: RSC 2.2.2 is supported with Solaris 10, but you need to get this from a supplemental CD (for Solaris 9, since there is no supplemental CD for S10). The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are...
Read more

Restart autosys agent

#/etc/init.d/uajm_agent stop CA-UAJM Agent stopped. #/etc/init.d/uajm_agent start CA-UAJM Agent started. Follow the below workaround if the autosys agent does not start. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1.Run the command to check the status of both process, auto_remote and csampmuxf # ps -ef|grep 'auto'     root 14712     1  0   Aug 27 ?        2:42 auto_remote     root 27652     1  0 13:00:22 ?        0:00 auto_remote     root 27782     1  0 13:00:40 ?        0:00 auto_remote     root 29066 24480  0 13:01:07 pts/7    0:00 grep auto 2.There should be two entries for /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux status . If you see one entry then stop agent and check the autore...
Read more