Results 1 to 8 of 8

Thread: skonf discovery and shinken restart issue

  1. #1
    Junior Member
    Join Date
    Feb 2013
    Posts
    4

    skonf discovery and shinken restart issue

    Hi
    I am new to shinken and related components, but very familiar with Nagios kind of monitoring.

    I have successfully installed and configured Shinken + MongoDB on a Raspberry Pi (after some fights...) ... and I have modified the cfg files to use MongoDB when necessary.

    So now, I want to use Skonf to discover some hosts. Skonf is displaying some hosts, but when I restart shinken, the config check fails:

    Code:
    $ sudo /etc/init.d/shinken restart
    Restarting scheduler
    . ok 
    Restarting poller
    . ok 
    Restarting reactionner
    . ok 
    Restarting broker
    . ok 
    Restarting receiver
    . ok 
    Restarting arbiter
    Doing config check
    [warn] full result is in /tmp/shinken_checkconfig_result ... (warning).
    [FAIL] ConfigCheck failed: Configuration is incorrect, sorry, I bail out ... failed!
     failed!
    Restarting skonf
    . ok
    The log file contains the following information:
    Code:
    $ sudo cat /tmp/shinken_checkconfig_result
    [1359720468] Info :  Shinken 1.2.3
    [1359720468] Info :  Copyright (c) 2009-2011:
    [1359720468] Info :  Gabes Jean (naparuba@gmail.com)
    [1359720468] Info :  Gerhard Lausser, Gerhard.Lausser@consol.de
    [1359720468] Info :  Gregory Starck, g.starck@gmail.com
    [1359720468] Info :  Hartmut Goebel, h.goebel@goebel-consult.de
    [1359720468] Info :  License: AGPL
    [1359720468] Info :  Loading configuration
    ....
    [1359720478] Info :  I correctly loaded the modules: [PickleRetentionArbiter,Mongodb,NamedPipe-Autogenerated]
    ...
    [1359720487] Info :  Running pre-flight check on configuration data...
    [1359720487] Info :  Checking global parameters...
    [1359720487] Info :  Checking hosts...
    [1359720487] Error :  [host::192.168.1.29] max_check_attempts property not set
    [1359720487] Warning : The host 192.168.1.29 has no contacts nor contact_groups in (mongodb:mongodb://localhost/?safe=true:shinken)
    [1359720487] Error :  [items] In 192.168.1.29 is incorrect ; from mongodb:mongodb://localhost/?safe=true:shinken
    [1359720487] Error :  [host::192.168.1.2] max_check_attempts property not set
    ...
    [1359720488] Debug :  Trying to open the distribution file pack_distribution.dat
    [1359720488] Info :  Saving the distribution file pack_distribution.dat
    [1359720488] Info :  Number of hosts in all the realm 4
    [1359720488] Info :  Number of hosts 4
    [1359720488] Error :  Configuration is incorrect, sorry, I bail out
    Configuration is incorrect, sorry, I bail out
    I get the same errors for all the discovered hosts.

    When I try to go back in skonf to edit and save the value of the property, it does not work (the Apply button has no effect)
    Looking deeper with google inspect displays:

    Request URL:http://192.168.1.198:7766/gotfirstda...1359723150060=
    Request Method:GET
    Status Code:404 Not Found
    Request Headersview source

    How can this be fixed ??? :

    Thanks

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

    Re: skonf discovery and shinken restart issue

    Seems that this host was added without a default template (generic-host). Can you look in skonf if the "use" parameter is void or not?

    For the gotfirstdata call, you can forget it, it's not use and will be delete in the code
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3
    Junior Member
    Join Date
    Feb 2013
    Posts
    4

    Re: skonf discovery and shinken restart issue

    [quote author=naparuba link=topic=758.msg4194#msg4194 date=1359726527]
    Seems that this host was added without a default template (generic-host). Can you look in skonf if the "use" parameter is void or not?

    For the gotfirstdata call, you can forget it, it's not use and will be delete in the code
    [/quote]

    No problem doing that if you tell me how to check that ...

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

    Re: skonf discovery and shinken restart issue

    In skonf, go in your host configuration and look for the use parameter
    No direct support by personal message. Please open a thread so everyone can see the solution

  5. #5
    Junior Member
    Join Date
    Feb 2013
    Posts
    4

    Re: skonf discovery and shinken restart issue

    Well, when I discover my server, the 'tag' discovered are 'mysql' and 'generic-host'.
    When I validate this host, it appears in the skonf 'Hosts' panel, but without any tags. If I click on the host, all the parameters are empty except the 'hostname' and 'display name' parameter.
    I hope it answers your question since I do not find a file 192.168.1.29.cfg file in my filesystem.

    So I think the issue is that some discovery information are not saved correctly since they cannot be retrieved when I want to edit an host.

    How can this be fixed?

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

    Re: skonf discovery and shinken restart issue

    You can add manually the tags to the host, but I don't understand why they are lost when the discovery saved them.
    No direct support by personal message. Please open a thread so everyone can see the solution

  7. #7
    Junior Member
    Join Date
    Feb 2013
    Posts
    4

    Re: skonf discovery and shinken restart issue

    [quote author=naparuba link=topic=758.msg4203#msg4203 date=1359732391]
    You can add manually the tags to the host, but I don't understand why they are lost when the discovery saved them.
    [/quote]

    It is not possible since when I edit the host object in skonf and that I re-add the tags, the validate button does not save the result.
    Any idea?

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

    Re: skonf discovery and shinken restart issue

    Look at skonf debug messages about this last problem.
    No direct support by personal message. Please open a thread so everyone can see the solution

Posting Permissions

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