[Bigjob-users] Problems with BigJob example

Andre Luckow aluckow at cct.lsu.edu
Tue Jan 3 08:11:19 CST 2012


Hi Ole,
BigJob doesn't use SAGA for launching jobs - the default job adaptor
has severe limitations, e.g. it cannot launch MPI jobs or jobs on
remote machines. The primary use case of BJ is the management of
multiple nodes. For this purpose, BJ relies on SSH. Since the local
version is just used for development purposes the same mechanisms are
applied here.

Best,
Andre

On Tue, Jan 3, 2012 at 2:23 PM, Ole Weidner <oweidner at cct.lsu.edu> wrote:
> Hi Andre,
>
> I'm a little confused: I thought big-job uses SAGA (and in the case of my example fork://) to launch the sub-jobs? I'm running the example on my local machine were I would like to avoid any type of password-less ssh logins!
>
> Why is ssh required in the fork:// case?
>
> Thanks,
> Ole
>
> On Jan 3, 2012, at 4:48 AM, Andre Luckow wrote:
>
>> Hi Ole
>>
>>> However, stdout.txt doesn't contain the output of /bin/date but "ssh: connect to host localhost port 22: Connection refused". I have no idea where this comes from.
>>
>> BigJob utilizes SSH for the execution of sub-jobs. Please ensure that
>> your local SSH daemon is up and running and that you can login without
>> password.
>>
>> Best,
>> Andre
>
> _______________________________________________
> Bigjob-users mailing list
> Bigjob-users at mail.cct.lsu.edu
> https://mail.cct.lsu.edu/mailman/listinfo/bigjob-users


More information about the Bigjob-users mailing list