Difference: KnownIssues (35 vs. 36)

Revision 362012-10-05 - PaoloAndreetto

Line: 1 to 1

META TOPICPARENT	name="GeneralDocumentation"

Known issues

Line: 62 to 62

NULL;

Deleted:

<
<

GlueCEStateWaitingJobs: 444444 and WallTime workaround

If on the queues there is published:

GlueCEStateWaitingJobs: 444444

and in the log /var/log/bdii/bdii-update.log you notice errors like the folllowing:

Traceback (most recent call last):
  File "/usr/libexec/lcg-info-dynamic-scheduler", line 435, in ?
    wrt = qwt * nwait
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

probably the queues have no "resources_default.walltime" parameter configured. So define it for each queue by launching, for example:

# qmgr -c "set queue prod resources_default.walltime = 01:00:00"
# qmgr -c "set queue cert resources_default.walltime = 01:00:00"
# qmgr -c "set queue cloudtf resources_default.walltime = 01:00:00"

Error parsing GLUE2PolicyRule

All the attibutes "GLUE2PolicyRule" defined in the file /var/lib/bdii/gip/ldif/ComputingShare.ldif MUST BE in the form "VO:nameofthevo" (the VO prefix is mandatory) Other strings, even the empty one, are not correctly parsed by the script lcg-info-dynamic-scheduler and the following error is reported in the BDII log:

vogrp = tmpl[2].strip()
IndexError: list index out of range

In that case the wrong attributes MUST BE removed

Problem at first configuration with EMI-2 CREAM with GE

Line: 120 to 93

bupdater_use_bhist_for_killed="yes"

Deleted:

<
<

Problem with generic dynamic scheduler with SGE

The yaim plugin for sge configures the gip for publishing information but when used out of the box the following error is shown in the BDII log:

Traceback (most recent call last):
File "/usr/libexec/lcg-info-dynamic-scheduler", line 256, in ?
import lrms
ImportError: No module named lrms

The workaround is defining PYTHONPATH in /var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper:

$ cat /var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
#!/bin/sh
#/opt/lcg/libexec/lcg-info-dynamic-scheduler -c /opt/glite/etc/lcg-info-dynamic-scheduler.conf
export PYTHONPATH=/usr/lib/python:$PYTHONPATH
/usr/libexec/lcg-info-dynamic-scheduler -c /etc/lcg-info-dynamic-scheduler.conf

Relevant ticket: https://ggus.eu/ws/ticket_info.php?ticket=76961

Issue with conflicting BUpdaterSGE instances

gLite service in CreamCE starts the following services by this exact order: tomcat5, glite-lb-locallogger and glite-ce-blahparser.

Line: 307 to 268

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 with generic dynamic scheduler with SGE

The yaim plugin for sge configures the gip for publishing information but when used out of the box the following error is shown in the BDII log:

Traceback (most recent call last):
File "/usr/libexec/lcg-info-dynamic-scheduler", line 256, in ?
import lrms
ImportError: No module named lrms

The workaround is defining PYTHONPATH in /var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper:

$ cat /var/lib/bdii/gip/plugin/glite-info-dynamic-scheduler-wrapper
#!/bin/sh
#/opt/lcg/libexec/lcg-info-dynamic-scheduler -c /opt/glite/etc/lcg-info-dynamic-scheduler.conf
export PYTHONPATH=/usr/lib/python:$PYTHONPATH
/usr/libexec/lcg-info-dynamic-scheduler -c /etc/lcg-info-dynamic-scheduler.conf

Relevant ticket: https://ggus.eu/ws/ticket_info.php?ticket=76961

Fix provided with EMI-2 update 3

Error parsing GLUE2PolicyRule

vogrp = tmpl[2].strip()
IndexError: list index out of range

In that case the wrong attributes MUST BE removed

Fix provided with EMI-2 update 3

GlueCEStateWaitingJobs: 444444 and WallTime workaround

If on the queues there is published:

GlueCEStateWaitingJobs: 444444

and in the log /var/log/bdii/bdii-update.log you notice errors like the folllowing:

Traceback (most recent call last):
  File "/usr/libexec/lcg-info-dynamic-scheduler", line 435, in ?
    wrt = qwt * nwait
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

probably the queues have no "resources_default.walltime" parameter configured. So define it for each queue by launching, for example:

# qmgr -c "set queue prod resources_default.walltime = 01:00:00"
# qmgr -c "set queue cert resources_default.walltime = 01:00:00"
# qmgr -c "set queue cloudtf resources_default.walltime = 01:00:00"

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

Fix provided with EMI-2 update 3

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.

View topic | History: r69 < r68 < r67 < r66 | More topic actions...