Hi,
It seems that the arbiter is not seeing the scheduler ofthe second realm,
but I do not see any revelant error in the debug output. I add some weeks
ago a "Pinging " output message of the artbier and I do not see it in the
debug. Can you update the source and try with a newer version? with the
pinging message, we will see how the arbiter "see" (or not and why) this
scheduler that seems to open the port like it should (0.0.0.0).
Thanks a lot,
Jean
On Mon, Nov 29, 2010 at 9:35 AM, nap <[email protected]> wrote:
> Thanks, I'll try to see what happen between the arbiter and the scheduler.
>
>
> Jean
>
> On Sat, Nov 27, 2010 at 5:13 PM, jpliste <[email protected]>wrote:
>
>> Le lundi 22 novembre 2010 à 09:43 +0100, nap a écrit :
>>
>> Hello,
>>
>> After running (with success) a single Shibken installation on both
>> machine I restore the "realm" machine and had a new try.
>> The test process was :
>> - starting tcpdump in file mode
>> - fire the "central" Shinken (debug moad)
>> - fire the "realm" Shinken (debug moad)
>> - wait one or two minutes
>> - stop all
>>
>> The arbiter"s log in the central machine was always growing at a fast
>> rate saying that a configuration was not ....
>>
>> The tcpdump file shows a "conversation" between the two machines, but
>> the log of the scheduler does not show any trace of connection.
>>
>> I get all the log files and join them with this mail, I hope that it can
>> help to get what is wrong.
>>
>> Regards
>>
>> JP P
>>
>>
>>
>> > On Sat, Nov 20, 2010 at 7:08 PM, jpliste <[email protected]>
>> > wrote:
>> > Le samedi 20 novembre 2010 à 12:56 +0100, Gerhard Lausser a
>> > écrit :
>> > > Hi,
>> > >
>> > > when you listen on the network
>> > > realm-machine# tcpdump port 7768
>> > > do you see any traffic?
>> > >
>> >
>> > Hello,
>> >
>> > Yes there is traffic on all 77xx ports.
>> > I have made two tests on the "realm" machine :
>> > 1) local shinken not launched.
>> > The central machine send packets on the 77xx ports
>> > 2) local shinken launched
>> > There are packets from/to both sides, but I can't see anything
>> > new in
>> > the debug files. The logs on the central machine are as usual
>> > always
>> > saying that the distribution in not complete.
>> >
>> > Will try more ASAP and examine the logs on both sides.
>> > Hi,
>> >
>> > what the arbiter debug say about pinging this scheduler? The "ping" is
>> > in fact a Pyro call, so this one should be in error. It looks liek
>> > there a problem between the two Pyro nodes, but ti's strange if it's
>> > all the same version :( (we can do linux<->windows calls, so why not
>> > ubuntu<->debian ones?).
>> >
>> > Look at the pinging tests, we will see if this is good (I think it is
>> > because it try to send conf).
>> >
>> >
>> > Jean
>> >
>> >
>> >
>> > Regards
>> >
>> > JP P
>> >
>> >
>> >
>> > > Gerhard
>> > >
>> > > > -----Ursprüngliche Nachricht-----
>> > > > Von: jplog [mailto:[email protected]]
>> > > > Gesendet: Samstag, 20. November 2010 01:49
>> > > > An: [email protected]
>> > > > Betreff: Re: [Shinken-devel] New to the list with a
>> > problem
>> > > >
>> > > > Hello,
>> > > >
>> > > > I verify the versions and there was a problem with
>> > Python's version.
>> > > >
>> > > > REALM machine Debian
>> > > > Python 2.6.5 (Was 2.5.5) --> upgrade to 2.6.5
>> > > > Pyro 3.9.1
>> > > >
>> > > >
>> > > > CENTRAL machine Ubuntu (VM downloaded from the
>> > > > site running under XEN)
>> > > > Python 2.6.5
>> > > > Pyro 3.9.1
>> > > >
>> > > > After migrating the Debian machine to Python 2.6.5 :
>> > > >
>> > > > Messages on the "realm" machine :
>> > > >
>> > ==============================================================
>> > > > =============
>> > > > tail -f scheduler.debug
>> > > > Using working directory : /var/lib/shinken
>> > > > Listening on: 0.0.0.0 : 7768
>> > > > The Arbiter Interface is at:
>> > > > PYRO://0.0.0.0:7768/7f00010105010a42f7ab0000008d6518
>> > > > Waiting for initial configuration
>> > >
>> > > ..............................................................
>> > > > ............
>> > > >
>> > > >
>> > > > Messages on the "central" machine :
>> > > >
>> > ==============================================================
>> > > > =============
>> > > > tail -f arbiter.debug
>> > > > tail -f arbiter.debug
>> > > > 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
>> > > > WARNING : All schedulers configurations are not
>> > dispatched, 1 are
>> > > > missing
>> > > > Nb Broks send: 0
>> > > > 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
>> > > > WARNING : All schedulers configurations are not
>> > dispatched, 1 are
>> > > > missing
>> > > > Nb Broks send: 0
>> > > > ......
>> > > > (repeating every second)
>> > > >
>> > ==============================================================
>> > > > =============
>> > > > The communication seems to be estabished ( on the "realm"
>> > machine ) :
>> > > > lsof -Pn | grep TCP | grep ':77'
>> > > > python 1281 shinken 3u IPv4 5635
>> > 0t0 TCP
>> > > > *:7768 (LISTEN)
>> > > > python 1281 shinken 4u IPv4 5707
>> > 0t0 TCP
>> > > > 192.168.1.120:7768->192.168.1.21:35042 (ESTABLISHED)
>> > > > python 1285 shinken 5u IPv4 5663
>> > 0t0 TCP
>> > > > *:7771 (LISTEN)
>> > > > python 1285 shinken 6u IPv4 5711
>> > 0t0 TCP
>> > > > 192.168.1.120:7771->192.168.1.21:48913 (ESTABLISHED)
>> > > > python 1293 shinken 5u IPv4 5692
>> > 0t0 TCP
>> > > > *:7769 (LISTEN)
>> > > > python 1293 shinken 6u IPv4 5709
>> > 0t0 TCP
>> > > > 192.168.1.120:7769->192.168.1.21:51613 (ESTABLISHED)
>> > > > python 1299 shinken 3u IPv4 5705
>> > 0t0 TCP
>> > > > *:7772 (LISTEN)
>> > > > python 1299 shinken 4u IPv4 5713
>> > 0t0 TCP
>> > > > 192.168.1.120:7772->192.168.1.21:51667 (ESTABLISHED)
>> > > >
>> > > > as on the "central" machine :
>> > > > lsof -Pn | grep TCP | grep ':77'
>> > > > python 1281 shinken 3u IPv4 5635
>> > 0t0 TCP
>> > > > *:7768 (LISTEN)
>> > > > python 1281 shinken 4u IPv4 5707
>> > 0t0 TCP
>> > > > 192.168.1.120:7768->192.168.1.21:35042 (ESTABLISHED)
>> > > > python 1285 shinken 5u IPv4 5663
>> > 0t0 TCP
>> > > > *:7771 (LISTEN)
>> > > > python 1285 shinken 6u IPv4 5711
>> > 0t0 TCP
>> > > > 192.168.1.120:7771->192.168.1.21:48913 (ESTABLISHED)
>> > > > python 1293 shinken 5u IPv4 5692
>> > 0t0 TCP
>> > > > *:7769 (LISTEN)
>> > > > python 1293 shinken 6u IPv4 5709
>> > 0t0 TCP
>> > > > 192.168.1.120:7769->192.168.1.21:51613 (ESTABLISHED)
>> > > > python 1299 shinken 3u IPv4 5705
>> > 0t0 TCP
>> > > > *:7772 (LISTEN)
>> > > > python 1299 shinken 4u IPv4 5713
>> > 0t0 TCP
>> > > > 192.168.1.120:7772->192.168.1.21:51667 (ESTABLISHED)
>> > > >
>> > > > If TCP connections are open why do they not communicate !
>> > > >
>> > > > Trying from "central" a telnet connection on the port 7768
>> > gives the
>> > > > Pyro prompt :
>> > > > telnet loc-t1 7768
>> > > > Trying 192.168.1.120...
>> > > > Connected to loc-t1.jpp.fr.
>> > > > Escape character is '^]'.
>> > > > PYRO x? ?5E????B
>> > > >
>> > > > and the "realm" react by some weird messages :
>> > > >
>> > > > Traceback (most recent call last):
>> > > > File
>> > "/usr/local/shinken/shinken/../bin/shinken-scheduler",
>> > > > line 595,
>> > > > in <module>
>> > > > p = Shinken(config_file, is_daemon, do_replace, debug,
>> > debug_file)
>> > > > File
>> > "/usr/local/shinken/shinken/../bin/shinken-scheduler",
>> > > > line 372,
>> > > > in __init__
>> > > > self.wait_initial_conf()
>> > > > File
>> > "/usr/local/shinken/shinken/../bin/shinken-scheduler",
>> > > > line 413,
>> > > > in wait_initial_conf
>> > > >
>> > shinken.pyro_wrapper.handleRequests(self.poller_daemon, s)
>> > > > File "/usr/local/shinken/shinken/pyro_wrapper.py", line
>> > 88, in
>> > > > handleRequests
>> > > > daemon.handleRequests()
>> > > > File "/usr/lib/pymodules/python2.6/Pyro/protocol.py",
>> > line 1064, in
>> > > > handleRequests
>> > > > self._handleRequest_NoThreads(timeout,others,callback)
>> > > > File "/usr/lib/pymodules/python2.6/Pyro/protocol.py",
>> > line 1085, in
>> > > > _handleRequest_NoThreads
>> > > > if self.getAdapter().handleConnection(conn, self):
>> > > > File "/usr/lib/pymodules/python2.6/Pyro/protocol.py",
>> > line 746, in
>> > > > handleConnection
>> > > > ver,body,pflags = self.receiveMsg(conn)
>> > > > File "/usr/lib/pymodules/python2.6/Pyro/protocol.py",
>> > line 560, in
>> > > > receiveMsg
>> > > > self.returnException(conn, ProtocolError(msg))
>> > > > File "/usr/lib/pymodules/python2.6/Pyro/protocol.py",
>> > line 723, in
>> > > > returnException
>> > > > pic=Pyro.util.getXMLPickle('gnosis')
>> > > > File "/usr/lib/pymodules/python2.6/Pyro/util.py", line
>> > 439, in
>> > > > getXMLPickle
>> > > > raise NotImplementedError('xml pickling implementation
>> > (%s) is not
>> > > > available' % impl)
>> > > > NotImplementedError: xml pickling implementation (gnosis)
>> > is not
>> > > > available
>> > > >
>> > > > I don't know how to test now !
>> > > >
>> > > > Regards
>> > > >
>> > > > JP P
>> > > >
>> > > >
>> > > >
>> > > >
>> > --------------------------------------------------------------
>> > > > ----------------
>> > > > 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
>> > > > [email protected]
>> > > > https://lists.sourceforge.net/lists/listinfo/shinken-devel
>> > > >
>> > >
>> > >
>> > > __________ Hinweis von ESET NOD32 Antivirus,
>> > Signaturdatenbank-Version 5634
>> > > (20101119) __________
>> > >
>> > > E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>> > >
>> > > http://www.eset.com
>> > >
>> > >
>> > >
>> > >
>> >
>> ------------------------------------------------------------------------------
>> > > 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
>> > > [email protected]
>> > > 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
>> > [email protected]
>> > 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 [email protected]
>> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
>> Tap into the largest installed PC base & get more eyes on your game by
>> optimizing for Intel(R) Graphics Technology. Get started today with the
>> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
>> http://p.sf.net/sfu/intelisp-dev2dev
>>
>> _______________________________________________
>> Shinken-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>>
>>
>
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Shinken-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shinken-devel
