For the records: According to
http://www.globus.org/toolkit/docs/5.2/5.2.0/gram5/rn/#gram5-fixed
it's a bug and fixed in 5.2...
On 10/12/11 12:12 PM, Martin Feller wrote:
Hi Globus team,
GT version: 5.0.4
jglobus version: 1.8.0
When I submit a job using jglobus' Gram API, the
On 03/27/2010 03:46 AM, Joseph Bester wrote:
That model is not supported by 5.0.0.
Try this patch. It uses the DN of the certificate to come up with a
semi-unique token that is appended to the service tag. Jobs with
different tags will run in separate job managers and won't deal with
each
On 03/29/2010 07:31 PM, Vladimir Mencl wrote:
We would do more thorough testing over this (and maybe next week).
Yuriy, who's doing most of the work on the client side of the job
submission (and who found the issue) is on training this week.
We'll report again when we do more testing - but
Hey Joe,
What are the disadvantages of configuring GRAM with -tag-with-dn-hash,
or stated differently, why not make this the default and only behavior?
JP
On Mar 26, 2010, at 9:46 AM, Joseph Bester wrote:
On Mar 25, 2010, at 9:45 PM, Vladimir Mencl wrote:
Hi,
We are evaluating how GRAM5
On Mar 26, 2010, at 11:21 AM, JP Navarro wrote:
Hey Joe,
What are the disadvantages of configuring GRAM with -tag-with-dn-hash,
or stated differently, why not make this the default and only behavior?
JP
The only potential problem I see is that the names of the files in
~/.globus/job are
On Mar 22, 2010, at 11:33 PM, Vladimir Mencl wrote:
Hi,
I had setup GRAM5 with PBS on a system here - and everything seemed
working all fine.
... until I tried specifying a queue name in the RSL. Not specifying
it, or specifying the single queue the system was setup with, job
submission
On 03/23/2010 11:12 PM, Joseph Bester wrote:
When the globus_gram_job_manager_pbs_setup postinstall occurs, it gathers the
names of the queues by default and adds those to the
$GLOBUS_LOCATION/share/globus_gram_job_manager/pbs.rvf file as enumerated
values for the queue RSL attribute.
On 03/13/2010 02:55 AM, Joseph Bester wrote:
That seems an odd place for the output to stop. Any chance the
globus-scheduler-event-generator program is built threaded? I think I
see a deadlock condition that can occur in it if that's the case.
Hi Joseph,
Thanks for this pointer - that helped
On 03/13/2010 02:55 AM, Joseph Bester wrote:
Weird. I'll have to try that and see where it goes wrong.
Hi Joseph,
Thanks for looking into it.
I only get:
[INFO] Enter globus_l_pbs_increase_buffer
[INFO] Exit globus_l_pbs_increase_buffer
and the output stops there. Any idea
On 03/11/2010 01:33 AM, Joseph Bester wrote:
pbs_log_path=/usr/spool/PBS/server_logs
Now, I could run the event-generator without any error.
Do events for jobs started outside of globus show up in the SEG log file when
you run the SEG?
Hi Joe,
Thanks for the reply.
I've now had a
On Mar 10, 2010, at 12:59 AM, Vladimir Mencl wrote:
Hi,
I'm installing GRAM5 (GT 5.0.0) on a CentOS 5 x86_64 system with Torque.
I got gatekeeper going and I can submit simple jobs all fine.
I've tried to switch to using the Scheduler event generator, but got
stuck on that:
I was
On Feb 11, 2010, at 7:26 PM, Aaron Hicks wrote:
Hi the list,
Well GRAM5 has a SGE Adapter, but the only documentation for it is here:
http://www.globus.org/toolkit/docs/5.0/5.0.0/execution/gram5/admin/#gram5-admin-lrmAdapters
Which covers, how to install GRAM5 with the SGE adapter and
12 matches
Mail list logo
