Bad uid for job execution msg ruserok failed validating

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=[0] 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.For complex and rarely used packaged you are often to nasty surprises. Also some packagers are pretty perverted and add to the package additional dependencies or configure is is a completely bizarre way.They are typically volunteers and nobody controls what they are doing.INFO ,862 Help Formatter - Date/Time: 2016/01/14 INFO ,862 Help Formatter - ---------------------------------------------------------------------- INFO ,863 Help Formatter - ---------------------------------------------------------------------- INFO ,878 QCommand Line - Scripting CNVDiscovery Pipeline INFO ,222 QCommand Line - Added 15 functions INFO ,222 QGraph - Generating graph. INFO ,623 Function Edge - Starting: 'java' '-Xmx2048m' '-XX: Use Parallel Old GC' '-XX: Parallel GCThreads=4' '-XX: GCTime Limit=50' '-XX: GCHeap Free Limit=10' 'tmpdir=/home/gaoyh/software/svtoolkit/installtest/tmpdir' '-cp' '/home/gaoyh/software/svtoolkit/lib/SVToolkit.jar:/home/gaoyh/software/svtoolkit/lib/gatk/Genome Analysis TK.jar:/home/gaoyh/software/svtoolkit/lib/gatk/Queue.jar' '-cp' '/home/gaoyh/software/svtoolkit/lib/SVToolkit.jar:/home/gaoyh/software/svtoolkit/lib/gatk/Genome Analysis TK.jar:/home/gaoyh/software/svtoolkit/lib/gatk/Queue.jar' 'org.queue.

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=[0] Description=[system error] Fault Cause=[Batch System pbs not supported!

Inno DB: If you are using big BLOB or TEXT rows,you must set the Inno DB: combined size of log files at least 10 times bigger than the Inno DB: largest such row. All activities about the job are tracked on its "command history", that is a sort of recorder realized for the purpose of noting the main internal/external events (i.e.

This means that the sudo operation (which is used to copy the proxy to a user specific directory) failed, very likely because of an an error in the sudoers file (e.g. the commands) which condition the job's life cycle.

$ /bin/cat [ executable="/bin/sleep"; arguments="1000"; ] $ glite-ce-job-submit -a -r alice16ru:8443/cream-pbs-dteam https://alice16ru:8443/CREAM510970530 $ glite-ce-job-cancel https://alice16ru:8443/CREAM510970530 $ 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=[0] Description=[system error] Fault Cause=[Batch System pbs not supported! 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.

Please, be sure that BLAH is properly configured and RESTART the CREAM service.

Leave a Reply