Nope, nothing about the scheduler trying to connect. :/ I agree the message isn’t making it there – this is why I fired up tcpdump, and attached the HTTP conversation to my original message, because it’s not a particularly sensible HTTP conversation from my POV, but the scheduler is talking to the socket for the mesos API.
I’m running the scheduler on the same host, and there are no relevant firewall rules, all tables (almost said chains ;d) are ACCEPT. I suppose I could try tcpdump on a successful register on the working cluster and see what’s diff, I’ll try this and report back. From: Vinod Kone <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, April 18, 2016 at 1:46 PM To: user <[email protected]<mailto:[email protected]>> Subject: Re: kafka-mesos still refusing to launch brokers on one cluster Is there nothing in the mesos master logs about this scheduler trying to connect/register? If not, the registration message from the scheduler is not making it to the master. Are there any firewall rules between the scheduler host and master host? ________________________________ P Please consider the environment before printing this e-mail The information in this electronic mail message is the sender's confidential business and may be legally privileged. It is intended solely for the addressee(s). Access to this internet electronic mail message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. The sender believes that this E-mail and any attachments were free of any virus, worm, Trojan horse, and/or malicious code when sent. This message and its attachments could have been infected during transmission. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective and remedial action about viruses and other defects. The sender's employer is not liable for any loss or damage arising in any way.
