Hi, the download link in the 10-minute-start page is quite old. (0.5.5, theres a 0.6 meanwhile) Can you please download http://www.shinken-monitoring.org/pub/shinken-0.6.tar.gz instead? If you already got the newest version, make sure the livestatus broker (which interacts with thruk) is running.
ps ef | grep broker You should see 2 processes (1 is the main broker with the embedded logging module, 1 is the external broker process with the Livestatus module) You can also contact the livestatus broker with: printf "GET hosts\n" | nc 127.0.0.1 50000 Did you receive some output from this? Gerhard Von: Samuel Ruet [mailto:samuel.r...@albertville.com] Gesendet: Montag, 16. Mai 2011 16:15 An: shinken-devel@lists.sourceforge.net Betreff: [Shinken-devel] Thruk -> No Backend available Hello, I try to install shinken + Thruk by using the "shinken_10min_start" but I have 2 problems.. In the "Discover your network" section, when I run nmap I have no new hosts... details : sudo shinken-discovery -o /etc/shinken/discovery -r nmap -m "NMAPTARGETS=172.20-21.1-254.1-254 localhost" Using Pyro 3.12 Macros ['NMAPTARGETS=172.20-21.1-254.1-254 localhost'] Got macros [('NMAPTARGETS', '172.20-21.1-254.1-254 localhost')] Opening configuration file /etc/shinken/discovery.cfg Processing object config file '/etc/shinken/discovery_rules.cfg' Processing object config file '/etc/shinken/discovery_runs.cfg' Processing object config file '/etc/shinken/commands.cfg' Processing object config file '/etc/shinken/resource.cfg' Opening configuration file /etc/shinken/discovery.cfg Processing object config file '/etc/shinken/discovery_rules.cfg' Processing object config file '/etc/shinken/discovery_runs.cfg' Processing object config file '/etc/shinken/commands.cfg' Processing object config file '/etc/shinken/resource.cfg' Warning : there is no arbiter, I add one in localhost:7770 Warning : there is no scheduler, I add one in localhost:7768 Warning : there is no poller, I add one in localhost:7771 Warning : there is no reactionner, I add one in localhost:7769 Warning : there is no broker, I add one in localhost:7772 Notice : the is no defined realms, so I add a new one Default Notice : Tagging Default-Poller with realm Default Notice : Tagging Default-Broker with realm Default Notice : Tagging Default-Reactionner with realm Default Notice : Tagging Default-Scheduler with realm Default For realm Default Me Default-Scheduler is linked with realm Default Me Default-Broker is linked with realm Default Me Default-Reactionner is linked with realm Default Me Default-Poller is linked with realm Default I Default-Poller manage tags : ['None'] Running pre-flight check on configuration data... Checking global parameters... Checking hosts... Checked 0 hosts Checking hostgroups... Checked 0 hostgroups Checking contacts... Checked 0 contacts Checking contactgroups... Checked 0 contactgroups Checking notificationways... Checked 0 notificationways Checking escalations... Checked 0 escalations Checking services... Checked 0 services Checking servicegroups... Checked 0 servicegroups Checking timeperiods... Checked 0 timeperiods Checking commands... Checked 37 commands Checking servicedependencies... Checked 0 servicedependencies Checking hostdependencies... Checked 0 hostdependencies Checking arbiterlinks... Checked 1 arbiterlinks Checking schedulerlinks... Checked 1 schedulerlinks Checking reactionners... Checked 1 reactionners Checking pollers... Checked 1 pollers Checking brokers... Checked 1 brokers Checking receivers... Checked 0 receivers Checking resultmodulations... Checked 0 resultmodulations Checking discoveryrules... Checked 23 discoveryrules Checking discoveryruns... Checked 2 discoveryruns I'm launching nmap {'id': 0} Got Raw disco data and in the "First launch" section: - I have no /var/lib/shinken/shinken.log - the thruk web interface write "No Backend available" détails : [root@shinken Desktop]# /etc/init.d/shinken stop Stopping scheduler Stopping poller [ OK ] Stopping reactionner [ OK ] Stopping broker [ OK ] Stopping receiver [ OK ] Stopping arbiter [ OK ] [root@shinken Desktop]# /etc/init.d/shinken start Starting scheduler: Starting poller: [ OK ] Starting reactionner: [ OK ] Starting broker: [ OK ] Starting receiver: [ OK ] Starting arbiter: [ OK ] [root@shinken Desktop]# /etc/init.d/thruk start [ OK ] Starting thruk: thruk. [root@shinken Desktop]# You can connect to your server at http://shinken.domain.name:3000 [error] data source error: failed to connect at /opt/thruk/script/../local-lib/lib/perl5/Monitoring/Livestatus/Class/Base/Ta ble.pm line 189 [error] No Backend available [error] on page: http://172.20.4.1:3000/thruk/ Thank a lot for your help! Sam CentOS release 5.4 (Final) x86_64 Linux version 2.6.18-164.el5 perl-5.8.8-32.el5_5.2.x86_64 perl-5.8.8-32.el5_5.2.i386 Python 2.4.3 Pyro-3.12 multiprocessing-2.6.2.1 shinken-0.6 Thruk-1.0.3-x86_64-linux-thread-multi-5.8.8 ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
