Also, the error message says it's "validating testuser/testuser". Because the UID should be testuser, but the GID is set to something else. I can do qstat, though, from submithosts and compute nodes.In case your blparser node servers multiple CREAM CEs, please be sure to have followed the instructions reported at Administrator Guide For EMI1#1_4_5_1_Configuration_of_the_old $ glite-ce-job-submit -D de2 -r cream-02infn.it:8443/cream-lsf-cream prren12008-01-28 ,859 FATAL - Method Name=[job Register] Timestamp=[Mon ] Error Code= Description=[delegation error: the proxy delegation ID "de2" is not more valid! ] $ cat job_ids ##CREAMJOBS## https://devel03infn.it:8443/CREAM683051516 https://devel03infn.it:8443/CREAM481684356 https://devel03infn.it:8443/CREAM333841302 https://devel03infn.it:8443/CREAM279829555 https://devel03infn.it:8443/CREAM334653961 ****** Job ID=[https://ppsce03es:8443/CREAM880596078] Status = [ABORTED] Exit Code =  Failure Reason = [BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Bad UID for job execution MSG=ruserok failed validating dteam017/dteam017 from ppsce03es-) N/A (job Id = CREAM880596078)] 2009-09-10 ,082 ERROR - Received NULL fault; the error is due to another cause: Fault String=[org.glite.security.delegation.storage.Gr DPStorage Exception: Configuration error: delegation_factorynull] - Fault Code=[SOAP-ENV: Exception] - Fault Sub Code=[SOAP-ENV: Exception] - Fault Detail=[ This problem can happen when submitting to CREAM through the WMS.[Update Nov 2016: I have since confirmed that this method works without change on 16.04 LTS as well, and have updated the post to note this.
In less than 10 minutes you'll have it up and running...Here, I'll present one way to do it on a Debian based Linux system.Ubuntu might work just as well, since Ubuntu is very similar to Debian.(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.