 |
 |
Hi, There is an automatic tool that can be used to check if *some* parts of the CREAM CE have been properly configured or if there are some issues to fix. This tool is based on the ig-fry framework. To use this tool: * Install the ig-fry rpm from http://www.pd.infn.it/~sgaravat/ig-fry/ The Latest version of ig-fry for CREAM is 3.1.2-0 * Install the rpm * Run it: fry -v -s <siteinfo.def> siteinfo.def> is the one used to configure the CREAM CE via yaim Please then post the produced output (Please note that if fry reports that everything is ok, this only means that the tests done by fry were successfully passed. This doesn't exclude that there are still issues in some other parts of the CE configuration not checked by fry) Regards 2009/2/5 Douglas McNab <[log in to unmask]>: > Hi, > > I have a few questions about setting up a cream ce and wondered if anyone > had any ideas about the issues I am seeing. > I believe that I have set up the grid service correctly but when I submit a > job using the simple CLI tools I receive an error message. > Unfortunately, I have been through the logs and have not found anything that > is helping me diagnose the issue. > I am sure it probably something very silly I have forgotten to set up but > any help would be appreciated. > > So far I have been following the instructions at: > http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:guides:devel:install-cream31-devel > > The test job was submitted using: glite-ce-job-submit -a -d -r > dev011.gla.scotgrid.ac.uk:8443/cream-pbs-q30m hellocream.jdl > and results in this fatal error: > > 2009-02-05 14:08:28,217 FATAL - MethodName=[jobRegister] Timestamp=[Thu 05 > Feb 2009 14:08:28] ErrorCode=[0] Description=[system error] > FaultCause=[cannot write the job wrapper (jobId = CREAM304767308)! The > problem seems to be related to glexec which reported: Broken pipe] > > investigating the logs I found the stacktrace in the catalina.out: > > org.glite.ce.creamapi.cmdmanagement.CommandException: cannot write the job > wrapper (jobId = CREAM810541183)! The problem seems to be related to glexec > which reported: Broken pipe at > org.glite.ce.creamapi.jobmanagement.cmdexecutor.AbstractJobExecutor.createJobSandboxDir(AbstractJobExecutor.java:1038) > > I have seen this page: > http://grid.pd.infn.it/cream/field.php?n=Main.ErrorMessagesReportedByCREAMToClient > which details the error message reported so this lead me to the glexec > logs. I increased the verbosity and debug levels in the glexec file in > order to help debug this issue. However, I failed to find anything of any > interest in /opt/glite/var/log/glexec_lcas_lcmaps.log > > it appears that it has mapped my credential correctly and there does not > appear to be any errors reported: > > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): 1 > ***************************************** > ** > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): SIGLEN: 256 > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): USER: > /C=UK/O=eScience/OU=Glasgow/L=Comps > erv/CN=douglas mcnab > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): UCA: > /C=UK/O=eScience/OU=Glasgow/L=Comps > erv/CN=douglas mcnab > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): SERVER: > /C=UK/O=eScience/OU=Glasgow/L=Comps > [log in to unmask] > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): SCA: > /C=UK/O=eScienceCA/OU=Authority/CN= > UK e-Science CA > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): VO: vo.scotgrid.ac.uk > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): URI: svr029.gla.scotgrid.ac.uk:15000 > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): DATE1: 20090205130408Z > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): DATE2: 20090206010408Z > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): fqan: > /vo.scotgrid.ac.uk/Role=NULL/Capabi > lity=NULL > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): GROUP: /vo.scotgrid.ac.uk > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): ROLE: NULL > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): CAP: NULL > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas_plugin_voms-print_vomsdata(): 1 > ***************************************** > ** > > LCAS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcas.mod-lcas_run_va(): succeeded > > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > Credential Print: > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > dn : /C=UK/O=eScience/OU=Glasgow/L=Compserv/CN=douglas > mcnab > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > uid : 220001 [1/1] > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > pgid : 220000 [1/1] > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : VO credential > mapping : [1/1] > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcmaps_printVoMapping(): address of vo mapping struct: 0x92da118 > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcmaps_printVoMapping(): VO string: > /vo.scotgrid.ac.uk/Role=NULL/ > Capability=NULL > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcmaps_printVoMapping(): mapped groupname: scotg > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > lcmaps_printVoMapping(): mapped GID: 220000 > LCMAPS 0: 2009-01-05.14:08:27-25329-glexec_get_accounts : > pool_index : > %2fc%3duk%2fo%3descience%2fou%3dglasgow%2fl%3dcompserv%2fcn% > 3ddouglas%20mcnab:scotg > > Does anyone know what sort of common errors would occur with glexec? > > Regards, > > Dug >