Unable to add more than 20 hosts !

[loops21]

Hi !

First, sorry for my bad english !

I've just installed Shinken (Shinken Framework, version: 3.0.0) in a Ubuntu 16.04 server 64. All good.

I need to add 27 hosts. There is a sample of my hosts configuration file :

define host{ use generic-host contact_groups admins host_name Name address X.X.X.X }

in the file the X.X.X.X is a real IP address !!!

I've created my 27 .cfg file ...

I add the 27 file in the /hosts/ folder and I restart shinken, there is no host in the web interface :/ So, I remove all host and i add only one. Next the restart, i can see my host. I continue host by host to find the problem.

When I add the host 21 and restart Shinken, all hosts disapear ... If I remove the host 21 and restart, i can see all hosts ...

OK, the host 21 is incorrect ? I can see anything wrong.

Well, I add the host 21 and i restart shinken ... all hosts disapears ! Now i remove an host ... the host 4 or 10 or 2 etc ... Now i restart shinken and i can see the host 21 ... i've only 20 hosts because i've removed another host ...

I dont understand ... I can see anything in the log ...

Have you any idea about this problem ?

Thank's a lot,

JC

[k0ste]

Shinken (core 3.0)

What is this?

[loops21]

I've modified ... an error typing ... :/

[k0ste]

No... what is Shinken 3.0 ?

[loops21]

the about splash screen give me :

About Shinken Web UI:

Web User Interface Version

Shinken Web UI, version: 2.4.2c Shinken Framework Version

Shinken Framework, version: 3.0.0 Copyright

[k0ste]

shinken-arbiter -v -c /etc/shinken/shinken.cfg, first lines.

or

shinken --version

[mohierf]

The WebUI displays 3.0.0 because ìt is the version reported by the Shinken you installed:

from shinken.bin import VERSION

I suppose that you installed from the git repository.

😉 I was not even aware that a version 3.0.0 existed...

[loops21]

Yes I've installed Shinken from Git. I used this tutorial : http://algorys.github.io/tuto/shinken-installation/

Any idea about my problem ?

[mohierf]

As far as I understood, the 21st host breaks the display of hosts in the WebUI, correct? But all your hosts are really monitored by Shinken or not ? Any errors in the log files ? Please post a pastebin with shinken-arbiter -v -c /etc/shinken/shinken.cfg

[loops21]

As far as I understood, the 21st host breaks the display of hosts in the WebUI, correct?

the Webgui works but display 0 hosts ... Exactly the same display if i delete all the .cfg files in the hosts directory ...

But all your hosts are really monitored by Shinken or not ?

Yes !

I've added the 21st host, restarted shinken and run the command :

shinken-arbiter -v -c /etc/shinken/shinken.cfg [1494007902] INFO: [Shinken] Shinken 3.0.0 [1494007902] INFO: [Shinken] Copyright (c) 2009-2014: [1494007902] INFO: [Shinken] Gabes Jean ([email protected]) [1494007902] INFO: [Shinken] Gerhard Lausser, [email protected] [1494007902] INFO: [Shinken] Gregory Starck, [email protected] [1494007902] INFO: [Shinken] Hartmut Goebel, [email protected] [1494007902] INFO: [Shinken] License: AGPL [1494007902] INFO: [Shinken] Loading configuration [1494007902] INFO: [Shinken] [config] opening '/etc/shinken/shinken.cfg' configuration file [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/reload-shinken.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_snmp_time.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_snmp_service.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_nrpe_args.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/detailled-host-by-email.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/restart-shinken.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/notify-service-by-email.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_ping.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_nrpe.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_dig.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/detailled-service-by-email.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/notify-host-by-email.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/notify-service-by-android-sms.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/notify-host-by-android-sms.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/configuration-check.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_host_alive.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_tcp.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/check_snmp_storage.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/notify-host-by-xmpp.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/commands/notify-service-by-xmpp.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/timeperiods/workhours.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/timeperiods/24x7.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/timeperiods/none.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/timeperiods/us-holidays.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/escalations/sample.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/dependencies/sample.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/templates/time_templates.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/templates/generic-contact.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/templates/generic-service.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/templates/generic-host.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/templates/srv-pnp.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/notificationways/email.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/notificationways/sms-android.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/notificationways/detailled-email.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/servicegroups/sample.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hostgroups/linux.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/contactgroups/admins.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/contactgroups/users.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/AS400.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Onduleur_Serveurs.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/localhost.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/nas01.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-P01-M.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-S01-I.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Juniper-S1.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Netinary.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Juniper-S3.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Juniper-S2.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-S01-M.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Juniper-Coeur.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-S02-I.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Juniper-Core-DR.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-S02-M.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-P02-M.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Stormshield.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-P01-I.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Onduleur_Bureaux.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/ESX-P02-I.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/hosts/Juniper-Core-Siege.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/services/services.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/contacts/piumib.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/contacts/lopezj.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/contacts/mazzonettl.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/contacts/guest.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/contacts/admin.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/packs/readme.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/packs/notification-smtp/notificationways.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/packs/notification-smtp/commands.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/modules/sample.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/modules/webui2.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/arbiters/arbiter-master.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/schedulers/scheduler-master.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/pollers/poller-master.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/reactionners/reactionner-android-sms.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/reactionners/reactionner-master.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/brokers/broker-master.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/receivers/receiver-master.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/realms/all.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/snmp.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/paths.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/smtp.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/active-directory.cfg' [1494007902] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/nmap.cfg' [1494007902] INFO: [Shinken] And arbiter is launched with the hostname:LNX22 from an arbiter point of view of addr:LNX22 [1494007902] INFO: [Shinken] I am the master Arbiter: arbiter-master [1494007902] INFO: [Shinken] My own modules: [1494007902] INFO: [Shinken] Modules directory: /var/lib/shinken/modules [1494007902] INFO: [Shinken] Modules directory: /var/lib/shinken/modules [1494007902] INFO: [Shinken] Correctly loaded dummy_arbiter as an old-new-style shinken module :| [1494007902] INFO: [Shinken] Correctly loaded dummy_broker_external as an old-new-style shinken module :| [1494007902] INFO: [Shinken] Correctly loaded dummy_broker as an old-new-style shinken module :| [1494007902] INFO: [Shinken] Correctly loaded dummy_poller as an old-new-style shinken module :| [1494007902] WARNING: [Shinken] [WebUI-auth-htpasswd] Can not import bcrypt password authentication. You should 'pip install passlib' if you intend to use it. [1494007902] WARNING: [Shinken] [WebUI] Can not import Alignak frontend library. If you intend to use Alignak backend authentication or objects, you should 'pip install alignak_backend_client' [1494007902] INFO: [Shinken] Correctly loaded webui2 as an old-new-style shinken module :| [1494007902] INFO: [Shinken] Correctly loaded dummy_scheduler as an old-new-style shinken module :| [1494007902] INFO: [Shinken] I correctly loaded the modules: [] [1494007902] INFO: [Shinken] All: (in/potential) (schedulers:1) (pollers:1/1) (reactionners:1/1) (brokers:1/1) (receivers:1/1) [1494007902] WARNING: [Shinken] The following parameter(s) are not currently managed. [1494007902] INFO: [Shinken] enable_predictive_service_dependency_checks [1494007902] INFO: [Shinken] host_perfdata_file_processing_interval [1494007902] INFO: [Shinken] use_embedded_perl_implicitly [1494007902] INFO: [Shinken] use_regexp_matching: If you go some host or service definition like prod*, it will surely failed from now, sorry. [1494007902] INFO: [Shinken] service_perfdata_file_processing_command [1494007902] INFO: [Shinken] use_true_regexp_matching [1494007902] INFO: [Shinken] enable_embedded_perl: It will surely never be managed, but it should not be useful with poller performances. [1494007902] INFO: [Shinken] enable_predictive_host_dependency_checks [1494007902] INFO: [Shinken] service_perfdata_file_processing_interval [1494007902] INFO: [Shinken] host_perfdata_file_processing_command [1494007902] INFO: [Shinken] passive_host_checks_are_soft [1494007902] INFO: [Shinken] date_format [1494007902] INFO: [Shinken] translate_passive_host_checks [1494007902] INFO: [Shinken] auto_rescheduling_interval [1494007902] INFO: [Shinken] soft_state_dependencies [1494007902] INFO: [Shinken] auto_reschedule_checks [1494007902] INFO: [Shinken] auto_rescheduling_window [1494007902] WARNING: [Shinken] Unmanaged configuration statement, do you really need it?Ask for it on the developer mailinglist https://lists.sourceforge.net/lists/listinfo/shinken-devel or submit a pull request on the Shinken github [1494007902] WARNING: [Shinken] The parameter status_update_interval is useless and can be removed from the configuration (Reason: This parameter is not longer take from the main file, but must be defined in the status_dat broker module instead. But Shinken will create you one if there are no present and use this parameter in it, so no worry.) [1494007902] WARNING: [Shinken] The parameter retained_contact_service_attribute_mask is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] WARNING: [Shinken] The parameter command_check_interval is useless and can be removed from the configuration (Reason: another value than look always the file is useless, so we fix it.) [1494007902] WARNING: [Shinken] The parameter retained_process_service_attribute_mask is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] WARNING: [Shinken] The parameter debug_verbosity is useless and can be removed from the configuration (Reason: This parameter is no longer useful in the Shinken architecture.) [1494007902] WARNING: [Shinken] The parameter max_check_result_file_age is useless and can be removed from the configuration (Reason: Shinken do not use flat file check resultfiles.) [1494007902] WARNING: [Shinken] The parameter sleep_time is useless and can be removed from the configuration (Reason: this deprecated option is useless in the shinken way of doing.) [1494007902] WARNING: [Shinken] The parameter bare_update_checks is useless and can be removed from the configuration (Reason: This parameter is no longer useful in the Shinken architecture.) [1494007902] WARNING: [Shinken] The parameter service_inter_check_delay_method is useless and can be removed from the configuration (Reason: This option is useless in the Shinken scheduling. The only way is the smart way.) [1494007902] WARNING: [Shinken] The parameter check_result_path is useless and can be removed from the configuration (Reason: Shinken use in memory returns, not check results on flat file.) [1494007902] WARNING: [Shinken] The parameter use_retained_program_state is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] WARNING: [Shinken] The parameter free_child_process_memory is useless and can be removed from the configuration (Reason: this option is automatic in Python processes) [1494007902] WARNING: [Shinken] The parameter check_for_updates is useless and can be removed from the configuration (Reason: network administrators will never allow such communication between server and the external world. Use your distribution packet manager to know if updates are available or go to the http://www.shinken-monitoring.org website instead.) [1494007902] WARNING: [Shinken] The parameter max_concurrent_checks is useless and can be removed from the configuration (Reason: Limiting the max concurrent checks is not helpful to got a good running monitoring server.) [1494007902] WARNING: [Shinken] The parameter use_large_installation_tweaks is useless and can be removed from the configuration (Reason: this option is deprecated because in shinken it is just an alias for enable_environment_macros=0) [1494007902] WARNING: [Shinken] The parameter admin_pager is useless and can be removed from the configuration (Reason: sorry, not yet implemented.) [1494007902] WARNING: [Shinken] The parameter retained_contact_host_attribute_mask is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] WARNING: [Shinken] The parameter max_check_result_reaper_time is useless and can be removed from the configuration (Reason: Shinken do not use reaper process.) [1494007902] WARNING: [Shinken] The parameter event_broker_options is useless and can be removed from the configuration (Reason: event broker are replaced by modules with a real configuration template.) [1494007902] WARNING: [Shinken] The parameter debug_level is useless and can be removed from the configuration (Reason: This parameter is no longer useful in the Shinken architecture.) [1494007902] WARNING: [Shinken] The parameter object_cache_file is useless and can be removed from the configuration (Reason: This parameter is not longer take from the main file, but must be defined in the status_dat broker module instead. But Shinken will create you one if there are no present and use this parameter in it, so no worry.) [1494007902] WARNING: [Shinken] The parameter retained_service_attribute_mask is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] WARNING: [Shinken] The parameter child_processes_fork_twice is useless and can be removed from the configuration (Reason: fork twice is not use.) [1494007902] WARNING: [Shinken] The parameter use_retained_scheduling_info is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] WARNING: [Shinken] The parameter debug_file is useless and can be removed from the configuration (Reason: This parameter is no longer useful in the Shinken architecture.) [1494007902] WARNING: [Shinken] The parameter temp_file is useless and can be removed from the configuration (Reason: Temporary files are not used in the shinken architecture. Skipping) [1494007902] WARNING: [Shinken] The parameter host_inter_check_delay_method is useless and can be removed from the configuration (Reason: This option is unused in the Shinken scheduling because distribution of the initial check is a random one.) [1494007902] WARNING: [Shinken] The parameter retained_process_host_attribute_mask is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] WARNING: [Shinken] The parameter service_interleave_factor is useless and can be removed from the configuration (Reason: This option is useless in the Shinken scheduling because it use a random distribution for initial checks.) [1494007902] WARNING: [Shinken] The parameter admin_email is useless and can be removed from the configuration (Reason: sorry, not yet implemented.) [1494007902] WARNING: [Shinken] The parameter retain_state_information is useless and can be removed from the configuration (Reason: sorry, retain state information will not be implemented because it is useless.) [1494007902] WARNING: [Shinken] The parameter external_command_buffer_slots is useless and can be removed from the configuration (Reason: We do not limit the external command slot.) [1494007902] WARNING: [Shinken] The parameter max_debug_file_size is useless and can be removed from the configuration (Reason: This parameter is no longer useful in the Shinken architecture.) [1494007902] WARNING: [Shinken] The parameter precached_object_file is useless and can be removed from the configuration (Reason: Shinken does not use precached_object_files. Skipping.) [1494007902] WARNING: [Shinken] The parameter check_result_reaper_frequency is useless and can be removed from the configuration (Reason: Shinken do not use reaper process.) [1494007902] WARNING: [Shinken] The parameter status_file is useless and can be removed from the configuration (Reason: This parameter is not longer take from the main file, but must be defined in the status_dat broker module instead. But Shinken will create you one if there are no present and use this parameter in it, so no worry.) [1494007902] WARNING: [Shinken] The parameter log_file is useless and can be removed from the configuration (Reason: This parameter is not longer take from the main file, but must be defined in the status_dat broker module instead. But Shinken will create you one if there are no present and use this parameter in it, so no worry.) [1494007902] WARNING: [Shinken] The parameter retained_host_attribute_mask is useless and can be removed from the configuration (Reason: We do not think such an option is interesting to manage.) [1494007902] INFO: [Shinken] Running pre-flight check on configuration data... [1494007902] INFO: [Shinken] Checking global parameters... [1494007902] INFO: [Shinken] Checking hosts... [1494007902] INFO: [Shinken] Checked 21 hosts [1494007902] INFO: [Shinken] Checking hostgroups... [1494007902] INFO: [Shinken] Checked 1 hostgroups [1494007902] INFO: [Shinken] Checking contacts... [1494007902] INFO: [Shinken] Checked 5 contacts [1494007902] INFO: [Shinken] Checking contactgroups... [1494007902] INFO: [Shinken] Checked 2 contactgroups [1494007902] INFO: [Shinken] Checking notificationways... [1494007902] INFO: [Shinken] Checked 4 notificationways [1494007902] INFO: [Shinken] Checking escalations... [1494007902] INFO: [Shinken] Checked 0 escalations [1494007902] INFO: [Shinken] Checking services... [1494007902] INFO: [Shinken] Checked 0 services [1494007902] INFO: [Shinken] Checking servicegroups... [1494007902] INFO: [Shinken] Checked 0 servicegroups [1494007902] INFO: [Shinken] Checking timeperiods... [1494007902] INFO: [Shinken] Checked 4 timeperiods [1494007902] INFO: [Shinken] Checking commands... [1494007902] INFO: [Shinken] Checked 25 commands [1494007902] INFO: [Shinken] Checking hostsextinfo... [1494007902] INFO: [Shinken] Checked 0 hostsextinfo [1494007902] INFO: [Shinken] Checking servicesextinfo... [1494007902] INFO: [Shinken] Checked 0 servicesextinfo [1494007902] INFO: [Shinken] Checking checkmodulations... [1494007902] INFO: [Shinken] Checked 0 checkmodulations [1494007902] INFO: [Shinken] Checking macromodulations... [1494007902] INFO: [Shinken] Checked 0 macromodulations [1494007902] INFO: [Shinken] Checking servicedependencies... [1494007902] INFO: [Shinken] Checked 0 servicedependencies [1494007902] INFO: [Shinken] Checking hostdependencies... [1494007902] INFO: [Shinken] Checked 0 hostdependencies [1494007902] INFO: [Shinken] Checking arbiters... [1494007902] INFO: [Shinken] Checked 1 arbiters [1494007902] INFO: [Shinken] Checking schedulers... [1494007902] INFO: [Shinken] Checked 1 schedulers [1494007902] INFO: [Shinken] Checking reactionners... [1494007902] INFO: [Shinken] Checked 1 reactionners [1494007902] INFO: [Shinken] Checking pollers... [1494007902] INFO: [Shinken] Checked 1 pollers [1494007902] INFO: [Shinken] Checking brokers... [1494007902] INFO: [Shinken] Checked 1 brokers [1494007902] INFO: [Shinken] Checking receivers... [1494007902] INFO: [Shinken] Checked 1 receivers [1494007902] INFO: [Shinken] Checking resultmodulations... [1494007902] INFO: [Shinken] Checked 0 resultmodulations [1494007902] INFO: [Shinken] Checking discoveryrules... [1494007902] INFO: [Shinken] Checked 0 discoveryrules [1494007902] INFO: [Shinken] Checking discoveryruns... [1494007902] INFO: [Shinken] Checked 0 discoveryruns [1494007902] INFO: [Shinken] Checking businessimpactmodulations... [1494007902] INFO: [Shinken] Checked 0 businessimpactmodulations [1494007902] INFO: [Shinken] Cutting the hosts and services into parts [1494007902] INFO: [Shinken] Creating packs for realms [1494007902] INFO: [Shinken] Number of hosts in the realm All: 21 (distributed in 21 linked packs) [1494007902] INFO: [Shinken] Total number of hosts : 21 [1494007902] INFO: [Shinken] Things look okay - No serious problems were detected during the pre-flight check

[mohierf]

It looks ok. And what about the logs in the arbiterd.log and brokerd.log files ?

[loops21]

I can't see anything wrong in the logs ... :/ arbiterd.txt brokerd.txt

[mohierf]

Everythong seems fine in your logs ... except the very verbose stats broker module ;)

Sorry but I do not see where this problem comes from 😞 perharps a problem that appeared with the 3.0 version? You should try to use an older version with the same configuration

[loops21]

Thank's a lot for your help, tuesday i will install a new shinken on the server.

[naparuba]

Can you also try with another UI? Like Thruk (it will use another broker module, so we better know where the error can came from).

Thanks :)

[naparuba]

@mohierf For 3.0 it's the enterprise backport branch and some other new features are in preparation when I have spare time (but with 3 childs, there is very few :( )

[mohierf]

@naparuba : I do not think that another module is the more interesting test 😉 The WebUI is using the Shinken Datamanager to populate the UI ... if not hosts get populated then probably something changed in the Datamanager, no?

IMHO, you should have created a branch for this 3.0 version to avoid such problems with the repo master branch...

[loops21]

Hi ! I've installed the 2.4.2 version this morning and all works perfectly !

Thank's a lot for your help !

[hvad]

Hi, I installed shinken from RPM version 2.4.3 with webui2 2.4.2c and it's work. Best regard

[geektophe]

Hello @loops21 could you have a test with the latest master branch and let me know if the issue persists ?