Skip to main content

Error when installing Zenoss in Centos 6 Docker image

This happens when using auto-deploy installation (hint).

# ./core-autodeploy.sh

The error happens in https://gist.github.com/fortran01/e6eb87c87fa8bb7aa3eb/ebdcce749b366c6cf97346f0411e91dd114a61d4#file-zenoss-core-autodeploy-ec817e6_core-autodeploy-sh-L261-L265 when the zenoss service is started.

Zenoss not initialized.  Performing first-boot initialization...
Fresh install pre steps
Checking RRDtool version >= 1.4.7: [FAIL] Missing.
Error: rrdtool is not in the search path. Please confirm that RRDtool (version >= 1.4.7) is installed.

It can be verified that rrdtool is already installed.

# rrdtool --version
RRDtool 1.4.7  Copyright 1997-2012 by Tobias Oetiker 
               Compiled Apr  5 2012 17:36:08

The routine that checks for rrdtool is in /opt/zenoss/bin/install-functions.sh. Look for confirm_rrd(). It uses the command `which` that is not installed by default in the Centos 6 docker image.

# yum install which -y
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirrors.vinahost.vn
 * extras: mirror.vietoss.com
 * updates: mirror.vietoss.com
Resolving Dependencies
--> Running transaction check
---> Package which.x86_64 0:2.19-6.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package          Arch              Version               Repository       Size
================================================================================
Installing:
 which            x86_64            2.19-6.el6            base             38 k

Transaction Summary
================================================================================
Install       1 Package(s)

Total download size: 38 k
Installed size: 71 k
Downloading Packages:
which-2.19-6.el6.x86_64.rpm                              |  38 kB     00:01     
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : which-2.19-6.el6.x86_64                                      1/1 
install-info: No such file or directory for /usr/share/info/which.info.gz
  Verifying  : which-2.19-6.el6.x86_64                                      1/1 

Installed:
  which.x86_64 0:2.19-6.el6                                                     

Complete!

It should now work.

# for service in memcached snmpd zenoss; do /sbin/chkconfig $service on; /sbin/service $service start; done
Starting memcached: 
Starting snmpd: 
Zenoss not initialized.  Performing first-boot initialization...
Fresh install pre steps
Checking RRDtool version >= 1.4.7: [ OK ] 1.4.7


Comments

Post a Comment

Popular posts from this blog

Resetting admin password in IBM System p5 510 Express ASMI

These are the steps in resetting the admin password: 0. Re-route stored static in your body via an ESD wrist strap to a metallic element. 1. Look for the 2 toggle switches and service processor batt. The batt should be in front of the Power Supply 1 and Power Supply 2 (codes: E1 and E2, see Rear Location Codes on the cover plate). The "very tiny" toggle switches should be in the area of P1-C14 slot. I forgot the exact sequence but it should be a combination of the ff. step (2): 2. Remove the battery, toggle the switches to the opposite direction. Allows some time for the caps to discharge. 3. Move back the toggle switches and put back the batt in its place. 4. Assign your PC to Class C subnet (i.e. masked 255.255.255.0 ): IPaddr: 192.168.2.x for HMC1 or IPaddr: 192.168.3.x for HMC2 5. Ping HMC1 or HMC2. Access the web interface using the default address: http://192.168.2.147 (for HMC1) or http://192.168.3.147 (for HMC2) Note: Sometimes you have to force the https protocol:
1 comment
Read more

Zenoss: monitor free VMWare ESXi version

We confirmed that the free ESXi version does not allow SNMP gets, only traps. The original script was taken from here: http://communities.vmware.com/docs/DOC-7170 Modified script: http://mirakulo.com/pub/esxi/check_esx_wbmem.py We added Fan and power supply, hinted from this page: http://www.stephenjc.com/2009/01/whatsup-vmware-esxi-monitor-these.html Use this guide to add the Data source: http://www.zenoss.com/community/docs/howtos/create-modify-nagios-templates Added as template under: /Devices /Server /VMWare /ESXi /Templates /esxi-monitor /check_esx_wbmem Name: check_esx_wbmem Source Type: Command Enable true Use SSH false Component: blank Event class: /VMWare/ESXi Severity: Error Cycle time: 60 Parser: auto Command template: /usr/local/zenoss/python/bin/python /opt/zenoss/libexec/check_esx_wbmem.py https://${dev/manageIp}:5989 root passwd To bind this template to ESXi nodes, go to the device: Example: /Devices /Server /VMWare /ESXi /esxi-01.prod.corp.org then to its temp
6 comments
Read more

ld: unrecognized option '--hash-style=both'

gcc -Wl,-Map=contiki.map,-export-dynamic testv6.co obj_linux-native/socketdev_listener.o \ contiki-linux-native.a -o testv6.linux-native /usr/local/bin/ld: unrecognized option '--hash-style=both' /usr/local/bin/ld: use the --help option for usage information collect2: ld returned 1 exit status If you look closely, the error is something related to the local gcc not using the host's linker (ld). $ which gcc /usr/bin/gcc $ which ld /usr/local/bin/ld For some reason, I messed my compiler path. To synchronized gcc to use the host's dynamic linker (i.e. /usr/bin/ld ), set the environment variable COMPILER_PATH to /usr/bin . $ export COMPILER_PATH=/usr/bin $ echo $COMPILER_PATH /usr/bin $ gcc -print-prog-name=ld /usr/bin/ld
9 comments
Read more