the blparser was not running when tomcat was started). It must be stressed, as reported here that the right procedure is: $ glite-ce-job-submit -a -r cert-26infn.it:8443/cream-pbs-cream 2008-01-15 ,167 FATAL - Method Name=[job Register] Timestamp=[Tue ] Error Code= Description=[system error] Fault Cause=[Batch System pbs not supported!
] This means that an error related with glexec happened in the CREAM CE.
BLParser Client - initialize Connection: getting info about BLParser (xxx) from BLAH (retry count=yy/zz) ... BLParser Client - initialize Connection error: cannot get BLParser (lsf) HOST: PORT information from BLAH.
To avoid that, I produced a Run Job script that breaks up the running in 5 pieces, each producing smaller outputs much easier to handle.(We are running Torque and Maui.) When I try to submit a job from the new cluster (a machine called morph4), I see: $ echo "sleep 10" | qsub -q morph qsub: Bad UID for job execution MSG=ruserok failed validating testuser/testuser from morph4 (morph is the new cluster.) testuser is set up so that it has the same UID and GID on all of the machines in the network.If I give the same command from a machine on the old cluster (submitting to morph), it runs.Also, the error message says it's "validating testuser/testuser". Because the UID should be testuser, but the GID is set to something else. The user name defined in the user list is either undefined or different from the user name of the job submitter or the user UID and GID at the executing node are different from the ones in the submitting node.