Try "qrsh -verbose hostname" -- see if it prints any debug messages?
http://gridscheduler.sourceforge.net/howto/commonproblems.html#interactive Rayson On Wed, Apr 13, 2011 at 2:07 PM, Casimir Wierzynski <[email protected]> wrote: > Dear Grid Engine community, > We recently upgraded from RHEL4 to RHEL 6 on all of our grid machines and > qmake isn't working any more. > I think I've narrowed the problem down to the fact that qrsh doesn't work, > although qsub does. > When I run qmake, it exits without ever scheduling any of the dependent > jobs. If I try to run one of the dependent jobs via qrsh, the job starts up > briefly on one of the machines but then quickly exits without completion. If > I submit the same thing via qsub, it works file. > Here is a minimal example I've put together: > === test.make === > .PHONY : all > > > > all : > > /ghome/cas/test.sh > > > === test.sh === > /bin/hostname >> /ghome/samba/cas/out > ============ > Here are the commands I run: > [cas@ca1-4 ~]$ qmake -cwd -v PATH -- -j 999 -f /ghome/cas/test.sh > qmake: *** cannot determine architecture from environment variable SGE_ARCH > no default architecture set > (qmake starts on a machine and then exits without running test.sh) > [cas@ca1-4 ~]$ qrsh /ghome/cas/test.sh > (test.sh runs on one of the machine and exits without creating output > file) > [cas@ca1-4 ~]$ qsub test.sh > Your job 10398 ("test.sh") has been submitted > (works fine) > I am puzzled, but I am also relatively new to SGE so I apologize if I am > doing something silly. > Cas > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
