Difference: KnownIssues (30 vs. 31)

Revision 312012-07-04 - EricFrizziero

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

Known issues

Line: 8 to 8
  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)
Added:
>
>

FAILURE_REASON="Cannot enqueue the command id=-1: Data truncation: Data too long for column 'commandGroupId' at row 1 (rollback performed)"

it's a bug reintroduced in EMI-2 CREAM CE: https://savannah.cern.ch/bugs/index.php?95593

A workaround is to modify a database table by executing the following query:

use creamdb; ALTER TABLE command_queue MODIFY commandGroupId varchar(255) 
NULL; 
 

GlueCEStateWaitingJobs: 444444 and WallTime workaround

If on the queues there is published:

Line: 112 to 124
  This will be fixed in EMI 2.
Deleted:
<
<

Issue with the setting of the maximum number of accepted FTP connections

The number of maximum number of gridftp connections is now automatically set in /etc/grid-security/gridftp.conf.

It should be manually added also in the file /etc/gridftp.conf where the line:

connections_max 150

should be added.

Relevant ticket: https://ggus.eu/tech/ticket_show.php?ticket=78902

 

Significant changes introduced with Torque 2.5.7-1

The updated EPEL5 build of torque-2.5.7-1 as compared to previous versions enables munge[1] as an inter node authentication method. Please see

Line: 268 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:
>
>

Issue with the setting of the maximum number of accepted FTP connections

The number of maximum number of gridftp connections is now automatically set in /etc/grid-security/gridftp.conf.

It should be manually added also in the file /etc/gridftp.conf where the line:

connections_max 150

should be added.

Relevant ticket: https://ggus.eu/tech/ticket_show.php?ticket=78902

 

Memory leak in bupdater for PBS and LSF

Version 1.16.3 of BLAH is affected by a quite critical memory leak in the bupdater component for LSF and PBS. Because of that the usage of memory of the bupdater process will keep increasing till when it crashes/it is killed by OOM. It is then automatically restarted by blah.

 
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