On Fri, Nov 19, 2010 at 1:09 AM, jpliste <jpli...@jppozzi.dyndns.org> wrote:
> Hello,
>
> Hi,
> Sorry, I didn't have time to do the testing.
> I download the last version from git repository.
> The "central" system is OK, all is running smoothly, the "external"
> realm is detected, and the arbiter try to send data to the "external"
> realm.
> ====================================================================
> ......
> Cutting the hosts and services into parts
> Creating packs for realms
> Number of hosts in the realm All : 8
> Number of hosts in the realm testweb : 1
> Things look okay - No serious problems were detected during the
> pre-flight check
> ====================================================================
>
> Data are sent (visible with an "iptables" counter), but the client side
> does not receive the data ... the logs are really only to complain about
> no data received.
>
> A little complaint about the debug log : the messages does not contains
> any kind of timestamps, it is very difficult to compare and understand
> the different logs. Chronology is important ...
>
Ok
>
> Log for the "realm" broker :
>
you mean "testweb" realm ?
> cat broker.debug
> [Broker] Using working directory : /var/lib/shinken
> [Broker] Opening port: 7772
> Waiting for initial configuration
> .......
>
> log for the realm poller :
> cat poller.debug
> Using working directory : /var/lib/shinken
> Opening port: 7771
> Waiting for initial configuration
> We ask us for a ping
> .We ask us for a ping
> .We ask us for a ping
> .We ask us for a ping
>
>
> Log for the reactionner :
> cat reactionner.debug
> Using working directory : /var/lib/shinken
> Opening port: 7769
> Waiting for initial configuration
> We ask us for a ping
> .We ask us for a ping
> .We ask us for a ping
>
> Log for the scheduler :
> cat scheduler.debug
> Using working directory : /var/lib/shinken
> Listening on: 192.168.1.120 : 7768
> The Arbiter Interface is at:
> PYRO://192.168.1.120:7768/7f00010104bb09be98aa00000074b3b8
>
Why not 0.0.0.0:7768? in the schedulerd.ini it wrote 0.0.0.0, so it should
be 0.0.0.0 here too.
> Waiting for initial configuration
> ..............................................................
>
> Log for the arbiter on the "central" server :
>
> Scheduler configuration 1 is unmanaged!!
> Warning : Missing satellite reactionner for configuration 1 :
> Warning : Missing satellite poller for configuration 1 :
> Warning : Missing satellite broker for configuration 1 :
> Dispatching Realm All
> [All] Dispatching 0/1 configurations
> [All] Schedulers order : scheduler-1
> Dispatching Realm testweb
> [testweb] Dispatching 1/1 configurations
> [testweb] Schedulers order : scheduler-web
> [testweb] Dispatching one configuration
> [testweb] Trying to send conf 1 to scheduler scheduler-web
>
Is there anything more between this lines? It should cry about a bad send or
something like it.
> WARNING : All schedulers configurations are not dispatched, 1 are
> missing
>
And we need to know why :)
without a scheduler, all other satellites do not have configuration because
they do not need to, so the problem is in the scheduler send.
> Nb Broks send: 0
>
> Repeated # every second
>
> Here is the specific part for that bloody realm in the
> shinken-specific.cfg file :
> ====================================================================
> .......
> # special testweb
> #
>
> define realm {
> realm_name testweb
> default 0
> }
> #Reactionner launch notifications
> define reactionner{
> reactionner_name reactionner-web
> address 192.168.1.120
> port 7769
> spare 0
> manage_sub_realms 0
> min_workers 1
> max_workers 5
> polling_interval 3
> #optionnal
> realm testweb
> }
> define broker{
> broker_name broker-web
> address 192.168.1.120
> port 7772
> spare 0
>
> #Which modules to load? Here only status.dat and nagios.log
> modules Status-Dat, Simple-log, Livestatus, ToMerlindb_Mysql
> #optionnal
> manage_sub_realms 1
> manage_arbiters 0 ;only one broker for the arbiter
> #advanced
> realm testweb
> }
>
> define scheduler{
> scheduler_name scheduler-web
> address 192.168.1.120
> port 7768
> #optional
> spare 0
> weight 1
> #advanced feature
> realm testweb
> }
>
> define poller{
> poller_name poller-web
> address 192.168.1.120
> port 7771
> #optional
> manage_sub_realms 0
> min_workers 2
> max_workers 2
> processes_by_worker 127
> polling_interval 5
> #advanced feature
> realm testweb
> }
>
> =====================================================================================
>
> Here the host + service definition :
>
> =====================================================================================
> # special testweb
> define host{
> use generic-host
> host_name loc-t1
> alias testweb_frontal
> address loc-t1.jpp.fr
> check_command check_ping!4.0,80%!10.0,80%!
> realm testweb
> max_check_attempts 3
> notification_interval 1800
> notification_period 24x7
> notification_options d,u,r
> register 1
> }
>
> define service {
> use generic-HTTP
> host_name loc-t1
> name KMAIL-LOCT1
> contact_groups virtuel
> notification_interval 480
> normal_check_interval 200
> check_interval 10
> }
>
> =====================================================================================
>
> Here are the configuration files for the 4 modules on the "external"
> server.
>
> =====================================================================================
> [daemon]
> #relative from this cfg file
> workdir=/var/lib/shinken
> pidfile=%(workdir)s/brokerd.pid
> interval_poll=5
> maxfd=1024
> port=7772
> host=0.0.0.0
> user=shinken
> group=shinken
> idontcareaboutsecurity=no
>
> [daemon]
> #relative from this configuration file
> workdir=/var/lib/shinken
> pidfile=%(workdir)s/pollerd.pid
> interval_poll=5
> maxfd=1024
> port=7771
> host=0.0.0.0
> user=shinken
> group=shinken
> # realm testweb
> idontcareaboutsecurity=no
>
> [daemon]
> #relative from this cfg file
> workdir=/var/lib/shinken
> pidfile=%(workdir)s/reactionnerd.pid
> interval_poll=5
> maxfd=1024
> port=7769
> host=0.0.0.0
> user=shinken
> group=shinken
> idontcareaboutsecurity=no
>
> [daemon]
> #Relative from this cfg file
> workdir=/var/lib/shinken
> pidfile=%(workdir)s/schedulerd.pid
> port=7768
> host=0.0.0.0
>
Are you sure about this line?
> user=shinken
> group=shinken
> idontcareaboutsecurity=no
> ========================================================
>
> The configuration seems good. I try you conf in my environnement (same code
version) and it's ok.
Do you have the same Pyro version in both side? And same Python version too?
To know Pyro version, just launch a python interpreter and launch :
$python
import Pyro
print Pyro.constants.VERSION
It must be the same in the both sides.
I'll add it in the debug output.
If you have 0.0.0.0 and the same Python/Pyro version, we will have to add
more debug output I think to know why the conf is not send to the scheduler.
there should be "pinging scheduler-web" lines on the arbiter-debug. Are they
OK?
Thanks,
Jean
> Regards
>
> JP Pozzi
>
>
>
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
> Spend less time writing and rewriting code and more time creating great
> experiences on the web. Be a part of the beta today
> http://p.sf.net/sfu/msIE9-sfdev2dev
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
