Page 1 of 5 123 ... LastLast
Results 1 to 10 of 47

Thread: [RESOLVED] Error-No Backend available

  1. #1

    [RESOLVED] Error-No Backend available

    Hi there,

    I'im in education and i shall configure a shinken server for testing. I followed the 10 Minutes tutorial and there was no error. Now i startet the services and connected to the Web Interface and i get the following error:

    No Backend available
    None of the configured Backends could be reached, please have a look at the logfile for more information.

    I really have no clue why this is happening. i already checked the config files, and for me, they are all correct.


    Please help me


    Thanks

    Bye

  2. #2
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: Error-No Backend available

    Hi,

    Look at your broker.log file, something should be wrong with the LiveStatatus module (no sqlite or json lib maybe).
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3

    Re: Error-No Backend available

    I searched for the file, but i didnt find it. Where should this log file be?

    I nearly forgot to tell. I am using Red Hat Enterprise 5 installed in a VM (the Vm may not be importing, but just as an info).

  4. #4
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: Error-No Backend available

    It depend how you installed Shinken, but you can look in /var/lib/shinken.
    No direct support by personal message. Please open a thread so everyone can see the solution

  5. #5

    Re: Error-No Backend available

    Foudn it, strange that "find" didnt find it...


    Here it is:



    2011-09-26 10:08:13,366 [1317024493] Using the local log file 'brokerd.log'

    2011-09-26 10:08:13,409 [1317024493] Waiting for initial configuration

    2011-09-26 10:08:14,933 [1317024494] [broker-1] [broker-1] We have our schedulers : {0: {'broks': {}, 'last_connection': 0, 'name': u'scheduler-1', 'uri': u'PYROLOC://localhost:7768/Broks', 'instance_id': 0, 'running_id': 0, 'address': u'localhost', 'active': True, 'port': 7768}}

    2011-09-26 10:08:14,933 [1317024494] [broker-1] [broker-1] We have our arbiters : {0: {'broks': {}, 'last_connection': 0, 'name': u'Arbiter-Master', 'uri': u'PYROLOC://localhost:7770/Broks', 'instance_id': 0, 'running_id': 0, 'address': u'localhost', 'port': 7770}}

    2011-09-26 10:08:14,934 [1317024494] [broker-1] [broker-1] We have our pollers : {0: {'broks': {}, 'instance_id': 0, 'last_connection': 0, 'name': u'poller-1', 'poller_tags': ['None'], 'uri': u'PYROLOC://localhost:7771/Broks', 'passive': False, 'reactionner_tags': [], 'running_id': 0, 'address': u'localhost', 'active': True, 'port': 7771}}

    2011-09-26 10:08:14,934 [1317024494] [broker-1] [broker-1] We have our reactionners : {0: {'broks': {}, 'instance_id': 0, 'last_connection': 0, 'name': u'reactionner-1', 'poller_tags': [], 'uri': u'PYROLOC://localhost:7769/Broks', 'passive': False, 'reactionner_tags': ['None'], 'running_id': 0, 'address': u'localhost', 'active': True, 'port': 7769}}

    2011-09-26 10:08:14,934 [1317024494] [broker-1] [broker-1] We received modules [<shinken.objects.module.Module object at 0x2baa393461d0>, <shinken.objects.module.Module object at 0x2baa39346210>]

    2011-09-26 10:08:14,940 [1317024494] [broker-1] [broker-1] Connexion OK to the scheduler scheduler-1

    2011-09-26 10:08:14,949 [1317024494] [broker-1] [broker-1] Connexion OK to the poller poller-1

    2011-09-26 10:08:14,952 [1317024494] [broker-1] [broker-1] Connexion OK to the reactionner reactionner-1

    2011-09-26 10:08:14,954 [1317024494] [broker-1] Warning in importing module : No module named memcache

    2011-09-26 10:08:14,968 [1317024494] [broker-1] Warning in importing module : No module named redis

    2011-09-26 10:08:14,974 [1317024494] [broker-1] Warning in importing module : No module named simplejson

    2011-09-26 10:08:14,975 [1317024494] [broker-1] Warning in importing module : No module named MySQLdb

    2011-09-26 10:08:14,978 [1317024494] [broker-1] Warning in importing module : No module named MySQLdb

    2011-09-26 10:08:14,991 [1317024494] [broker-1] Warning in importing module : No module named simplejson

    2011-09-26 10:08:14,991 [1317024494] [broker-1] Warning : the module type livestatus for Livestatus was not found in modules!

    2011-09-26 10:08:14,992 [1317024494] [broker-1] Trying to init module : Simple-log

    2011-09-26 10:08:14,992 [1317024494] [broker-1] I open the log file nagios.log

    2011-09-26 10:08:14,993 [1317024494] [broker-1] I correctly loaded the modules : [Simple-log]



    I think your were right, but how do i fix it? Like i said i followed the 10 Minutes turorial and there didnt occur a problem.

    Thanks

  6. #6
    Administrator
    Join Date
    Jun 2011
    Posts
    216

    Re: Error-No Backend available

    Hi,

    The fisrt lines you put in bold are not important. I've quite the same too, I don't know where it comes from.

    For the Livestatus it's more strange. Can you copy/paste the part of the shinken-specific.cfg where you define it?

    By the way, what's your shinken version?

  7. #7

    Re: Error-No Backend available

    I am using the newest Version of Shinken, since i have just installed/downloaded it a few hours ago (Version 0.6.5 tarball).




    http://www.megaupload.com/?d=G7HEARRO




    There is my config File, but i didnt touched it. I just did this Minute guide:

    http://www.shinken-monitoring.org/wi...en_10min_start

  8. #8
    Administrator
    Join Date
    Jun 2011
    Posts
    216

    Re: Error-No Backend available

    I think you made a mistake uploading your file : I have only 60 lines on the file.

    Nevertheless, I check the default shinken-specific.cfg available in the source (GitHub) and the Livestatus module is loaded by default.

  9. #9
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: Error-No Backend available

    The LiveStatus need both modules :

    * python-sqlite
    * python-simplejson

    Regards,


    Jean
    No direct support by personal message. Please open a thread so everyone can see the solution

  10. #10

    Re: Error-No Backend available

    Thank you for your help.

    Indeed i copied just a part of the config, sorry. Now it should be the whole config. Like i said i didnt touched this file before, so is should be default one.

    http://www.megaupload.com/?d=2DEK687H


    Erik

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •