Re: Executor can't start d-bus communication

Excellent, glad you got it sorted! Cheers, Greg On Wed, Oct 14, 2015 at 8:24 AM, Pradeep Kiruvale wrote: > Hi Greg, > > I solved the issue. The problem was with credentials. I was running > Master and Slave as root and Framework as normal user. > > After I started all components as user, its

Re: Executor can't start d-bus communication

Hi Greg, I solved the issue. The problem was with credentials. I was running Master and Slave as root and Framework as normal user. After I started all components as user, its worked. I wrote the executor using the Executor APIs. By creating a new class. Thanks for your reply. Regards, Prade

Re: Executor can't start d-bus communication

Hi Pradeep, Can you tell us a bit about your executor: in particular, did you write it against the Executor API , or is it a plain executable that gets run through the command executor? Cheers, Greg On Wed, Oct 14, 201

Executor can't start d-bus communication

Hi All, I have written a new framework and an executor. I launch the task from Framework and the task get pushed to the specific slave/executor based on the resource availability. But on the executor side it has to connect to an application which is running and providing the service through the d-