Re: [Gridscheduler-users] what voodoo should I invoke to get a working OGE ???

[Rayson Ho <ray...@gm...>]

Hi Eric,

You just need to configure SSH with passwordless login:

http://gridscheduler.sourceforge.net/howto/qrsh_qlogin_ssh.html

And with the tight ssh integration, all the disadvantages in the HOWTO
do not apply anymore.

Rayson



On Thu, Jul 7, 2011 at 12:16 PM, Eric Belhomme
<eri...@ev...> wrote:
> Le 06/07/2011 20:20, Rayson Ho a écrit :
>>
>> Hi Eric,
>>
>> Sorry, the SGE 6.2u5p3 release is overdue... besides the libcore fix
>> we are checking in, we still need to fix the Java build stuff -- On
>> the other hand, it's Canadian day&  Independence Day last/this week so
>> we are taking some personal time off :D
>>
> welcome to real life ;)
>
>> Please see the flags we use to compile Grid Engine / OGS:
>>
>> http://gridscheduler.sourceforge.net/CompileGridEngineSource.html
>>
> I already pointed on that page, but it didn't helped me a lot
>
>>
>> And libcore is located at this following URL, and you will need to
>> build it as a shared lib:
>>
>> http://gridscheduler.sourceforge.net/patches/libcore.c
>>
> thanks for the pointer. Why is it not explained on
> CompileGridEngineSource.html document ?
>
>> And if you want to compile ssh tight integration, read this
>> presentation we gave at the SGE workshop back in 2007:
>>
>>
>> http://gridscheduler.sourceforge.net/patches/SGE-WS2007-openSSHTightIntegration_RonChen.pdf
>>
>
> Very interesting, but once again, it's addressed for SGE/OGS devel gurus,
> and I'm not !
> I tried to compile openssh 5.8p2 (and 5.5p1) but I can't pass the
> "configure" step under aimk, I always get this :
>
> configure: error: *** compiler cannot create working executables, check
> config.log ***
> make: Makefile: No such file or directory
> make: *** No rule to make target `Makefile'.  Stop.
> not done
>
> After many hours spent to understand what happened, I finally understood I
> got a "chiken & egg" problem, as aimk tries to link openssh with  sge libs.
>
> So here is what I did :
>
>
> ./aimk -no-java -no-jni -no-secure -spool-classic -only-depend
> ./scripts/zerodepend
> ./aimk -no-java -no-jni -no-secure -spool-classic depend
> ./aimk -no-java -no-jni -no-secure -spool-classic
>
> Then :
>
> ./aimk -no-java -no-jni -no-secure -spool-classic -tight-ssh depend
> ./aimk -no-java -no-jni -no-secure -spool-classic -tight-ssh
>
> And I finally was able to go to link step to openssh before it failed :-/
> Some hours of brainstorming after, I figured it failed because of a missing
> symbol "g_new_interactive_job_support" that is defined in shepherd.c
> As I was unable to figure why openssh tries to link with, and as this symbol
> is not exported by a SGE library, I choosed to symply define it into sshd.c
> like this :
> char g_new_interactive_job_support = 0;
>
> And it worked !
>
> At least I was able to do a scripts/distinst -all -local -noexit
> successfully.
> But I'm still a bit confused, as ssh binaries are not included into the dist
> installation ? Is it a normal behavious ? Should I handle manually the new
> ssh/sshd deployment into all nodes ?
>
> In fact, how to configure SGE (sorry, I mean OGS ;) to use ssh instead of
> rsh ?
>
> Thanks,
>
> --
> Eric Belhomme  -  EVE SA  -  www.eve-team.com
> 2bis, voie la cardon, 91120 PALAISEAU, FRANCE
> Tel: +33 1 64 53 27 30,Fax: +33 1 64 53 27 40
>