Difference: KnownIssues (42 vs. 43)

Revision 432012-12-21 - PaoloAndreetto

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

Known issues

Line: 14 to 14
  "Received NULL fault; the error is due to another cause: FaultString=[CREAM service not available: configuration failed!] - FaultCode=[SOAP-ENV:Server] - FaultSubCode=[SOAP-ENV:Server]"
Deleted:
<
<

Problem by submitting jobs via WMS (direct submission to CREAM CE isn't affected by this problem)

There is an unwanted auto-updating of the field "creationTime" on the cream database. This happen, for example, when tomcat is restarted (yaim does the stop and the start of the tomcat service).

Submitting jobs via WMS, you could obtain the following wrong message:

=================== glite-wms-job-status Success =================

BOOKKEEPING INFORMATION:

Status info for the Job : ...

Current Status: Aborted <-----------------

Status Reason: CREAM'S database has been scratched and all its jobs have been lost <-----------------

Destination: ...

Submitted: ...

Parent Job: ...

======================================================================

N.B: The CREAM database isn't scratched, but it is so from the WMS point of view because of the above problem.

The problem is solved applying the following workaround on the cream database:


use creamdb; ALTER TABLE db_info MODIFY creationTime TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP; commit;
 

EMI-2 CREAM CE delegates bad proxy to WN

The delegated and limited proxy on the CE contains a corrupted field "X509v3 Key Usage"; this issue can be reproduced executing the following command:
openssl x509 -noout -text -in /var/glite/cream_sandbox/[vo]/[dn_fqan_mappeduser]/proxy/[delegationid_internalid]
Line: 298 to 265
 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)
Added:
>
>

Problem by submitting jobs via WMS (direct submission to CREAM CE isn't affected by this problem)

There is an unwanted auto-updating of the field "creationTime" on the cream database. This happen, for example, when tomcat is restarted (yaim does the stop and the start of the tomcat service).

Submitting jobs via WMS, you could obtain the following wrong message:

=================== glite-wms-job-status Success =================

BOOKKEEPING INFORMATION:

Status info for the Job : ...

Current Status: Aborted <-----------------

Status Reason: CREAM'S database has been scratched and all its jobs have been lost <-----------------

Destination: ...

Submitted: ...

Parent Job: ...

======================================================================

N.B: The CREAM database isn't scratched, but it is so from the WMS point of view because of the above problem.

The problem is solved applying the following workaround on the cream database:


use creamdb; ALTER TABLE db_info MODIFY creationTime TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP; commit;
 

Problem with cancelled jobs notification

In BLAH 1.18.0(EMI2) to run correctly the notification of cancelled jobs it is needed to add in /etc/blah.config the row:

 
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