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 works all fine: > >> globusrun -o -r ng1.canterbury.ac.nz >> '&(executable=/bin/hostname)(queue=small)' >> ngcompute.canterbury.ac.nz > > But when I pass any other queue name, it fails: > >> globusrun -o -r ng1 '&(executable=/bin/hostname)(queue=gt5test) >> 'GRAM Job submission failed because the provided RSL 'queue' parameter is >> invalid (error code 37) > > The queue does exist and I can submit jobs to that queue as the local user. > >> From what I could trace, the LRM interface script pbs.pm does NOT get > invoked at all - somehow, the job manager decides the queue name > specified is invalid. > > I'm attaching below the output I got in ~/gram_<date>.log. > > I'm running the GT 5.0.0 release, on Linux CentOS 5.4 x86_64. > > Any help would be highly appreciated. > > Cheers, > Vladimir
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. This can be disabled by running cd $GLOBUS_LOCATION/setup ./setup-globus-job-manager-pbs.pl -validate-queues=no or removing the queues entry in the rvf file. Joe
