-----Original Message----- From: owner-drmaa-wg@ggf.org [mailto:owner-drmaa-wg@ggf.org] On Behalf Of Tim Harsch Sent: Monday, August 08, 2005 8:07 PM To: Matthew Holt Cc: DRMAA-WG Subject: Re: [drmaa-wg] Perl Binding Errors
It seems to be telling you what the problem is: job rejected: root@grid0.cs.elon.edu is not allowed to submit jobs
What I usually do is test SGE first, then run make test of Schedule::DRMAAc. If SGE works by itself you should be in good shape.
Test SGE by runnning the simplest test job. ie:
% qsub <<EOF sleep 30 EOF
% qstat # do you see a job in the queue? Check your home directory for output files called STDIN.e## and STDIN.o## ( where ## is the job id )
Join the SGE users list for help setting up your SGE distro...
----- Original Message ----- From: "Matthew Holt" <mholt@elon.edu> To: "Tim Harsch" <harsch1@llnl.gov> Sent: Monday, August 08, 2005 5:39 PM Subject: RE: [drmaa-wg] Perl Binding Errors
Tim, I have unsubscribed myself from the drmaa-wg list already, so
for sending directly to my email. I continued with the integration of SGE/GT4. I went back and ran the tests and the output is different this time. I've included both the 'make test' output and the 'make test TEST_VERBOSE=1' output in text files. I am running on Red Hat Enterprise Linux AS 4 using perl version 5.8.5.
Thanks for the help.
Matt
________________________________
From: Tim Harsch [mailto:harsch1@llnl.gov] Sent: Mon 8/8/2005 8:20 PM To: Matthew Holt; drmaa-wg@gridforum.org Subject: Re: [drmaa-wg] Perl Binding Errors
Sorry, haven't checked messages from this group for a couple of days....
If it didn't pass that test, I doubt its fully functional. You should rerun the test to see if the failed output is repeatable. If so, run as: make test TEST_VERBOSE=1 and send the output...
Also, what OS are you running on? what version of Perl are you using?
----- Original Message ----- From: "Matthew Holt" <mholt@elon.edu> To: <drmaa-wg@gridforum.org> Sent: Thursday, August 04, 2005 3:37 PM Subject: FW: [drmaa-wg] Perl Binding Errors
Was able to resolve the problem after a complete reinstall and following the below steps. I ran the make test this time and only received the below error:
t/01_constants.........ok t/02_subs..............ok t/03_system_queries....ok t/04_standard_attrs....ok t/05_vector_attrs......dubious Test returned status 255 (wstat -1, 0xffffffff) test program seems to have generated a core after all the subtests completed successfully t/06_simple_job........ok t/07_complex_job.......ok t/08_posix_tests.......ok
But I am going to assume that it's alright. Otherwise, could someone let me know. Thanks. Matthew Holt
________________________________
From: Fred L Youhanaie [mailto:fly@anydata.co.uk] Sent: Thu 8/4/2005 1:28 AM To: Matthew Holt Subject: Re: [drmaa-wg] Perl Binding Errors
Hi Matthew,
You shouldn't need to run swig, i.e.
unpack cd Schedule-DRMAAc-0.81 ln -s $SGE_ROOT/include/drmaa.h perl Makefile.PL make make test make install
Cheers f.
Matthew Holt wrote:
Hey Everyone, I am having trouble with the setup of the Perl Bindings for SGE 6.0. As root, I created a directory for the install as /root/integrate/Schedule-DRMAAc-0.81 and did the following:
export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/sge/lib/:/usr/local/sge/uti l/ar ch/
ln -s $SGE_ROOT/include/drmaa.h
swig -perl5 -exportall Schedule_DRMAAc.i
perl Makefile.pl -Only possible error was: Note (probably harmless): No library found for -lsocket
make
make test
-This is where I ran into the problem.. Everyone one of the tests
failed.
Here is sample output from what I thought was the most descriptive of
Just a tiny remark... Several DRM systems disallow root account for job submission. Hrabri thanks the
error messages:
Global symbol "$DRMAA_ERRNO_SUCCESS" requires explicit package name at t/08_posix_tests.t line 116. Global symbol "$DRMAA_ERRNO_SUCCESS" requires explicit package name at t/08_posix_tests.t line 122. Global symbol "$DRMAA_ERRNO_SUCCESS" requires explicit package name at t/08_posix_tests.t line 130. Execution of t/08_posix_tests.t aborted due to compilation errors. # Looks like your test died before it could output anything. t/08_posix_tests.......dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-32 Failed 32/32 tests, 0.00% okay
Any ideas on what I am doing wrong? Thanks. Matthew Holt