Difference: KnownIssues (2 vs. 3)

Revision 32011-07-21 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="GeneralDocumentation"

Known issues

Deleted:
<
<
Known problems in CREAM software or in other software modules affecting a CREAM based CE (the list refer to known problem affecting the latest release of the software in production)
 
Changed:
<
<

Condor and SGE support

>
>

Open known issues

Known problems in CREAM software or in other software modules affecting a CREAM based CE (the list refer to known problem affecting the latest release of the software released in EMI)

Problems affecting users with certificates signed by the GermanGrid

Because of a bug in trustmanager, users with certificates signed by the GermanGrid CA can't submit jobs to CREAM. The error message is something like:

Failed to create a delegation id for job https://grid-lb0.desy.de:9000/ADkeOt6tc0Rfi8oP-pzUrQ: reason is Client 'O=GermanGrid,OU=DESY,CN=Alexander Fomenko' is not issuer of proxy 'O=GermanGrid,OU=DESY,CN=Alexander Fomenko,CN=proxy,CN=proxy'.

Condor and SGE support

  Condor and SGE are not yet fully supported as batch system for CREAM.
Changed:
<
<

Execution of DAG jobs

>
>

Execution of DAG jobs

  Execution of DAG jobs on the CREAM based CE through the gLite WMS is not implemented yet.
Changed:
<
<

qsub crashes

>
>

Memory issues with new BLAH Blparser

If the new Blparser is used (click here to check this) there can be issues if the blah registry becomes very large. The submission process can get slower and there can be problems with memory usage.

Waiting for the fix, there are two possible workarounds:

  • Reduce the number of multiple instances of blahpd (the default value is 50). This means changing the value cream_concurrency_level in cream-config.xml. To apply the change, you will then need to restart tomcat. This should help addressing the issue, but it will also mean less parallel instances interacting with the batch system (and so a possible reduction of the throughput in the submission to the batch system)
. Click here to get more details
  • Reduce the value for purge_interval in blah.config. This value is expressed in seconds. A job is removed from the BLAH registry (and therefore not managed anymore by BLAH and therefore CREAM) after purge_interval seconds since its submission. To apply the change, you will then need to restart the blparser (/etc/init.d/glite-ce-blahparser restart)

Relevant bug: https://savannah.cern.ch/bugs/index.php?75854

qsub crashes

  With some Torque versions it was observer qsub crashing with glibc detecting a double free or corruption.Although this is a problem to be addressed in Torque problem, adding:
Line: 26 to 55
 to /etc/blah.config should help
Changed:
<
<

CREAM CE not Torque master: communication errors when the maui server and client are not of the same builds.

>
>

CREAM CE not Torque master: communication errors when the maui server and client are not of the same builds.

  * Bug #61698: when the CREAM CE is not a Torque server, there could be communication errors when the maui (and probably torque) server and client are NOT of the same builds.
Line: 82 to 111
 vo_max_jobs_cmd: /opt/lcg/libexec/vomaxjobs-maui -h lcg-ce –infile /import/dir/to/cream-ce/diagnose-for-cream
Changed:
<
<

Reconfiguration after update

>
>

Reconfiguration after update

  After an update of the CREAM RPM, it is mandatory to reconfigure (via yaim)
Changed:
<
<

Special characters in CREAM_DB_USER and CREAM_DB_PASSWORD

>
>

Special characters in CREAM_DB_USER and CREAM_DB_PASSWORD

  Don't use special characters in the CREAM_DB_USER and CREAM_DB_PASSWORD yaim variables
Changed:
<
<

Problems with OS language different than US English

>
>

Problems with OS language different than US English

  Problems have been reported if jobs are submitted through the WMS to a CREAM CE deployed on a machine installed using a non-English language. This is because of different representations of decimal numbers. The workaround in this case is to uncomment the line:
Line: 101 to 130
 in $CATALINA_HOME/conf/tomcat5.conf and then restart tomcat
Added:
>
>

Old known issues

Problems in CREAM software or in other software modules affecting a CREAM based CE that have already been fixed (i.e. they are not affecting the latest release of the software released in EMI)

Problems with SubCAs when Argus is used as authorization system

There are problems when CREAM CE is configured to use Argus, happening with sub-CAs (e.g. CERN-TCA, UKeScienceCA)

  -- MassimoSgaravatto - 2011-05-05
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback