Hey! Thanks for the reply. After a painful few days I managed to narrow it down to an error (that was being swallowed, grr!!) as a result of an implementation bug in Tornado (the python library we're using for the libprocess http service). I've since submitted a patch here https://github.com/tornadoweb/tornado/pull/1124 - feel free to chime in!
This highlights an issue with Mesos which I have also opened here https://issues.apache.org/jira/browse/MESOS-1625. I'd love to get any input on the problem, as i'm a little scared about the consequences if this were to be fixed. In other news, pesos is now working and i'm finishing off the rest of the actions/callback implementations today. Tom. On 23 Jul 2014, at 07:42, Vetoshkin Nikita <[email protected]> wrote: > Hi, Tom! > I would gladly help you to debug if you could provide some information > about your setup. Is it localhost only communication? Any code snippet to > reproduce the problem? > > P.S. I'm trying to setup pesos and it seems like python3.3 is a requirement > but it isn't mentioned anywhere. > > > On Tue, Jul 22, 2014 at 1:45 AM, Tom Arnfeld <[email protected]> wrote: > >> Hey, >> >> I've started to try and finish off the work @wickman started around >> pesos[1] and compactor[2] - pure language bindings for mesos and libprocess >> in Python. It's currently far from finished, but have fun into a brick wall >> around libprocess. If anyone could shed any light that'd be great. >> >> To start with, I saw the framework register but disconnect immediately. >> From a quick chat on IRC someone mentioned this could be related to not >> keeping the inbound message connection open, the one that sends >> mesos.internal.FrameworkRegisteredMessage. In doing this, the framework >> does register with the master and shows up in the UI – however no further >> messages are received at all. I'm keeping the outbound connection open >> already. >> >> Mesos seems to think it's sending offers (they show up in the logs and are >> showing in the Offers page) but the master never gets past there, and the >> framework never receives the HTTP connections. No doubt this is a bug in >> the socket logic on my end. Struggling to find my way through the >> libprocess source to figure it out. >> >> Any pointers would be much appreciated. >> >> Thanks! >> >> Tom. >> >> [1] https://github.com/wickman/pesos >> [2] https://github.com/wickman/compactor
