Hello all, I would like to get you in touch of my progress. I think I solved the issue. The advise to search which user was logged when executing the job was good. This user was the user "gridamin" which is the user used to install the exec daemon. In fact, the problem was due to the fact this user did not get sudo rights. Historically, when I have executed the install_execd script, I was logged as my user "gridadmin" I used for the installation. However, this user was not sudo. Hence, the exec daemon did not get any rights to write in other users home dir or to change user. Now, I executed again the install_execd script with sudo and the daemon restarted. And when I submit a job now with the user "tommy", the user used is "tommy" that can correctly write in /home/tommy. It seems that the daemon change user. Note that UID are not synchronized on the machines and the things seems to work ok...
Thank a lot for your advises... Lionel ________________________________________ De : [email protected] [[email protected]] de la part de Malcolm Cowe [[email protected]] Date d'envoi : vendredi 27 juillet 2012 01:31 À : [email protected] Objet : Re: [gridengine users] RE : Managing user password A half-way house for user management is to maintain the accounts on one system and distribute the passwd files (passwd, shadow, group, etc.) using rsync or CF-Engine or Puppet. Malcolm. On 27/07/12 02:05, Rayson Ho wrote: > On Thu, Jul 26, 2012 at 11:46 AM, Lionel SPINELLI > <[email protected]> wrote: >> Now I understand better : I need my users to be defined on a centralized >> point (LDAP or NIS) so they are shared by all machines. Complex since the >> platform I try to manage is linux based and the rest of the IT system in the >> lab is Microsoft based. > IIRC, you don't need to have a centralized user account management > system, and in fact even same account w/ different UIDs *should* work. > Grid Engine looks up the account information when it starts a job, so > really a sync UID is not absolutely needed, but it can be if you have > a shared filesystem that has ACLs that uses UID. > > Instead of implementing a centralized user account system, which > *really* is lots of work, I think the best to approach is to find out > why it can't write to the local disk. You can submit a job that runs > "id", and output it to the shared FS, and check if the job is really > running as the job owner. And then you can login as tommy and run > something interactively and see if writing to the local disk is OK or > not, etc... basically standard Linux admin stuff - you got the idea. > :-) > > Rayson > > > >> Thanks a lot for your responses... I will try to find a solution... >> >> >> Lionel >> ________________________________________ >> De : Rayson Ho [[email protected]] >> Date d'envoi : jeudi 26 juillet 2012 17:37 >> À : Reuti >> Cc : Lionel SPINELLI; [email protected] >> Objet : Re: [gridengine users] Managing user password >> >> On Thu, Jul 26, 2012 at 11:32 AM, Reuti<[email protected]> wrote: >>>> But when I try to submit a job, I got an error telling "error: can't open >>>> output file "/home/tommy/simple.sh.o60": Permission denied >>>> >>>> Obviously, if i use the -o and -e option of qsub to put the output and >>>> error logs to a shared disk without write permissions, anything is ok. >>> Mmh - is it now shared with or without write permission? "... to a shared >>> disk without write permissions, it won't work". >> I think Lionel means with... >> >> AND BTW, Grid Engine does not need to login as the user with a >> password, so you don't need the same password for tommy. Also, >> different UIDs for each tommy account should also work, however that >> writing to a shared disk works but a local disk fails (or vice versa?) >> means that it can be the UID issue... >> >> Rayson >> >> >> >> >> >>> -- Reuti >>> >>> >>>> So, how can i get my user "tommy" able to submit jobs that need to write >>>> temporary files (for instance) on the account "tommy" ? >>>> >>>> Thanks in advance >>>> >>>> Lionel >>>> >>>> >>>> _______________________________________________ >>>> users mailing list >>>> [email protected] >>>> https://gridengine.org/mailman/listinfo/users >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> https://gridengine.org/mailman/listinfo/users > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
