shinken 0.6 on gentoo

18 may 2011

copied from shinken-monitoring.org

gentoo linux logo (copied from commons.wikipedia.org)

motivation

recently i had problems with the deployment of an** experimental** ‘shinken’ [1], a monitoring tool, on gentoo. most of the installation was ‘straightforward’. but i had a problem with livestatus in combination to ‘thruk’ [2].

Note: i basically used the shinken guide [3] for fast and easy testing of shinken

  • gentoo linux in virtualbox
  • shinken 0.6
  • thruk-1.0.3 (using the perl webserver; NOT using apache2)

dependencies

this list contains packages which are not essentially (as the apache and mysql stuff) but it’s basically all packages i’ve installed to make it work, so just pick what you need:

> sys-apps/portage-2.1.9.25
app-emulation/emul-linux-x86-baselibs-20100915-r1
sys-kernel/gentoo-sources-2.6.36-r5
sys-kernel/genkernel-3.4.10.907
app-arch/xz-utils-4.999.9_beta
sys-kernel/gentoo-sources-2.6.36-r5
sys-boot/grub-0.97-r10
sys-kernel/genkernel-3.4.10.907
app-portage/eix-0.20.5
net-misc/dhcpcd-5.2.8
app-admin/eselect-vi-1.1.7-r1
sys-libs/gpm-1.20.6
app-admin/eselect-ctags-1.13
app-portage/eix-0.20.5
sys-apps/iproute2-2.6.35-r2
dev-util/ctags-5.7
app-editors/vim-core-7.3.50
app-editors/vim-7.3.50
app-vim/gentoo-syntax-20100215
dev-python/setuptools-0.6.15
dev-python/pyro-3.12
dev-python/pyro-4.3
app-admin/metalog-1
virtual/logger-0
net-libs/libpcap-1.1.1
net-analyzer/nmap-5.21-r1
app-editors/gentoo-editor-2
virtual/pam-0
net-mail/mailbase-1
mail-mta/ssmtp-2.62-r8
virtual/mta-0
app-admin/sudo-1.7.4_p5
dev-libs/oniguruma-5.9.2
dev-db/mysql-init-scripts-1.2
dev-libs/apr-1.4.4
app-admin/eselect-php-0.6.2
dev-libs/libmcrypt-2.5.8-r2
dev-util/pkgconfig-0.25-r2
sys-apps/ed-1.4
dev-perl/Net-Daemon-0.43
perl-core/Storable-2.20
perl-core/File-Spec-3.31
virtual/perl-Sys-Syslog-0.27
dev-libs/libpcre-8.12
dev-libs/apr-util-1.3.11
virtual/perl-Storable-2.20
virtual/perl-File-Spec-3.31
app-admin/apache-tools-2.2.17
dev-perl/PlRPC-0.202.0
www-servers/apache-2.2.17
dev-perl/DBI-1.615
dev-db/mysql-5.0.91
virtual/mysql-5.0
dev-perl/DBD-mysql-4.01.7
dev-lang/php-5.3.6
media-libs/gd-2.0.35-r1
dev-perl/GD-2.44
dev-perl/yaml-0.71
app-misc/screen-4.0.3-r4
dev-perl/JSON-2.27
perl-core/Compress-Raw-Zlib-2.024
app-arch/unzip-6.0-r1
app-vim/genutils-2.5
virtual/perl-MIME-Base64-3.08
dev-perl/URI-1.55
app-misc/beep-1.2.2-r1
dev-libs/eventlog-0.2.12
app-text/build-docbook-catalog-1.4
app-text/sgml-common-0.6.3-r5
dev-libs/libgpg-error-1.10
app-text/docbook-xsl-stylesheets-1.75.2
dev-libs/libgcrypt-1.4.6
dev-libs/libxslt-1.1.26-r1
app-text/docbook-xml-dtd-4.3-r1
dev-util/gtk-doc-am-1.16
dev-libs/glib-2.28.6
app-admin/syslog-ng-3.1.4
net-analyzer/nagios-plugins-1.4.14-r2
app-misc/realpath-1.15-r1
app-portage/gentoolkit-0.2.4.6.1-r1
dev-python/simplejson-2.1.3
dev-db/sqlite-3.7.5
dev-python/pysqlite-2.6.3

problem with livestatus

i’ve missed a line in the README of shinken and therefore the livestatus service on port 50000 was not enabled. but there was no ‘good’ error message mentioning what actually got wrong.

thruk reported (in the webinterface):

No Backend available

shinken reported (/var/lib/shinken/brokerd.log):

[broker-1] Warning : the module type livestatus for Livestatus was not found in modules!

But that was fixed after i installed:

  • dev-db/sqlite-3.7.5
  • dev-python/pysqlite-2.6.3

and restarted shinken.

debugging

look into:

  • /etc/shinken/ (config files)
  • /var/lib/shinken (log files)

optinally one can restart a single module of the shinken service with debugging:

/etc/init.d/shinken-broker -d restart

solution

article source