Hi,

Ronny said that you are in 0.6.3 version of Shinken.
You should definitely try to "pull" the latest version.
Jean has fixed some bugs about LiveStatus this week.
I used to get some irrelevant configuration with Livestatus (duplicate 
number of hosts/services for example).
Now with the lastest version, everything seems fine.

Regards

Olivier

Le 25/05/2011 16:38, Markus Elger a écrit :
> Hi @all,
>
> we've tested our configuration with shinken the last days and we found
> some bugs or at least nice to have features. ;)
>
>
> A very very short description of our configuration:
>
> - a shinken master
> - some satellites with scheduler and poller
>
>
> 1
> When I add the module Status-Dat to my broker (on the master, with a
> single broker) and restart shinken, the status.dat is created, but not
> filled with data (should be updated every 15 seconds). It seems that the
> module simple-log has problems with archiving old logs (directory
> 'archives' not found). After I created the directory archives, deleted
> status.dat and objects.cache I restarted shinken and everything worked.
> I think it would be nice if the simple-log wouldn't block the other
> modules from running?
>
> This is the error the broker wrote to his log:
>
> 2011-05-25 00:00:11,325 [1306274411] [broker-all] We are archiving the
> old log file
>
> 2011-05-25 00:00:11,326 [1306274411] [broker-all] Moving the old log
> file from nagios.log to archives/nagios-05-24-2011-00.log
>
> 2011-05-25 00:00:11,326 [1306274411] [broker-all] Error : the instance
> Simple-log raised an exception [Errno 2] No such file or directory:
> u'archives/nagios-05-24-2011-00.log', I remove it!
>
> 2011-05-25 00:00:11,327 [1306274411] [broker-all] Back trace of this
> remove : Traceback (most recent call last):
>    File "/usr/lib/python2.5/site-packages/shinken/modulesmanager.py",
> line 124, in try_instance_init
>      inst.init()
>    File
> "/usr/lib/python2.5/site-packages/shinken/modules/simplelog_broker.py",
> line 143, in init
>      moved = self.check_and_do_archive(first_pass=True)
>    File
> "/usr/lib/python2.5/site-packages/shinken/modules/simplelog_broker.py",
> line 115, in check_and_do_archive
>      shutil.move(self.path, file_archive_path)
>    File "/usr/lib/python2.5/shutil.py", line 199, in move
>      copy2(src,dst)
>    File "/usr/lib/python2.5/shutil.py", line 91, in copy2
>      copyfile(src, dst)
>    File "/usr/lib/python2.5/shutil.py", line 47, in copyfile
>      fdst = open(dst, 'wb')
> IOError: [Errno 2] No such file or directory:
> u'archives/nagios-05-24-2011-00.log'
>
>
> 2
> I have some hosts with 'parents' which are not in the same realm. During
> the configcheck the following error was thrown -->  Error : the realm
> configuration of your hosts is not good because there a more than one
> realm in one pack (host relations).
> But at the end the configcheck says that everything looks good (Things
> look okay - No serious problems were detected during the pre-flight
> check). But Shinken doesn't check and process the Host.
> It would be nice, if such an Error could be mentioned at the end of the
> configcheck. So I have to search the whole checkconfig output, because
> there 'maybe' is a mistake which is not mentioned in the summary at the
> end.
>
>
> 3
> When I start shinken, the arbiter splits the configuration and send it
> to the schedulers. They begin to work (I watched this in the logs). But
> in Thruk the number of hosts and services is changing repeatedly in the
> first minutes. The number is increasing and decreasing in the size of
> the host/service number of random realms. After a few minutes the
> numbers are correct.
>
> For example:
> I have 4 realms with 10 Hosts each. Then it could be that thruk says
> there are 20 hosts, then there are 10 hosts, then 20, then 30 ....and so
> on....
>
> I think the Arbiter/Broker should know the whole number of hosts and
> services before the Arbiter splits them (that means from the beginning
> and not some minutes later)? So that the correct number can be send out
> immediately via Livestatus at the start of shinken. Because now I was
> sitting in front of Thruk and waited untill the correct number of hosts
> showed up. This is important, because together with my bug report number
> 2 I have to make sure that shinken is checking all hosts and services.
>
>
> 4
> When I create a realm and assign a scheduler and poller to it, but
> don't make him a member of the default realm I get no error message.
> The scheduler and poller in the created realm get their configuration
> from the arbiter, but no broker will output data, because none is
> assigned to the new realm?
>
> Isn't it better if there is any warning/error message during
> configcheck?
>
>
> 5
> The configcheck incorrectly counts the number of hosts in a realm.
> Well...I think it's better when I show you an example, instead of
> describing it ;)
>
> Running pre-flight check on configuration data...
> Checking global parameters...
> Checking hosts...
>          Checked 574 hosts
> Checking hostgroups...
>          Checked 173 hostgroups
> Checking contacts...
>          Checked 14 contacts
> Checking contactgroups...
>          Checked 4 contactgroups
> Checking notificationways...
>          Checked 14 notificationways
> Checking escalations...
>          Checked 0 escalations
> Checking services...
>          Checked 7579 services
> Checking servicegroups...
>          Checked 24 servicegroups
> Checking timeperiods...
>          Checked 5 timeperiods
> Checking commands...
>          Checked 207 commands
> Checking servicedependencies...
>          Checked 0 servicedependencies
> Checking hostdependencies...
>          Checked 0 hostdependencies
> Checking arbiterlinks...
>          Checked 1 arbiterlinks
> Checking schedulerlinks...
>          Checked 11 schedulerlinks
> Checking reactionners...
>          Checked 1 reactionners
> Checking pollers...
>          Checked 11 pollers
> Checking brokers...
>          Checked 1 brokers
> Checking receivers...
>          Checked 1 receivers
> Checking resultmodulations...
>          Checked 1 resultmodulations
> Checking discoveryrules...
>          Checked 0 discoveryrules
> Checking discoveryruns...
>          Checked 0 discoveryruns
> Cutting the hosts and services into parts
> Creating packs for realms
> Number of hosts in the realm All : 0
> Number of hosts in the realm test1 : 0
> Number of hosts in the realm test2 : 0
> Number of hosts in the realm test3 : 0
> Number of hosts in the realm test4 : 1
> Number of hosts in the realm test5 : 1
> Number of hosts in the realm test6 : 2
> Number of hosts in the realm test7 : 0
> Number of hosts in the realm test8 : 58
> Number of hosts in the realm test9 : 1
> Number of hosts in the realm test10 : 1
> Things look okay - No serious problems were detected during the
> pre-flight check
>
>
> You see i've got 574 hosts which are in realms. But where are they after
> 'Creating packs for realms'?  The realm test8 with it's 58 Hosts is the
> server with the realm, where the shinken master runs, and from where I
> run the configcheck (only on the master checkconfig counted correct).
> As I see the hosts are put to their realms correctly, because when I run
> shinken everything works fine. But it would be nice if this summary will
> be accurate, too ;)
>
>
> So, that's it for now. ;)
>
>
> Markus Elger
> Linux-Systemadministrator
>
> Unister GmbH
> Barfußgässchen 11 | 04109 Leipzig
>
> Telefon: +49 (0)341 49288 4537
> markus.el...@unister.de
> www.unister.de
>
> Vertretungsberechtigter Geschäftsführer: Thomas Wagner
> Amtsgericht Leipzig, HRB: 19056
>
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel


------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to