Main.KnownIssues History

Hide minor edits - Show changes to markup - Cancel

November 04, 2011, at 03:25 PM by 193.205.157.206 -
Changed lines 9-12 from:
  • Bug #73481: The blparser for SGE is not able to manage already finished jobs. This means that cancelled jobs or jobs finished in a not clean way are reported with a wrong status
to:
Added lines 150-151:
  • Bug #73481: The blparser for SGE is not able to manage already finished jobs. This means that cancelled jobs or jobs finished in a not clean way are reported with a wrong status. Fix provided with gLite 3.2 Update 32
September 01, 2011, at 09:45 AM by 193.205.157.206 -
Changed line 7 from:
  • Bug #86238: Torque should be configured to suppress all mails (mail_domain=never). Otherwise the buptarer process of the blparser will keep dying.
to:
  • Bug #86238: Torque should be configured to suppress all mails (mail_domain=never). Otherwise the bupdater process of the blparser will keep dying.
September 01, 2011, at 09:45 AM by 193.205.157.206 -
Added lines 6-7:
  • Bug #86238: Torque should be configured to suppress all mails (mail_domain=never). Otherwise the buptarer process of the blparser will keep dying.
June 27, 2011, at 04:19 PM by 193.205.157.206 -
Changed line 27 from:
In case of a fresh installation, instead, add an exclude line to the .repo file (/etc/yum.repos.d/slc5-updates.repo):
to:
In case of a fresh installation, instead, add an exclude line to the .repo file (/etc/yum.repos.d/slc5-updates.repo or main SL repository, starting with SL 5.6):
May 23, 2011, at 02:25 PM by 151.83.205.158 -
Changed line 27 from:

In case of a fresh installation, instead, add an exclude line to the .repo file (/etc/yum.repos.d/slc5-updates.repo):

to:
In case of a fresh installation, instead, add an exclude line to the .repo file (/etc/yum.repos.d/slc5-updates.repo):
May 23, 2011, at 02:24 PM by 151.83.205.158 -
Changed lines 7-11 from:
  • Bug #73481: The blparser for SGE is not able to manage already finisghed jobs. This means that cancelled jobs or jobs finished in a not clean way are reported with a wrong status

There are problems

to:
  • Bug #73481: The blparser for SGE is not able to manage already finished jobs. This means that cancelled jobs or jobs finished in a not clean way are reported with a wrong status
Changed lines 19-20 from:
  • When updating a CREAM CE node, a dependency problem such as:
to:
  • When installing/updating a CREAM CE node, a dependency problem such as:
Added line 22:
Added lines 26-29:

In case of a fresh installation, instead, add an exclude line to the .repo file (/etc/yum.repos.d/slc5-updates.repo):

exclude=c-ares
May 17, 2011, at 03:52 PM by 193.205.157.206 -
Added lines 1-3:

This page refers to the gLite version of CREAM. For CREAM released with EMI, please refer to the new CREAM wiki: http://wiki.italiangrid.org/CREAM

Deleted lines 5-7:

This page refers to the gLite version of CREAM. For CREAM released with EMI, please refer to the new CREAM wiki: http://wiki.italiangrid.org/CREAM

May 17, 2011, at 03:52 PM by 193.205.157.206 -
Added lines 4-5:

This page refers to the gLite version of CREAM. For CREAM released with EMI, please refer to the new CREAM wiki: http://wiki.italiangrid.org/CREAM

February 24, 2011, at 08:07 PM by 82.52.182.167 -
Added lines 144-146:
  • Bug #78565: problem with truncation of arguments. Fix provided with gLite 3.2 Update 23
February 21, 2011, at 11:28 AM by 193.205.157.206 -
Added lines 5-9:
  • Bug #73481: The blparser for SGE is not able to manage already finisghed jobs. This means that cancelled jobs or jobs finished in a not clean way are reported with a wrong status

There are problems

Added lines 15-16:
  • Bug #78331: The bupdater log file is not created with SGE
February 16, 2011, at 09:49 AM by 193.205.157.206 -
Added lines 79-80:
  • Execution of DAG jobs on CREAM based CE through the gLite WMS is not implemented yet.
February 11, 2011, at 11:19 PM by 82.50.178.192 -
Added lines 4-9:
  • Bug #78062: with CREAM CE 1.6.4, in the standard output of the job wrapper the following message is shown:
jw_echo: command not found.
The workaround, is to modify the CREAM jw template, as described here replacing "jw_echo" with "echo". At any rate this issue doesn't cause particular problems
February 11, 2011, at 10:51 PM by 82.50.178.192 -
Changed lines 8-9 from:
could be seen.

In this case, the update should be done doing:

to:
could be seen. In this case, the update should be done doing:
February 11, 2011, at 10:51 PM by 82.50.178.192 -
Added lines 3-11:
  • When updating a CREAM CE node, a dependency problem such as:
Error: Missing Dependency: libcares.so.0()(64bit) is needed by package glite-security-gss-2.0.0-6.sl5.x86_64
could be seen.

In this case, the update should be done doing:

yum update --exclude=c-ares
February 10, 2011, at 07:31 AM by 79.30.241.112 -
Added lines 165-166:
Fix provided with gLite 3.2 Update 22.
February 10, 2011, at 07:30 AM by 79.30.241.112 -
Changed lines 114-121 from:
  • Bug #74807: there are problems if the mapping for a certain user is changed, and jobs refer to a delegationid created before the change.
Waiting for the fix, as workaround each delegationid created by that user before the mapping change should be manuallu removed, as shown in the following example.
use delegationdb;
delete from t_credential where dlg_id='cert12345678' and local_user='dteam002';
to:
Added lines 156-164:
  • Bug #74807: there are problems if the mapping for a certain user is changed, and jobs refer to a delegationid created before the change.
Waiting for the fix, as workaround each delegationid created by that user before the mapping change should be manuallu removed, as shown in the following example.
use delegationdb;
delete from t_credential where dlg_id='cert12345678' and local_user='dteam002';
February 10, 2011, at 07:28 AM by 79.30.241.112 -
Deleted lines 4-31:
  • In the old CREAM CE (CREAM CE < 1.6.3) the sudoers file was scratched at each yaim reconfiguration and filled with just the stuff needed for CREAM. This meant that local customizations were scratched. In the new CREAM CE (CREAM CE 1.6.3) yaim:
    • checks if the installed sudo version supports the include directive (this should be the case for SL5)
    • cleans from /etc/sudoers the CREAM related stuff existing from a previous installation
    • if sudo supports include directives (this should be the case for SL5), yaim sets the CREAM related stuff in /etc/sudoers.forcream and adds in /etc/sudoers the include of /etc/sudoers.forcream
There is a problem with the cleaning part, which doesn't work properly if the name of the users don't include the name of the group: bug #76235
For gLite 3.2, when updating to CREAM CE 1.6.3 from previous versions this means that the sudoers file could have some problems after the yaim reconfiguration. When the sudoers file is manually fixed, the problems won't happen anymore in following yaim reconfigurations
  • Bugs #73224 and #73109 in yaim-core: the variable GLOBUS_TCP_PORT_RANGE could not be properly defined and therefore causing problems with gridftp, See the workaround specified in these bugs
  • Bug #69320: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:
mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info
where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.
Do not move the directories named <subcluster> from /opt/glite/var/info.
Changed lines 74-75 from:
  • Because of bug #37366 (in gsoap-plugin) some error messages are not propagated properly, and in this case user simply get something like:
to:
  • On SL(c)4 when kerberos is used, the /usr/bin/id executable can be affected by a problem: the exit code could be different than 0, as in the following example:
Changed lines 78-82 from:

Received NULL fault; the error is due to another cause: : FaultString=[Client fault] - FaultCode=[SOAP-ENV:Client]

to:
  1. su dteam001 -

[dteam001@cert-08 glexec]$ id uid=1651(dteam001) gid=2688(dteam) groups=2688(dteam),1090601808 [dteam001@cert-08 glexec]$ echo $? 1

Deleted lines 84-96:
The problem has been fixed in gLite 3.2, so it is relevant for direct submissions done by a gLite 3.1 UI and by submissions through WMS for a gLite 3.1 WMS
  • On SL(c)4 when kerberos is used, the /usr/bin/id executable can be affected by a problem: the exit code could be different than 0, as in the following example:
# su dteam001 -
[dteam001@cert-08 glexec]$ id
uid=1651(dteam001) gid=2688(dteam) groups=2688(dteam),1090601808
[dteam001@cert-08 glexec]$ echo $?
1
Added lines 128-162:
  • Bugs #73224 and #73109 in yaim-core: the variable GLOBUS_TCP_PORT_RANGE could not be properly defined and therefore causing problems with gridftp, See the workaround specified in these bugs. Fix provided with gLite 3.2 Update 22.
  • In the old CREAM CE (CREAM CE < 1.6.3) the sudoers file was scratched at each yaim reconfiguration and filled with just the stuff needed for CREAM. This meant that local customizations were scratched. In the new CREAM CE (CREAM CE 1.6.3) yaim:
    • checks if the installed sudo version supports the include directive (this should be the case for SL5)
    • cleans from /etc/sudoers the CREAM related stuff existing from a previous installation
    • if sudo supports include directives (this should be the case for SL5), yaim sets the CREAM related stuff in /etc/sudoers.forcream and adds in /etc/sudoers the include of /etc/sudoers.forcream
There is a problem with the cleaning part, which doesn't work properly if the name of the users don't include the name of the group: bug #76235.
For gLite 3.2, when updating to CREAM CE 1.6.3 from previous versions this means that the sudoers file could have some problems after the yaim reconfiguration. When the sudoers file is manually fixed, the problems won't happen anymore in following yaim reconfigurations.
Fix provided with CREAM CE 1.6.4 (released with gLite 3.2 Update 22)
  • Bug #69320: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:
mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info
where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.
Do not move the directories named <subcluster> from /opt/glite/var/info.
Fix provided with gLite 3.2 Update 22
  • Because of bug #37366 (in gsoap-plugin) some error messages are not propagated properly, and in this case user simply get something like:
Received NULL fault; the error is due to another cause: : FaultString=[Client fault] - FaultCode=[SOAP-ENV:Client]
The problem has been fixed in gLite 3.2, so it is relevant for direct submissions done by a gLite 3.1 UI and by submissions through WMS for a gLite 3.1 WMS
January 25, 2011, at 10:45 AM by 193.205.157.206 -
Added lines 23-32:
  • Bug #69320: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:
mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info
where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.
Do not move the directories named <subcluster> from /opt/glite/var/info.
Changed lines 173-180 from:
  • Bug #69320: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:
mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info
where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.
Do not move the directories named <subcluster> from /opt/glite/var/info.
to:
December 12, 2010, at 11:56 PM by 95.232.48.152 -
Changed lines 7-8 from:
  • checks if the installed sudo version supports the include directive (this should be the case for SL5, while this shouldn't be the case for SL4)
to:
  • checks if the installed sudo version supports the include directive (this should be the case for SL5)
Changed lines 10-14 from:
  • if sudo supports include directives (this should be the case for SL5), yaim sets the CREAM related stuff in /etc/sudoers.forcream and adds in /etc/sudoers the include of /etc/sudoers.forcream
  • If sudo doesn't supports include directives (this should be the case for SL4), yaim sets the CREAM related stuff in /etc/sudoers
There is a problem with the cleaning part, which doesn't work properly if the name of the users don't include the name of the group: bug #75369
to:
  • if sudo supports include directives (this should be the case for SL5), yaim sets the CREAM related stuff in /etc/sudoers.forcream and adds in /etc/sudoers the include of /etc/sudoers.forcream
There is a problem with the cleaning part, which doesn't work properly if the name of the users don't include the name of the group: bug #76235
Changed lines 16-19 from:
For gLite 3.1, this means that the sudoers file could have some problems after each yaim reconfiguration.
Possible workarounds are:
  • To restore the previous version of the sudoers file (the one existing before the reconfiguration) which is saved in /etc/sudoers.bak_<date>_<time>
  • To do the yaim configuration starting with a sudoers file which doesn't contain anything related to CREAM
to:
November 16, 2010, at 01:11 PM by 193.205.157.206 -
Changed lines 5-11 from:
  • In the old CREAM CE (CREAM CE < 1.6.3) the sudoers file was scratched at each yaim reconfiguration and filled with just the stuff needed for CREAM. This meant that local customizations were scratched. In the new CREAM CE (CREAM CE 1.6.3 released with gLite 3.2 Update 20) yaim:
    • Check if the installed version supports the include directive (this should be the case for SL5, while this shouldn't be the case for SL4)
    • Clean from /etc/sudoers the CREAM related stuff existing from a previous installation
    • If sudo supports include directives (this should be the case for SL5), it include the CREAM related stuff in /etc/sudoers.forcream and add in /etc/sudoers the include of /etc/sudoers.forcream
    • If sudo doesn't supports include directives (this should be the case for SL4), it include the CREAM related stuff in /etc/sudoers
to:
  • In the old CREAM CE (CREAM CE < 1.6.3) the sudoers file was scratched at each yaim reconfiguration and filled with just the stuff needed for CREAM. This meant that local customizations were scratched. In the new CREAM CE (CREAM CE 1.6.3) yaim:
    • checks if the installed sudo version supports the include directive (this should be the case for SL5, while this shouldn't be the case for SL4)
    • cleans from /etc/sudoers the CREAM related stuff existing from a previous installation
    • if sudo supports include directives (this should be the case for SL5), yaim sets the CREAM related stuff in /etc/sudoers.forcream and adds in /etc/sudoers the include of /etc/sudoers.forcream
    • If sudo doesn't supports include directives (this should be the case for SL4), yaim sets the CREAM related stuff in /etc/sudoers
Changed line 18 from:
  • To restore The previous version of the sudoers file (the one existing before the reconfiguration) which is saved in /etc/sudoers.bak_<date>_<time>
to:
  • To restore the previous version of the sudoers file (the one existing before the reconfiguration) which is saved in /etc/sudoers.bak_<date>_<time>
Deleted line 21:
It looks like there are in some cases a problem with the second item (the cleaning of /etc/sudoers). Still investigating when/how this happens
November 16, 2010, at 01:08 PM by 193.205.157.206 -
Changed lines 16-19 from:
For gLite 3.1, this means that the sudoers file could have some problems after each yaim reconfiguration
to:
For gLite 3.1, this means that the sudoers file could have some problems after each yaim reconfiguration.
Possible workarounds are:
  • To restore The previous version of the sudoers file (the one existing before the reconfiguration) which is saved in /etc/sudoers.bak_<date>_<time>
  • To do the yaim configuration starting with a sudoers file which doesn't contain anything related to CREAM
November 16, 2010, at 11:05 AM by 193.205.157.206 -
Changed line 14 from:
For gLite 3.2, when updating to CREAM CE 1.6.3 from previous versions this means that the sudoers file could have some problems after the yaim reconfiguration. When fixed, the problems won't happen anymore in following yaim reconfigurations
to:
For gLite 3.2, when updating to CREAM CE 1.6.3 from previous versions this means that the sudoers file could have some problems after the yaim reconfiguration. When the sudoers file is manually fixed, the problems won't happen anymore in following yaim reconfigurations
November 16, 2010, at 11:01 AM by 193.205.157.206 -
Changed lines 5-9 from:
  • In the old CREAM CE (CREAM CE < 1.6.3) the sudoers file was scratched at each yaim reconfiguration and filled with just the stuff needed for CREAM. This meant that local customizations were scratched. In the new CREAM CE (CREAM CE 1.6.3 released with gLite 3.2 Update 20) yaim is supposed:
    • to include the CREAM related stuff in /etc/sudoers.forcream
    • to clean from /etc/sudoers the CREAM related stuff existing from a previous installation
    • to add in /etc/sudoers the include of /etc/sudoers.forcream
to:
  • In the old CREAM CE (CREAM CE < 1.6.3) the sudoers file was scratched at each yaim reconfiguration and filled with just the stuff needed for CREAM. This meant that local customizations were scratched. In the new CREAM CE (CREAM CE 1.6.3 released with gLite 3.2 Update 20) yaim:
    • Check if the installed version supports the include directive (this should be the case for SL5, while this shouldn't be the case for SL4)
    • Clean from /etc/sudoers the CREAM related stuff existing from a previous installation
    • If sudo supports include directives (this should be the case for SL5), it include the CREAM related stuff in /etc/sudoers.forcream and add in /etc/sudoers the include of /etc/sudoers.forcream
    • If sudo doesn't supports include directives (this should be the case for SL4), it include the CREAM related stuff in /etc/sudoers
There is a problem with the cleaning part, which doesn't work properly if the name of the users don't include the name of the group: bug #75369
For gLite 3.2, when updating to CREAM CE 1.6.3 from previous versions this means that the sudoers file could have some problems after the yaim reconfiguration. When fixed, the problems won't happen anymore in following yaim reconfigurations
For gLite 3.1, this means that the sudoers file could have some problems after each yaim reconfiguration
November 14, 2010, at 12:18 AM by 82.52.177.162 -
Added lines 3-11:
  • In the old CREAM CE (CREAM CE < 1.6.3) the sudoers file was scratched at each yaim reconfiguration and filled with just the stuff needed for CREAM. This meant that local customizations were scratched. In the new CREAM CE (CREAM CE 1.6.3 released with gLite 3.2 Update 20) yaim is supposed:
    • to include the CREAM related stuff in /etc/sudoers.forcream
    • to clean from /etc/sudoers the CREAM related stuff existing from a previous installation
    • to add in /etc/sudoers the include of /etc/sudoers.forcream
It looks like there are in some cases a problem with the second item (the cleaning of /etc/sudoers). Still investigating when/how this happens
November 14, 2010, at 12:01 AM by 82.52.177.162 -
Added line 4:
  • Bugs #73224 and #73109 in yaim-core: the variable GLOBUS_TCP_PORT_RANGE could not be properly defined and therefore causing problems with gridftp, See the workaround specified in these bugs
November 11, 2010, at 10:16 AM by 193.206.247.185 -
Changed lines 5-18 from:
  • Bug #69320: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:
mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info
where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.
Do not move the directories named <subcluster> from /opt/glite/var/info.
to:
Changed lines 146-153 from:
to:
  • Bug #69320: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:
mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info
where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.
Do not move the directories named <subcluster> from /opt/glite/var/info.
November 11, 2010, at 10:13 AM by 193.206.247.185 -
Changed lines 4-8 from:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to choose a high value (e.g. 86400) for the alldone_interval attribute in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
  • Because of a non backward compatible change done in Torque (related with the -W option), the CREAM CE doesn't work with Torque v. >= 2.4). This will be addressed with CREAM CE 1.6.3
to:
Changed lines 17-20 from:
  • Bug #68225 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
There are problems if there are special characters (e.g. '-') in the pool account groups: a problem with the sudoer file is reported.
As a workaround edit the /etc/sudoers file simply replacing the special characters in the alias names with valid ones.
to:
Added lines 150-158:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to choose a high value (e.g. 86400) for the alldone_interval attribute in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart). Problem addressed with CREAM CE 1.6.3 released with gLite 3.2 Update 20.
  • Because of a non backward compatible change done in Torque (related with the -W option), the CREAM CE doesn't work with Torque v. >= 2.4). Problem addressed with CREAM CE 1.6.3 released with gLite 3.2 Update 20.
  • Bug #68225 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
There are problems if there are special characters (e.g. '-') in the pool account groups: a problem with the sudoer file is reported.
As a workaround edit the /etc/sudoers file simply replacing the special characters in the alias names with valid ones. Problem addressed with CREAM CE 1.6.3 released with gLite 3.2 Update 20.
November 04, 2010, at 01:35 PM by 193.205.157.206 -
Changed line 145 from:

[@

to:
[@
November 04, 2010, at 01:35 PM by 193.205.157.206 -
Added lines 142-149:
  • Bug #74807: there are problems if the mapping for a certain user is changed, and jobs refer to a delegationid created before the change.
Waiting for the fix, as workaround each delegationid created by that user before the mapping change should be manuallu removed, as shown in the following example.
use delegationdb;
delete from t_credential where dlg_id='cert12345678' and local_user='dteam002';
Added lines 151-152:
November 02, 2010, at 04:35 PM by 82.50.182.245 -
Added lines 140-142:
  • 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 export MALLOC_CHECK_=0 to /opt/glite/etc/blah.config should help
November 02, 2010, at 03:41 PM by 82.50.182.245 -
Added lines 136-139:
  • For jobs running on SL4 WNs, some env variables (GLITE_LOCATION LCG_LOCATION EDG_LOCATION GLOBUS_LOCATION) are not set.
The fix was provided for SL5 but not for SL4 (which is now frozen).
Site admins can deploy this rpm on the SL4 WNs to address this issue
October 21, 2010, at 03:16 PM by 193.205.157.206 -
Added lines 6-7:
  • Because of a non backward compatible change done in Torque (related with the -W option), the CREAM CE doesn't work with Torque v. >= 2.4). This will be addressed with CREAM CE 1.6.3
October 19, 2010, at 06:12 PM by 79.7.1.200 -
Changed line 127 from:
  • Don't use the '&" character in the CREAM_DB_USER and CREAM_DB_PASSWORD yaim variables
to:
  • Don't use special characters in the CREAM_DB_USER and CREAM_DB_PASSWORD yaim variables
October 15, 2010, at 09:30 PM by 82.52.183.155 -
Added lines 128-134:
  • 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:
LANG=en_US
in $CATALINA_HOME/conf/tomcat5.conf and then restart tomcat
October 14, 2010, at 12:16 PM by 193.205.157.206 -
Changed line 4 from:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to set to a high value (e.g. 36000, if jobs can't be queued for more than 10 hours) the alldone_interval attribute in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
to:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to choose a high value (e.g. 86400) for the alldone_interval attribute in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
September 16, 2010, at 03:45 PM by 193.205.157.206 -
Changed line 4 from:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to set to a high value (e.g. 36000) the alldone_interval attribute in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
to:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to set to a high value (e.g. 36000, if jobs can't be queued for more than 10 hours) the alldone_interval attribute in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
September 13, 2010, at 09:08 AM by 193.205.157.206 -
Changed line 4 from:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to set a higher value (e.g. 36000) for alldone_interval in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
to:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to set to a high value (e.g. 36000) the alldone_interval attribute in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
September 12, 2010, at 09:14 AM by 79.1.246.123 -
Changed line 4 from:
to:
  • Bug #70287, when using the new blah blparser, jobs queued for more than one hour, are considered "lost" (i.e. they are considered failed with "reason 999"). The workaround is to set a higher value (e.g. 36000) for alldone_interval in /opt/glite/etc/blah.config and then restart the blparser (/opt/glite/etc/init.d/glite-ce-blahparser restart)
August 20, 2010, at 09:16 AM by 82.52.177.101 -
Deleted lines 83-86:
  • Because of bug #58515 in voms-api-java, there are problems whenever the Email= field is present in the certificate of a VOMS server
Added lines 131-133:
  • Because of bug #58515 in voms-api-java, there are problems whenever the Email= field is present in the certificate of a VOMS server.
Fix provided with gLite 3.2 Update 17
August 19, 2010, at 07:20 PM by 82.51.31.125 -
Changed lines 84-86 from:
  • Bug #63714 in VOMS api java which doesn't support the critical extension Issuing Distribution Point. This affects the KEK CA. Waiting for the fix to be provided by the VOMS product team, the workaround is to replace /var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/vomsjapi.jar with this file and restart tomcat.
to:
Deleted lines 87-89:
Added lines 135-137:
  • Bug #63714 in VOMS api java which doesn't support the critical extension Issuing Distribution Point. This affects the KEK CA. Waiting for the fix to be provided by the VOMS product team, the workaround is to replace /var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/vomsjapi.jar with this file and restart tomcat.
Fix provided with gLite 3.2 Update 17
August 19, 2010, at 07:18 PM by 82.51.31.125 -
Changed lines 16-20 from:
  • Bug #68159 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
There are problems if there are special characters (e.g. '-') in the pool account users and/or groups.
As workaround replace the file $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar with the new jar file and restart tomcat.
to:
Added lines 140-144:
  • Bug #68159 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
There are problems if there are special characters (e.g. '-') in the pool account users and/or groups.
As workaround replace the file $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar with the new jar file and restart tomcat.
Fix provided with gLite 3.2 Update 17
August 19, 2010, at 07:17 PM by 82.51.31.125 -
Changed line 7 from:
  • Bug #69320->https://savannah.cern.ch/bugs/?69320]]: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
to:
  • Bug #69320: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
August 19, 2010, at 07:15 PM by 82.51.31.125 -
Changed lines 4-14 from:
  • There is a memory leak in util-java which can cause a OutOfMemory problem in the CREAM CE: see bug #69554
The workaround is:
  • Update the util-java rpm. take the new one from here
  • cp /opt/glite/share/java/glite-security-util-java.jar /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar
  • Restart tomcat
  • Because of bug #69545 asynchronous commands can be processed very slowly. The workaround is:
    • Replace /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file
    • Restart tomcat
to:
Added lines 142-153:
  • There is a memory leak in util-java which can cause a OutOfMemory problem in the CREAM CE: see bug #69554
The workaround is:
  • Update the util-java rpm. take the new one from here
  • cp /opt/glite/share/java/glite-security-util-java.jar /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar
  • Restart tomcat
Fix provided with gLite 3.2 Update 17
  • Because of bug #69545 asynchronous commands can be processed very slowly. The workaround is:
    • Replace /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file
    • Restart tomcat
Fix provided with gLite 3.2 Update 17
August 04, 2010, at 07:09 AM by 79.24.246.186 -
Changed line 24 from:
  • Bug #68159 and bug #68225 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
to:
  • Bug #68159 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
Changed lines 27-31 from:
If needed edit the /etc/sudoers file replacing the special characters in the alias names with valid ones.
to:
  • Bug #68225 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
There are problems if there are special characters (e.g. '-') in the pool account groups: a problem with the sudoer file is reported.
As a workaround edit the /etc/sudoers file simply replacing the special characters in the alias names with valid ones.
July 23, 2010, at 06:10 PM by 193.205.157.206 -
Changed line 27 from:
If needed edit the /etc/sudoers file replacing the special characters with valid ones.
to:
If needed edit the /etc/sudoers file replacing the special characters in the alias names with valid ones.
July 19, 2010, at 07:53 AM by 79.31.243.137 -
Changed line 17 from:
[@
to:
[@
Changed lines 21-22 from:

where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside. Do not move the directories named <subcluster> from /opt/glite/var/info.

to:
where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside.
Do not move the directories named <subcluster> from /opt/glite/var/info.
July 19, 2010, at 07:52 AM by 79.31.243.137 -
Added lines 13-22:
  • Bug #69320->https://savannah.cern.ch/bugs/?69320]]: due to a bug in yaim-core 4.0.12-1 in combination with lcg-info-dynamic-software 1.0.3-3, introduced in glite-CREAM since version 3.2.5-0, clean installations of glite-CREAM may fail to publish software tags. This is because yaim-core is no longer creating the directory /opt/edg/var/info/$VO, where $VO is the VOs supported by the CREAM CE. This is used by lcg-info-dynamic-software to publish software tags.
The workaround is to create these directories manually along with an empty .list file inside each for holding the tags. As the faulty yaim core does in fact create the directories, but in the wrong location, it is easiest to move the directories to the correct place:
mkdir -p /opt/edg/var/info
mv /opt/glite/var/info/<VO> /opt/edg/var/info

where <VO> is replaced by the name of each VO supported. The ownership and permissions will already be correct on the directories yaim has created, along with an empty .list file inside. Do not move the directories named <subcluster> from /opt/glite/var/info.

July 19, 2010, at 07:46 AM by 79.31.243.137 -
Deleted lines 18-25:
  • Bug #56762: since gLite 3.1 Update 56 (patch #3259) it is not possible to specify NodeNumber or CpuNumber in the JDL when JobType is Normal. Waiting for the patch fixing this problem , please apply the following workaround:
    • Replace $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-jdl-api-java.jar with this file
    • Restart tomcat
This problem doesn't affect the CREAM CE version for gLite 3.2/sl5
Fix provided with patch #3898
Added lines 135-141:
  • Bug #56762: since gLite 3.1 Update 56 (patch #3259) it is not possible to specify NodeNumber or CpuNumber in the JDL when JobType is Normal. Waiting for the patch fixing this problem , please apply the following workaround:
    • Replace $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-jdl-api-java.jar with this file
    • Restart tomcat
This problem doesn't affect the CREAM CE version for gLite 3.2/sl5
Fix provided with gLite 3.1.0 Update 65 (patch #3898)
July 14, 2010, at 04:17 PM by 82.52.181.117 -
Changed lines 10-11 from:
  • Because ofbug #69545 asyncronous commands can be processed very slowly. The workaround is:
    • Replace /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file
to:
  • Because of bug #69545 asynchronous commands can be processed very slowly. The workaround is:
    • Replace /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file
July 14, 2010, at 04:15 PM by 82.52.181.117 -
Changed lines 10-12 from:
to:
  • Because ofbug #69545 asyncronous commands can be processed very slowly. The workaround is:
    • Replace /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file
    • Restart tomcat
July 14, 2010, at 04:05 PM by 82.52.181.117 -
Changed line 7 from:
  • cp /opt/glite/share/java/glite-security-util-java.jar /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar@@
to:
  • cp /opt/glite/share/java/glite-security-util-java.jar /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar
July 14, 2010, at 04:05 PM by 82.52.181.117 -
Changed lines 6-7 from:
  • Overwrite /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar and /usr/share/tomcat5/server/lib/glite-security-util-java.jar with this file
to:
  • Update the util-java rpm. take the new one from here
  • cp /opt/glite/share/java/glite-security-util-java.jar /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar@@
July 14, 2010, at 12:08 PM by 79.6.45.144 -
Changed lines 6-7 from:
  • Overwrite /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar and /usr/share/tomcat5/server/lib/glite-security-util-java.jar with this file
  • Restart tomcat
to:
  • Overwrite /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar and /usr/share/tomcat5/server/lib/glite-security-util-java.jar with this file
  • Restart tomcat
July 14, 2010, at 12:05 PM by 79.6.45.144 -
Changed lines 5-6 from:

The workaround is:

  • Overwrite /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar and /usr/share/tomcat5/server/lib/glite-security-util-java.jar with
to:
The workaround is:
  • Overwrite /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar and /usr/share/tomcat5/server/lib/glite-security-util-java.jar with this file
July 14, 2010, at 12:01 PM by 79.6.45.144 -
Added lines 3-9:
  • There is a memory leak in util-java which can cause a OutOfMemory problem in the CREAM CE: see bug #69554

The workaround is:

  • Overwrite /usr/share/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-security-util-java.jar and /usr/share/tomcat5/server/lib/glite-security-util-java.jar with
  • Restart tomcat
June 07, 2010, at 03:41 PM by 193.205.157.206 -
Changed lines 9-28 from:
  • Bug #67302 in trustmanager affecting the CREAM CE 1.6 for gLite 3.2 (the one released with gLite 3.2 Update 12).
The bug affects the users of the following CAs:
/C=AU/O=APACGrid
/C=IL/O=IUCC
/C=CN/O=HEP
Fix provided with patch #4119 (in staged-rollout)
In the meantime the workaround is to modify the relevant /etc/grid-security/certificates/*.namespaces files:
/etc/grid-security/certificates/1e12d831.namespaces
/etc/grid-security/certificates/6fee79b0.namespaces
/etc/grid-security/certificates/ba2f39ca.namespaces
changing /emailAddress= into /Email=
to:
Added lines 133-146:
  • Bug #67302 in trustmanager affecting the CREAM CE 1.6 for gLite 3.2 (the one released with gLite 3.2 Update 12).
The bug affects the users of the following CAs:
/C=AU/O=APACGrid
/C=IL/O=IUCC
/C=CN/O=HEP
Fix provided with patch #4119 (released with gLite 3.2 Update 13)
June 01, 2010, at 11:21 PM by 95.232.47.170 -
Changed lines 4-5 from:
  • Bug #68159 in CREAM affecting CREAM CE 1.6.1
Replace the file $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar with the new jar file.
to:
  • Bug #68159 and bug #68225 in CREAM affecting CREAM CE 1.6.x (released first with gLite 3.2 update 12).
There are problems if there are special characters (e.g. '-') in the pool account users and/or groups.
As workaround replace the file $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar with the new jar file and restart tomcat.
If needed edit the /etc/sudoers file replacing the special characters with valid ones.
June 01, 2010, at 01:40 PM by 193.205.157.98 -
Changed line 5 from:
The following jar file must be saved into $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib
to:
Replace the file $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar with the new jar file.
June 01, 2010, at 01:33 PM by 193.205.157.98 -
Added lines 3-5:
  • Bug #68159 in CREAM affecting CREAM CE 1.6.1
The following jar file must be saved into $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib
May 31, 2010, at 08:19 AM by 151.82.151.1 -
Changed lines 13-14 from:
The workaround is to modify the relevant /etc/grid-security/certificates/*.namespaces files:
to:
Fix provided with patch #4119 (in staged-rollout)
In the meantime the workaround is to modify the relevant /etc/grid-security/certificates/*.namespaces files:
May 18, 2010, at 12:56 PM by 95.241.0.16 -
Changed line 21 from:

changing /emailAddress= into /Email=

to:
changing /emailAddress= into /Email=
May 18, 2010, at 12:56 PM by 95.241.0.16 -
Changed lines 13-21 from:
The workaround is to modify the relevant /etc/grid-security/certificates/*.namespaces files changing /emailAddress= into /Email=
to:
The workaround is to modify the relevant /etc/grid-security/certificates/*.namespaces files:
/etc/grid-security/certificates/1e12d831.namespaces
/etc/grid-security/certificates/6fee79b0.namespaces
/etc/grid-security/certificates/ba2f39ca.namespaces

changing /emailAddress= into /Email=

May 17, 2010, at 06:13 PM by 82.52.181.136 -
Changed lines 4-13 from:
to:
  • Bug #67302 in trustmanager affecting the CREAM CE 1.6 for gLite 3.2 (the one released with gLite 3.2 Update 12).
The bug affects the users of the following CAs:
/C=AU/O=APACGrid
/C=IL/O=IUCC
/C=CN/O=HEP
The workaround is to modify the relevant /etc/grid-security/certificates/*.namespaces files changing /emailAddress= into /Email=
May 03, 2010, at 10:57 PM by 82.48.225.18 -
Deleted lines 85-89:
  • Because of bug #17046 (in trustmanager) if there are CA changes, it is necessary to restart tomcat
Deleted lines 88-93:
Deleted line 90:
Deleted lines 99-103:
Added lines 129-130:
  • Because of bug #17046 (in trustmanager) if there are CA changes, it is necessary to restart tomcat
May 03, 2010, at 05:41 PM by 193.205.157.206 -
Deleted lines 216-217:

xxx

May 03, 2010, at 05:41 PM by 193.205.157.206 -
Changed lines 114-118 from:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported.
Fix provided with patch #3959, released with gLite 3.2.0 Update 12.
In the meantime the workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file and restart tomcat
to:
Added lines 211-216:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported.
Fix provided with patch #3959, released with gLite 3.2.0 Update 12.
In the meantime the workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file and restart tomcat
May 03, 2010, at 05:40 PM by 193.205.157.206 -
Changed lines 95-105 from:
  • Bug #45914 (in glexec) and in BLAH: sometimes glexec (used by CREAM/BLAH) can fail reporting something like:
gLExec has detected an input file change during the use of the file
CREAM CE patch #3959, released with gLite 3.2.0 Update 12, is not affected by this problem anymore
to:
Changed lines 111-117 from:
  • Bug #47804: for a LSF based CREAM CE, the yaim variable BATCH_CONF_DIR must be set to the directory where there is the lsf.conf. yaim-cream-ce assumes that in the same directory there is also the lsf.profile script, while this is not always the case. Waiting for the fix for this bug, the workaround is to edit /opt/glite/etc/blah.config (setting the proper path of the lsf.profile script), and restart tomcat
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
  • Bug #56518: The BLAH blparser doesn't automatically start after a reboot
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
to:
Added lines 199-212:
  • Bug #45914 (in glexec) and in BLAH: sometimes glexec (used by CREAM/BLAH) can fail reporting something like:
gLExec has detected an input file change during the use of the file
CREAM CE patch #3959, released with gLite 3.2.0 Update 12, is not affected by this problem anymore
  • Bug #47804: for a LSF based CREAM CE, the yaim variable BATCH_CONF_DIR must be set to the directory where there is the lsf.conf. yaim-cream-ce assumes that in the same directory there is also the lsf.profile script, while this is not always the case. Waiting for the fix for this bug, the workaround is to edit /opt/glite/etc/blah.config (setting the proper path of the lsf.profile script), and restart tomcat
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
  • Bug #56518: The BLAH blparser doesn't automatically start after a reboot
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
May 03, 2010, at 05:39 PM by 193.205.157.206 -
Changed lines 85-98 from:
  • Bug #47254: if the proxy used to talk with a CREAM based CE is shorter than 10 minutes, the following problem could be seen:
CREAM Register returned error "MethodName=[jobRegister] Timestamp=[Fri 20 Feb 2009 16:24:32] ErrorCode=[0] Description=[system error]
FaultCause=[cannot create the job's working directory! The problem seems to be related to glexec]"
Actually in these cases glexec is not to blame: the problem is instead in the proxy used by CREAM for this glexec operation
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
  • Old (expired) proxies delegated to a CREAM based CE are not deleted (bugs #33730 and #49497)
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
to:
Added lines 195-208:
  • Bug #47254: if the proxy used to talk with a CREAM based CE is shorter than 10 minutes, the following problem could be seen:
CREAM Register returned error "MethodName=[jobRegister] Timestamp=[Fri 20 Feb 2009 16:24:32] ErrorCode=[0] Description=[system error]
FaultCause=[cannot create the job's working directory! The problem seems to be related to glexec]"
Actually in these cases glexec is not to blame: the problem is instead in the proxy used by CREAM for this glexec operation
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
  • Old (expired) proxies delegated to a CREAM based CE are not deleted (bugs #33730 and #49497)
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
May 03, 2010, at 05:38 PM by 193.205.157.206 -
Deleted lines 5-6:
Changed lines 12-20 from:
  • Bug #61790: There can be problems if there are some "strange" characters in the subject DN. E.g. if there is a ":" in the subject DN, the sandbox directory has a name with ":", and this is a character not accepted by PBS.
Patch #3959, released with gLite 3.2.0 Update 12, provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char).
In the meantime the workaround is to replace:
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream.jar with this file
/var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-monitor.jar with this file
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar and /var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-common-java.jar with this file
and restart tomcat
to:
Deleted lines 73-74:
  • Bug #62893 : in some cases the JobWrapper running on the WN could not download in time the fresh proxy from the CREAM CE node. Fix provided with patch #3959, released with gLite 3.2.0 Update 12. In the meantime the workaround is to replace the CREAM jw template (following the instructions reported at: http://grid.pd.infn.it/cream/field.php?n=Main.HowToCustomizeTheCREAMJobWrapper) with this one.
Added line 76:
Changed lines 80-89 from:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651): fix provided with patch #3959, released with gLite 3.2.0 Update 12
As a workaround in the meantime it is suggested:
  • To create the index for the extra_table attribute (see bug #52876): not needed if you are already using gLite 3.1 Update 56
  • To increase the number of file descriptors (e.g. to 4096) for tomcat. You can do it editing /etc/security/limits.conf and adding:
tomcat           soft    nofile          4096
tomcat           hard    nofile          4096
to:
Added lines 185-206:
  • Bug #61790: There can be problems if there are some "strange" characters in the subject DN. E.g. if there is a ":" in the subject DN, the sandbox directory has a name with ":", and this is a character not accepted by PBS.
Patch #3959, released with gLite 3.2.0 Update 12, provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char).
In the meantime the workaround is to replace:
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream.jar with this file
/var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-monitor.jar with this file
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar and /var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-common-java.jar with this file
and restart tomcat
  • Bug #62893 : in some cases the JobWrapper running on the WN could not download in time the fresh proxy from the CREAM CE node. Fix provided with patch #3959, released with gLite 3.2.0 Update 12. In the meantime the workaround is to replace the CREAM jw template (following the instructions reported at: http://grid.pd.infn.it/cream/field.php?n=Main.HowToCustomizeTheCREAMJobWrapper) with this one.
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651): fix provided with patch #3959, released with gLite 3.2.0 Update 12
As a workaround in the meantime it is suggested:
  • To create the index for the extra_table attribute (see bug #52876): not needed if you are already using gLite 3.1 Update 56
  • To increase the number of file descriptors (e.g. to 4096) for tomcat. You can do it editing /etc/security/limits.conf and adding:
tomcat           soft    nofile          4096
tomcat           hard    nofile          4096
May 03, 2010, at 05:35 PM by 193.205.157.206 -
Changed lines 5-20 from:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default). With CREAM CE 1.6 (patch #3959, released with gLite 3.2.0 Update 12) the new blparser can instead be used (and it is the default option)
  • Bug #58941 and #61493 in some cases glexec could map to a different account than the one mapped by gridftpd, therefore causing problems.
Because of this problem it is not possible to have both of the following in the grid-mapfile:
  • a mapping of some role/group to a static account;
  • a wildcard to map unrecognized roles/groups to pool accounts
Fix provided with patch #3959, released with gLite 3.2.0 Update 12. In the meantime it is possible to apply the following workaround after having configured via yaim:
  • echo "user_identity_switch_by = lcmaps" >> /opt/glite/etc/glexec.conf
  • wget --no-check-certificate https://savannah.cern.ch/bugs/download.php?file_id=11374 -O lcmaps-glexec.db
  • cp -p /opt/glite/etc/lcmaps/lcmaps-suexec.db opt/glite/etc/lcmaps/lcmaps-suexec.db.old
  • cat lcmaps-glexec.db > /opt/glite/etc/lcmaps/lcmaps-suexec.db
  • Only for glite 3.2/sl5_x86_64: sed -i -e 's|/opt/glite/lib/|/opt/glite/lib64/|' /opt/glite/etc/lcmaps/lcmaps-suexec.db
to:
Added lines 189-204:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default). With CREAM CE 1.6 (patch #3959, released with gLite 3.2.0 Update 12) the new blparser can instead be used (and it is the default option)
  • Bug #58941 and #61493 in some cases glexec could map to a different account than the one mapped by gridftpd, therefore causing problems.
Because of this problem it is not possible to have both of the following in the grid-mapfile:
  • a mapping of some role/group to a static account;
  • a wildcard to map unrecognized roles/groups to pool accounts
Fix provided with patch #3959, released with gLite 3.2.0 Update 12. In the meantime it is possible to apply the following workaround after having configured via yaim:
  • echo "user_identity_switch_by = lcmaps" >> /opt/glite/etc/glexec.conf
  • wget --no-check-certificate https://savannah.cern.ch/bugs/download.php?file_id=11374 -O lcmaps-glexec.db
  • cp -p /opt/glite/etc/lcmaps/lcmaps-suexec.db opt/glite/etc/lcmaps/lcmaps-suexec.db.old
  • cat lcmaps-glexec.db > /opt/glite/etc/lcmaps/lcmaps-suexec.db
  • Only for glite 3.2/sl5_x86_64: sed -i -e 's|/opt/glite/lib/|/opt/glite/lib64/|' /opt/glite/etc/lcmaps/lcmaps-suexec.db

xxx

April 30, 2010, at 02:18 PM by 193.205.157.206 -
Changed lines 5-7 from:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default). With CREAM CE 1.6 (patch #3959, already certified but not yet in production) the new blparser can instead be used (and it is the default option)
to:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default). With CREAM CE 1.6 (patch #3959, released with gLite 3.2.0 Update 12) the new blparser can instead be used (and it is the default option)
Changed lines 13-14 from:
Fix provided with patch #3959. In the meantime it is possible to apply the following workaround after having configured via yaim:
to:
Fix provided with patch #3959, released with gLite 3.2.0 Update 12. In the meantime it is possible to apply the following workaround after having configured via yaim:
Changed line 28 from:
Patch #3959 provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char).
to:
Patch #3959, released with gLite 3.2.0 Update 12, provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char).
Changed lines 97-98 from:
  • Bug #62893 : in some cases the JobWrapper running on the WN could not download in time the fresh proxy from the CREAM CE node. Fix provided with patch #3959. In the meantime the workaround is to replace the CREAM jw template (following the instructions reported at: http://grid.pd.infn.it/cream/field.php?n=Main.HowToCustomizeTheCREAMJobWrapper) with this one.
to:
  • Bug #62893 : in some cases the JobWrapper running on the WN could not download in time the fresh proxy from the CREAM CE node. Fix provided with patch #3959, released with gLite 3.2.0 Update 12. In the meantime the workaround is to replace the CREAM jw template (following the instructions reported at: http://grid.pd.infn.it/cream/field.php?n=Main.HowToCustomizeTheCREAMJobWrapper) with this one.
Changed line 104 from:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651): fix provided with patch #3959
to:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651): fix provided with patch #3959, released with gLite 3.2.0 Update 12
Changed lines 124-126 from:
Fix provided with patch #3959
to:
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
Changed lines 128-129 from:
Fix provided with patch #3959
to:
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
Changed lines 143-148 from:
CREAM CE patch #3959 will not be affected by this problem anymore
to:
CREAM CE patch #3959, released with gLite 3.2.0 Update 12, is not affected by this problem anymore
Changed lines 161-162 from:
Fix provided with patch #3959
to:
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
Changed lines 164-166 from:
Fix provided with patch #3959
to:
Fix provided with patch #3959, released with gLite 3.2.0 Update 12
Changed line 168 from:
Fix provided with patch #3959.
to:
Fix provided with patch #3959, released with gLite 3.2.0 Update 12.
April 22, 2010, at 04:38 PM by 193.205.157.206 -
Changed line 187 from:
{@
to:
[@
April 22, 2010, at 04:37 PM by 193.205.157.206 -
Added lines 170-195:
  • On SL(c)4 when kerberos is used, the /usr/bin/id executable can be affected by a problem: the exit code could be different than 0, as in the following example:
# su dteam001 -
[dteam001@cert-08 glexec]$ id
uid=1651(dteam001) gid=2688(dteam) groups=2688(dteam),1090601808
[dteam001@cert-08 glexec]$ echo $?
1
Because of this problem, job submission could fail reporting Authorization error: System error reading local user information
In this case the following workaround can be applied:
  • Create (and chmod +x) a script (e.g. /opt/glite/etc/glite-ce-cream/id-wrapper.sh) which issues the id command, but returns 0 as exit code, e.g.:
{@
  1. !/bin/sh

/usr/bin/id exit 0 @]

  • Replace in /opt/glite/etc/glite-ce-cream/cream-config.xml and in /opt/glite/etc/lcas/lcas-glexec.db, the occurence of /usr/bin/id with the pathname of this script.
  • Restart tomcat
April 22, 2010, at 04:28 PM by 193.205.157.206 -
Changed lines 13-14 from:
Fix provided with patch #3959. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
to:
Fix provided with patch #3959. In the meantime it is possible to apply the following workaround after having configured via yaim:
Changed lines 25-26 from:
to:
Fix provided with patch #3898
Deleted lines 123-126:
Fix provided with patch #3979
  • Old (expired) proxies delegated to a CREAM based CE are not deleted (bugs #33730 and #49497)
Added lines 126-129:
  • Old (expired) proxies delegated to a CREAM based CE are not deleted (bugs #33730 and #49497)
Fix provided with patch #3959
Added line 165:
March 30, 2010, at 07:52 AM by 151.81.10.161 -
Changed lines 5-7 from:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default). With CREAM CE 1.6 (patch #3179, already certified but not yet in production) the new blparser can instead be used (and it is the default option)
to:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default). With CREAM CE 1.6 (patch #3959, already certified but not yet in production) the new blparser can instead be used (and it is the default option)
Changed lines 13-14 from:
Fix provided with patch #3179. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
to:
Fix provided with patch #3959. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
Changed line 27 from:
Patch #3179 provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char).
to:
Patch #3959 provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char).
Changed lines 96-97 from:
  • Bug #62893 : in some cases the JobWrapper running on the WN could not download in time the fresh proxy from the CREAM CE node. Fix provided with patch #3179. In the meantime the workaround is to replace the CREAM jw template (following the instructions reported at: http://grid.pd.infn.it/cream/field.php?n=Main.HowToCustomizeTheCREAMJobWrapper) with this one.
to:
  • Bug #62893 : in some cases the JobWrapper running on the WN could not download in time the fresh proxy from the CREAM CE node. Fix provided with patch #3959. In the meantime the workaround is to replace the CREAM jw template (following the instructions reported at: http://grid.pd.infn.it/cream/field.php?n=Main.HowToCustomizeTheCREAMJobWrapper) with this one.
Changed line 103 from:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651): fix provided with patch #3179
to:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651): fix provided with patch #3959
Changed lines 123-125 from:
Fix provided with patch #3179
to:
Fix provided with patch #3979
Changed lines 127-128 from:
Fix provided with patch #3179
to:
Fix provided with patch #3959
Changed lines 142-147 from:
CREAM CE patch #3179 will not be affected by this problem anymore
to:
CREAM CE patch #3959 will not be affected by this problem anymore
Changed lines 160-161 from:
Fix provided with patch #3179
to:
Fix provided with patch #3959
Changed lines 163-164 from:
Fix provided with patch #3179
to:
Fix provided with patch #3959
Changed line 166 from:
Fix provided with patch #3179.
to:
Fix provided with patch #3959.
March 24, 2010, at 09:25 AM by 192.16.186.5 -
Changed line 16 from:
  • wget -nd https://savannah.cern.ch/bugs/download.php?file_id=11374 -O lcmaps-glexec.db
to:
  • wget --no-check-certificate https://savannah.cern.ch/bugs/download.php?file_id=11374 -O lcmaps-glexec.db
March 24, 2010, at 09:23 AM by 192.16.186.5 -
Changed line 16 from:
  • wwget -nd https://savannah.cern.ch/bugs/download.php?file_id=11374 -O lcmaps-glexec.db
to:
  • wget -nd https://savannah.cern.ch/bugs/download.php?file_id=11374 -O lcmaps-glexec.db
March 24, 2010, at 09:23 AM by 192.16.186.5 -
Changed line 16 from:
  • wget -m -nd -nH 'https://savannah.cern~db?file_id=11374' -O lcmaps-glexec.db
to:
  • wwget -nd https://savannah.cern.ch/bugs/download.php?file_id=11374 -O lcmaps-glexec.db
March 18, 2010, at 11:50 AM by 193.205.157.206 -
Changed lines 5-7 from:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default)
to:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default). With CREAM CE 1.6 (patch #3179, already certified but not yet in production) the new blparser can instead be used (and it is the default option)
Added lines 95-96:
  • Bug #62893 : in some cases the JobWrapper running on the WN could not download in time the fresh proxy from the CREAM CE node. Fix provided with patch #3179. In the meantime the workaround is to replace the CREAM jw template (following the instructions reported at: http://grid.pd.infn.it/cream/field.php?n=Main.HowToCustomizeTheCREAMJobWrapper) with this one.
March 03, 2010, at 10:38 PM by 79.31.243.13 -
Added lines 94-96:
  • Bug #63714 in VOMS api java which doesn't support the critical extension Issuing Distribution Point. This affects the KEK CA. Waiting for the fix to be provided by the VOMS product team, the workaround is to replace /var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/vomsjapi.jar with this file and restart tomcat.
March 01, 2010, at 07:27 PM by 82.52.178.101 -
Deleted lines 32-34:
  • Bug #63386 There are problems with certificates issued by the Romanian CA, which doesn't respect the RFC. The workaround is to replace /var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/vomsjapi.jar with this file and restart tomcat
February 23, 2010, at 02:26 PM by 193.205.157.206 -
Added lines 33-36:
  • Bug #63386 There are problems with certificates issued by the Romanian CA, which doesn't respect the RFC. The workaround is to replace /var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/vomsjapi.jar with this file and restart tomcat
February 12, 2010, at 11:23 AM by 79.17.245.33 -
Changed line 32 from:
to:
and restart tomcat
February 12, 2010, at 11:23 AM by 79.17.245.33 -
Changed lines 30-31 from:
/var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-monitor.jar with
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar and /var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-common-java.jar with
to:
/var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-monitor.jar with this file
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar and /var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-common-java.jar with this file
February 12, 2010, at 11:21 AM by 79.17.245.33 -
Changed lines 26-27 from:
  • Bug #61790: There could be problems if there are some "strange" characters in the subject DN. E.g. if there is a ":" in the subject DN, the sandbox directory has a name with ":", and this is a character not accepted by PBS.
Patch #3179 provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char.
to:
  • Bug #61790: There can be problems if there are some "strange" characters in the subject DN. E.g. if there is a ":" in the subject DN, the sandbox directory has a name with ":", and this is a character not accepted by PBS.
Patch #3179 provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char).
Changed line 29 from:
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream.jar with
to:
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream.jar with this file
February 12, 2010, at 11:17 AM by 79.17.245.33 -
Added lines 25-31:
  • Bug #61790: There could be problems if there are some "strange" characters in the subject DN. E.g. if there is a ":" in the subject DN, the sandbox directory has a name with ":", and this is a character not accepted by PBS.
Patch #3179 provides a fix for this problem (the sandbox dir will have only alpha-numeric chars + the '_' char.
In the meantime the workaround is to replace:
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-cream.jar with
/var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-monitor.jar with
/var/lib/tomcat5/webapps/ce-cream/WEB-INF/lib/glite-ce-common-java.jar and /var/lib/tomcat5/webapps/ce-monitor/WEB-INF/lib/glite-ce-common-java.jar with
February 03, 2010, at 10:53 PM by 82.54.246.102 -
Changed line 157 from:
  • Don't use the '&" in the CREAM_DB_USER and CREAM_DB_PASSWORD yaim variables
to:
  • Don't use the '&" character in the CREAM_DB_USER and CREAM_DB_PASSWORD yaim variables
February 03, 2010, at 10:52 PM by 82.54.246.102 -
Added line 157:
  • Don't use the '&" in the CREAM_DB_USER and CREAM_DB_PASSWORD yaim variables
February 02, 2010, at 11:18 PM by 79.7.1.215 -
Changed lines 13-14 from:
Fix provided with patch #3209. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
to:
Fix provided with patch #3179. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
Changed lines 147-148 from:
Fix provided with patch #3209
to:
Fix provided with patch #3179
Changed line 150 from:
Fix provided with patch #3209
to:
Fix provided with patch #3179
January 30, 2010, at 02:00 PM by 82.51.31.218 -
Changed line 27 from:
  • 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.
to:
  • GGUS ticket #55015: 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.
January 27, 2010, at 09:14 AM by 151.81.136.242 -
Added line 85:
(Thanks to Marios Chatziangelou and Dennis van Dok for having provided the possible workaround)
January 27, 2010, at 09:11 AM by 151.81.136.242 -
Added line 39:
Changed lines 52-54 from:
[@

[root@lcg-ce]# cat <<EOF>> /etc/cron.d/diagnose-for-cream@@

to:
[@

[root@lcg-ce]# cat <<EOF>> /etc/cron.d/diagnose-for-cream

Changed line 60 from:
The interval defined at the /etc/cron.d/diagnose-for-cream file, has to be set by the experts. Just an example has been provided here
to:
The interval defined at the /etc/cron.d/diagnose-for-cream file, has to be set by the experts. Just an example has been provided here
Changed line 63 from:
[@
to:
[@
Changed line 73 from:
{@
to:
[@
Changed line 79 from:
[@
to:
[@
Deleted lines 83-85:

PS:

January 27, 2010, at 09:09 AM by 151.81.136.242 -
Added lines 25-86:
  • 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.
A common scenario/example when this can happen:
  • The maui server is a 32bit binary deployed on a 32bit LCG-CE
  • The 64bit maui client is deployed on a 64bit CREAM-CE
From the CREAM-CE node perform:
[root@cream-ce]# diagnose –g
If you see:
ERROR:    lost connection to server
ERROR:    cannot request service (status)
you are affected by the problem.
A possible workaround is the following:
  • At the LCG-CE:
    • Create a cron file to dump the `diagnose -g` output to a file
[root@lcg-ce]# cat <<EOF>> /etc/cron.d/diagnose-for-cream@@

> */5 * * * * root  /usr/bin/diagnose –g > /export/dir/to/cream-ce/diagnose.out

> EOF
The interval defined at the /etc/cron.d/diagnose-for-cream file, has to be set by the experts. Just an example has been provided here
  • Export over NFS the directory where the file is located
[root@lcg-ce]# cat /etc/exports

/export/dir/to/cream-ce            cream-ce(rw,map_identity,no_root_squash,sync)
  • At the CREAM-CE:
    • Include/mount the remote directory to a local one
{@

[root@cream-ce]# cat /etc/fstab | grep diagnose lcg-ce: /export/dir/to/cream-ce /import/dir/to/cream-ce nfs defaults,bg 0 0 @]

  • Feed the lcg-info-dynamic-scheduler with the diagnose output file.
[root@cream-ce]# cat /opt/glite/etc/lcg-info-dynamic-scheduler.conf|grep vomaxjobs-maui

vo_max_jobs_cmd: /opt/lcg/libexec/vomaxjobs-maui -h lcg-ce –infile /import/dir/to/cream-ce/diagnose-for-cream

PS:

January 26, 2010, at 05:07 PM by 193.205.157.206 -
Changed lines 49-50 from:
to:
Fix provided with patch #3179
Changed lines 53-54 from:
to:
Fix provided with patch #3179
Changed lines 86-87 from:
to:
Fix provided with patch #3209
Changed lines 89-90 from:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file and restart tomcat
to:
Fix provided with patch #3209
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported.
Fix provided with patch #3179.
In the meantime the workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file and restart tomcat
January 26, 2010, at 05:00 PM by 193.205.157.206 -
Changed line 8 from:
  • Bug #58941: in some cases (in particular when the mapping is to static accounts) glexec could map to a different account than the one mapped by gridftpd, therefore causing problems.
to:
  • Bug #58941 and #61493 in some cases glexec could map to a different account than the one mapped by gridftpd, therefore causing problems.
January 26, 2010, at 05:00 PM by 193.205.157.206 -
Changed line 9 from:

Because of this problem it is not possible to have both of the following in the grid-mapfile:

to:
Because of this problem it is not possible to have both of the following in the grid-mapfile:
January 26, 2010, at 04:59 PM by 193.205.157.206 -
Changed lines 8-13 from:
  • Bug #58941: in some cases (in particular when the mapping is to static accounts) glexec could map to a different account than the one mapped by gridftpd, therefore causing problems, Fix provided with patch #3209. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
to:
  • Bug #58941: in some cases (in particular when the mapping is to static accounts) glexec could map to a different account than the one mapped by gridftpd, therefore causing problems.

Because of this problem it is not possible to have both of the following in the grid-mapfile:

  • a mapping of some role/group to a static account;
  • a wildcard to map unrecognized roles/groups to pool accounts
Fix provided with patch #3209. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
January 11, 2010, at 10:27 PM by 82.50.177.157 -
Changed lines 23-32 from:
  • Because of bug #57141, there are problems to properly configure gLite 3.1 CREAM (32-bit) on a 64-bit node. Fix provided with patch #3438. In the meantime the workaround is to is to create a pre-configuration function in /opt/glite/yaim/functions/pre/config_cream_glexec:
config_cream_glexec_pre()
{
    # hack to get 32-bit LCAS/LCMAPS modules on 64-bit CREAM host
    export OS_ARCH=32BIT
}
to:
Added lines 89-91:
  • Because of bug #57141, there are problems to properly configure gLite 3.1 CREAM (32-bit) on a 64-bit node. Fix provided with patch #3438.
Deleted line 92:
January 09, 2010, at 10:51 PM by 82.48.233.105 -
Added lines 6-14:
  • Bug #58941: in some cases (in particular when the mapping is to static accounts) glexec could map to a different account than the one mapped by gridftpd, therefore causing problems, Fix provided with patch #3209. In the meantime it is possible to apply the following workaround after having confiugured via yaim:
    • echo "user_identity_switch_by = lcmaps" >> /opt/glite/etc/glexec.conf
    • wget -m -nd -nH 'https://savannah.cern~db?file_id=11374' -O lcmaps-glexec.db
    • cp -p /opt/glite/etc/lcmaps/lcmaps-suexec.db opt/glite/etc/lcmaps/lcmaps-suexec.db.old
    • cat lcmaps-glexec.db > /opt/glite/etc/lcmaps/lcmaps-suexec.db
    • Only for glite 3.2/sl5_x86_64: sed -i -e 's|/opt/glite/lib/|/opt/glite/lib64/|' /opt/glite/etc/lcmaps/lcmaps-suexec.db
January 07, 2010, at 03:41 PM by 193.205.157.206 -
Changed line 7 from:
  • Bug #56762: with gLite 3.1 Update 56 (patch #3259) it is not possible to specify NodeNumber or CpuNumber in the JDL when JobType is Normal. Waiting for the patch fixing this problem , please apply the following workaround:
to:
  • Bug #56762: since gLite 3.1 Update 56 (patch #3259) it is not possible to specify NodeNumber or CpuNumber in the JDL when JobType is Normal. Waiting for the patch fixing this problem , please apply the following workaround:
Added line 10:
This problem doesn't affect the CREAM CE version for gLite 3.2/sl5
November 18, 2009, at 02:14 PM by 193.205.157.206 -
Changed line 83 from:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file and restart tomcat
to:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file and restart tomcat
November 18, 2009, at 02:13 PM by 193.205.157.206 -
Changed line 83 from:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with [[this file->http://grid.pd.infn.itvar//crea/Misc/glite-ce-cream-api-java-common.jar] and restart tomcat
to:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file and restart tomcat
November 18, 2009, at 02:12 PM by 193.205.157.206 -
Changed line 83 from:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file? and restart tomcat
to:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with [[this file->http://grid.pd.infn.itvar//crea/Misc/glite-ce-cream-api-java-common.jar] and restart tomcat
November 18, 2009, at 02:10 PM by 193.205.157.206 -
Changed line 83 from:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported
to:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported. The workaround is to replace /var/lib/tomcat5/webapps//ce-cream/WEB-INF/lib/glite-ce-cream-api-java-common.jar with this file? and restart tomcat
November 10, 2009, at 01:34 PM by 151.82.162.48 -
Added line 11:
  • Because of bug #58515 in voms-api-java, there are problems whenever the Email= field is present in the certificate of a VOMS server
November 09, 2009, at 06:41 PM by 82.52.181.85 -
Changed lines 12-13 from:
  • Because of bug #57141, there are problems to properly configure gLite 3.1 CREAM (32-bit) on a 64-bit node. The workaround is to is to create a pre-configuration function in /opt/glite/yaim/functions/pre/config_cream_glexec:
to:
  • Because of bug #57141, there are problems to properly configure gLite 3.1 CREAM (32-bit) on a 64-bit node. Fix provided with patch #3438. In the meantime the workaround is to is to create a pre-configuration function in /opt/glite/yaim/functions/pre/config_cream_glexec:
Changed lines 55-56 from:
  • Bug #45914 (in glexec): sometimes glexec (used by CREAM/BLAH) can fail reporting something like:
to:
  • Bug #45914 (in glexec) and in BLAH: sometimes glexec (used by CREAM/BLAH) can fail reporting something like:
Added lines 59-60:
CREAM CE patch #3179 will not be affected by this problem anymore
October 30, 2009, at 12:47 PM by 193.205.157.206 -
Changed lines 55-63 from:
  • Bug #45914 (in glexec): sometimes glexec (used by CREAM/BLAH) can fail reporting in syslog something like:
Dec 18 17:44:35 cream-32 glexec[18612]: File
'/opt/glite/var/cream/user_proxy/C_
IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Alessio_Gianelle_dteam_Role_NULL_Capability_NULL/https3A2F2Fdevel152Ecnaf2Einfn2Eit3A90002FGOWAw6pOslnknloKZj12DdA
_deleg.proxy.lmt' has changed during opening.
Dec 18 17:44:35 cream-32 glexec[18612]: Error in LCAS/LCMAPS, rc = 120
to:
  • Bug #45914 (in glexec): sometimes glexec (used by CREAM/BLAH) can fail reporting something like:
gLExec has detected an input file change during the use of the file
October 16, 2009, at 10:50 PM by 82.54.226.230 -
Changed line 149 from:
Fix provided with patch #3084
to:
Fix provided with gLite 3.1 Update 54.
October 16, 2009, at 10:48 PM by 82.54.226.230 -
Changed line 79 from:
The problem has been fixed in gLite 3.1, so it is relevant for direct submissions done by a gLite 3.1 UI and by submissions through WMS for a gLite 3.1 WMS
to:
The problem has been fixed in gLite 3.2, so it is relevant for direct submissions done by a gLite 3.1 UI and by submissions through WMS for a gLite 3.1 WMS
October 16, 2009, at 10:47 PM by 82.54.226.230 -
Changed lines 79-80 from:
to:
The problem has been fixed in gLite 3.1, so it is relevant for direct submissions done by a gLite 3.1 UI and by submissions through WMS for a gLite 3.1 WMS
Added line 83:
Changed line 86 from:
  • Bug #52942: if a ISB/OSB file transfer fails, the failure reason is not properly reported
to:
  • Bug #52942: if a ISB/OSB file transfer done by the CREAM job wrapper fails, the failure reason is not properly reported
October 16, 2009, at 10:44 PM by 82.54.226.230 -
Changed lines 14-15 from:

[@

to:
[@
October 16, 2009, at 10:44 PM by 82.54.226.230 -
Added lines 11-21:
  • Because of bug #57141, there are problems to properly configure gLite 3.1 CREAM (32-bit) on a 64-bit node. The workaround is to is to create a pre-configuration function in /opt/glite/yaim/functions/pre/config_cream_glexec:
config_cream_glexec_pre()
{
    # hack to get 32-bit LCAS/LCMAPS modules on 64-bit CREAM host
    export OS_ARCH=32BIT
}
October 08, 2009, at 10:47 PM by 82.50.179.241 -
Added lines 6-10:
  • Bug #56762: with gLite 3.1 Update 56 (patch #3259) it is not possible to specify NodeNumber or CpuNumber in the JDL when JobType is Normal. Waiting for the patch fixing this problem , please apply the following workaround:
    • Replace $CATALINA_HOME/webapps/ce-cream/WEB-INF/lib/glite-jdl-api-java.jar with this file
    • Restart tomcat
October 07, 2009, at 07:36 PM by 82.52.182.198 -
Added lines 16-17:
  • RFC proxies are not supported yet. It is possible to submit to a CREAM CE using a RFC proxy, but the delegated proxy is not usable because of this bug in the delegation code.
October 07, 2009, at 09:56 AM by 82.48.229.216 -
Changed line 5 from:
  • Because of some serious problems with the new blparser (in particular bug #55438, it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default)
to:
  • Because of some serious problems with the new blparser (in particular bug #55438), it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default)
October 07, 2009, at 09:56 AM by 82.48.229.216 -
Added lines 4-5:
  • Because of some serious problems with the new blparser (in particular bug #55438, it is suggested to keep using the old parser (i.e.: BLPARSER_WITH_UPDATER_NOTIFIER=false, which is the default)
October 06, 2009, at 11:26 PM by 82.54.225.102 -
October 06, 2009, at 11:23 PM by 82.52.177.243 -
Added line 74:
October 06, 2009, at 11:22 PM by 82.52.177.243 -
Changed lines 4-5 from:
  • Bug #48083: if the mapping of a certain user changes, that user could not be able to submit jobs anymore (the error message will be a generic glexec error in the creation of the sandbox dir). Fix provided with path #2666/#3259. Waiting for the path, you have to remove/chown the user sandbox dir (in /opt/glite/var/cream_sandbox...).
to:
Changed line 7 from:
  • To create the index for the extra_table attribute (see below bug #52876): not needed if you are already using patch #2666/#3259
to:
  • To create the index for the extra_table attribute (see bug #52876): not needed if you are already using gLite 3.1 Update 56
Changed lines 15-19 from:
  • On glite 3.1 (which is supported just for sl4_ia32), BLAH and the blparser don't work on 64bit machines: fix provided with patch #3259
  • Bug #52876:The extra_attribute table in the CREAM DB has no keys/indexes defined. This results in performance problems for some operations
Waiting for the official fix (released with patch #2666/#3259), it is suggested to create the index using the following mysql command
to:
  • Bug #47254: if the proxy used to talk with a CREAM based CE is shorter than 10 minutes, the following problem could be seen:
Changed lines 18-19 from:

mysql --password=<passwd> -D creamdb -u root -e 'ALTER TABLE extra_attribute ADD CONSTRAINT fk_extra_attribute_jobId_job_id FOREIGN KEY (jobId) REFERENCES job (id) ON UPDATE NO ACTION ON DELETE NO ACTION; CREATE INDEX commandGroupId_Idx ON JOB_MANAGEMENT (commandGroupId);'

to:

CREAM Register returned error "MethodName=[jobRegister] Timestamp=[Fri 20 Feb 2009 16:24:32] ErrorCode=[0] Description=[system error] FaultCause=[cannot create the job's working directory! The problem seems to be related to glexec]"

Deleted lines 21-34:
  • Because of bug #44924, if the CREAM jobwrapper fails to download the proxy from the CREAM CE node, after 5 attempts it gives up and cancels the job with "proxy expired", even if the proxy is still valid. The recent changes in yaim-core (which introduced a limit on the number of concurrent gridftp connections), can trigger this problem. For the time being the workaround is to remove /opt/globus/etc/gridftp.conf from the CREAM CE and restart the gridftpd: fix provided with patch #2666/#3259
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitly or by the automatic purger) when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830: fix provided with patch #2666/#3259
  • Bug #47254: if the proxy used to talk with a CREAM based CE is shorter than 10 minutes, the following problem could be seen:
CREAM Register returned error "MethodName=[jobRegister] Timestamp=[Fri 20 Feb 2009 16:24:32] ErrorCode=[0] Description=[system error]
FaultCause=[cannot create the job's working directory! The problem seems to be related to glexec]"
Deleted lines 27-29:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is however managed by the yaim-cream-ce conf procedure. With patch #2666/#3259 VOMS server certificates are not needed anymore
Changed lines 48-53 from:
  • Bug #43830: There are problems if there are more than 32000 active jobs for a given user: fix provided with patch #2666/#3259
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed: fix provided with patch #2666/#3259
to:
Added lines 69-85:
  • Bug #43830: There are problems if there are more than 32000 active jobs for a given user: fix provided with gLite 3.1 Update 56
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed: fix provided with gLite 3.1 Update 56
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is however managed by the yaim-cream-ce conf procedure. With gLite 3.1 Update 56 VOMS server certificates are not needed anymore
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitly or by the automatic purger) when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830: fix provided with gLite 3.1 Update 56
  • On glite 3.1 (which is supported just for sl4_ia32), BLAH and the blparser don't work on 64bit machines: fix provided with gLite 3.1 update 56
  • Bug #52876:The extra_attribute table in the CREAM DB has no keys/indexes defined. This results in performance problems for some operations. Fix provided with gLite 3.1 Update 56
  • Because of bug #44924, if the CREAM jobwrapper fails to download the proxy from the CREAM CE node, after 5 attempts it gives up and cancels the job with "proxy expired", even if the proxy is still valid. The recent changes in yaim-core (which introduced a limit on the number of concurrent gridftp connections), can trigger this problem. For the time being the workaround is to remove /opt/globus/etc/gridftp.conf from the CREAM CE and restart the gridftpd: fix provided with gLite 3.1 Update 56
  • Bug #48083: if the mapping of a certain user changes, that user could not be able to submit jobs anymore (the error message will be a generic glexec error in the creation of the sandbox dir). Fix provided with gLite 3.1 Update 56
October 06, 2009, at 12:59 PM by 193.205.157.206 -
Added lines 87-88:
  • Bug #52942: if a ISB/OSB file transfer fails, the failure reason is not properly reported
October 06, 2009, at 12:55 PM by 193.205.157.206 -
Changed lines 4-5 from:
  • Bug #48083: if the mapping of a certain user changes, that user could not be able to submit jobs anymore (the error message will be a generic glexec error in the creation of the sandbox dir). Fix provided with path #2666/#3259. Waiting for the path, you have to remove/chown the

user sandbox dir (in /opt/glite/var/cream_sandbox...).

to:
  • Bug #48083: if the mapping of a certain user changes, that user could not be able to submit jobs anymore (the error message will be a generic glexec error in the creation of the sandbox dir). Fix provided with path #2666/#3259. Waiting for the path, you have to remove/chown the user sandbox dir (in /opt/glite/var/cream_sandbox...).
October 06, 2009, at 12:55 PM by 193.205.157.206 -
Added lines 3-5:
  • Bug #48083: if the mapping of a certain user changes, that user could not be able to submit jobs anymore (the error message will be a generic glexec error in the creation of the sandbox dir). Fix provided with path #2666/#3259. Waiting for the path, you have to remove/chown the

user sandbox dir (in /opt/glite/var/cream_sandbox...).

October 05, 2009, at 04:06 PM by 193.205.157.206 -
Changed lines 16-17 from:
  • There is a bug in lcas, which crashes (and therefore glexec doesn't work) if the number of delegation is higher than the number of RDNs in the subject. For example the following proxy:
to:
  • Bug #52876:The extra_attribute table in the CREAM DB has no keys/indexes defined. This results in performance problems for some operations
Waiting for the official fix (released with patch #2666/#3259), it is suggested to create the index using the following mysql command
Changed lines 20-24 from:

subject : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy/CN=proxy issuer : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy identity : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy type : proxy strength : 1024 bits

to:

mysql --password=<passwd> -D creamdb -u root -e 'ALTER TABLE extra_attribute ADD CONSTRAINT fk_extra_attribute_jobId_job_id FOREIGN KEY (jobId) REFERENCES job (id) ON UPDATE NO ACTION ON DELETE NO ACTION; CREATE INDEX commandGroupId_Idx ON JOB_MANAGEMENT (commandGroupId);'

Changed lines 23-33 from:
is affected by the problem, since the number of RDN is 3 (O=GermanGrid, OU=GSI, CN=Kilian Schwarz) and the number of delegations is 4.
Fix provided with patch #3084
  • Bug #52876:The extra_attribute table in the CREAM DB has no keys/indexes defined. This results in performance problems for some operations
Waiting for the official fix (released with patch #2666/#3259), it is suggested to create the index using the following mysql command
mysql --password=<passwd> -D creamdb -u root -e 'ALTER TABLE extra_attribute ADD CONSTRAINT fk_extra_attribute_jobId_job_id FOREIGN KEY (jobId) REFERENCES job (id) ON UPDATE NO ACTION ON DELETE NO ACTION; CREATE INDEX commandGroupId_Idx ON JOB_MANAGEMENT (commandGroupId);'
to:
Changed lines 50-53 from:
  • If you see an error message such as "log_success_msg: command not found" starting/stopping tomcat, please check this page.
to:
  • If you see an error message such as "log_success_msg: command not found" starting/stopping tomcat, please check this page. At any rate this message is basically harmless
Deleted lines 65-67:
  • Bug #42401: The JDL attribute MWVersion is not properly managed: fix provided with patch #2666/#3259
Changed lines 84-88 from:
to:
  • Bug #56518: The BLAH blparser doesn't automatically start after a reboot

Problems for which fixes have already been released in production

Changed lines 116-117 from:

Problems for which fixes have already been released in production

to:
  • There is a bug in lcas, which crashes (and therefore glexec doesn't work) if the number of delegation is higher than the number of RDNs in the subject. For example the following proxy:
subject   : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy/CN=proxy
issuer    : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy
identity  : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy
type      : proxy
strength  : 1024 bits
is affected by the problem, since the number of RDN is 3 (O=GermanGrid, OU=GSI, CN=Kilian Schwarz) and the number of delegations is 4.
Fix provided with patch #3084
September 30, 2009, at 12:48 PM by 193.205.157.206 -
Changed lines 4-7 from:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651).
As a workaround it is suggested:
  • To create the index for the extra_table attribute (see below bug #52876)
  • To increase (with ulimit -n) the number of file descriptors (e.g. to 4096)
to:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651): fix provided with patch #3179
As a workaround in the meantime it is suggested:
  • To create the index for the extra_table attribute (see below bug #52876): not needed if you are already using patch #2666/#3259
  • To increase the number of file descriptors (e.g. to 4096) for tomcat. You can do it editing /etc/security/limits.conf and adding:
tomcat           soft    nofile          4096
tomcat           hard    nofile          4096
September 30, 2009, at 12:13 PM by 193.205.157.206 -
Changed lines 4-9 from:
  • On glite 3.1 (which is supported just for sl4_ia32), BLAH and the blparser don't work on 64bit machines.
to:
  • CREAM/CEMon could "crash" reporting in its log files "too many open files" (see bug #52651).
As a workaround it is suggested:
  • To create the index for the extra_table attribute (see below bug #52876)
  • To increase (with ulimit -n) the number of file descriptors (e.g. to 4096)
  • On glite 3.1 (which is supported just for sl4_ia32), BLAH and the blparser don't work on 64bit machines: fix provided with patch #3259
September 30, 2009, at 12:04 PM by 193.205.157.206 -
Changed line 21 from:
Waiting for the official fix (released with patch #2666), it is suggested to create the index using the following mysql command
to:
Waiting for the official fix (released with patch #2666/#3259), it is suggested to create the index using the following mysql command
Changed lines 27-32 from:
  • Because of bug #44924, if the CREAM jobwrapper fails to download the proxy from the CREAM CE node, after 5 attempts it gives up and cancels the job with "proxy expired", even if the proxy is still valid. The recent changes in yaim-core (which introduced a limit on the number of concurrent gridftp connections), can trigger this problem. For the time being the workaround is to remove /opt/globus/etc/gridftp.conf from the CREAM CE and restart the gridftpd: fix provided with patch #2666
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitly or by the automatic purger) when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830: fix provided with patch #2666
to:
  • Because of bug #44924, if the CREAM jobwrapper fails to download the proxy from the CREAM CE node, after 5 attempts it gives up and cancels the job with "proxy expired", even if the proxy is still valid. The recent changes in yaim-core (which introduced a limit on the number of concurrent gridftp connections), can trigger this problem. For the time being the workaround is to remove /opt/globus/etc/gridftp.conf from the CREAM CE and restart the gridftpd: fix provided with patch #2666/#3259
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitly or by the automatic purger) when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830: fix provided with patch #2666/#3259
Changed lines 46-48 from:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is however managed by the yaim-cream-ce conf procedure. With patch #2666 VOMS server certificates are not needed anymore
to:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is however managed by the yaim-cream-ce conf procedure. With patch #2666/#3259 VOMS server certificates are not needed anymore
Changed lines 69-75 from:
  • Bug #42401: The JDL attribute MWVersion is not properly managed: fix provided with patch #2666
  • Bug #43830: There are problems if there are more than 32000 active jobs for a given user: fix provided with patch #2666
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed: fix provided with patch #2666
to:
  • Bug #42401: The JDL attribute MWVersion is not properly managed: fix provided with patch #2666/#3259
  • Bug #43830: There are problems if there are more than 32000 active jobs for a given user: fix provided with patch #2666/#3259
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed: fix provided with patch #2666/#3259
September 14, 2009, at 09:41 PM by 79.1.247.221 -
Added lines 3-4:
  • On glite 3.1 (which is supported just for sl4_ia32), BLAH and the blparser don't work on 64bit machines.
July 30, 2009, at 07:51 AM by 151.81.134.160 -
Changed lines 50-52 from:
  • Because of bug #36470 (in LB) LB processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim. Fix provided with patch #3042
to:
Added line 119:
  • Because of bug #36470 (in LB) LB processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim. Fix provided with gLite 3.1 Update 52
July 30, 2009, at 07:47 AM by 151.81.134.160 -
Added lines 118-119:

Problems for which fixes have already been released in production

July 20, 2009, at 09:14 AM by 193.205.157.206 -
Changed line 19 from:
Waiting for the official fix, it is suggested to create the index using the following mysql command
to:
Waiting for the official fix (released with patch #2666), it is suggested to create the index using the following mysql command
Changed lines 21-23 from:

use creamdb; ALTER TABLE extra_attribute ADD CONSTRAINT fk_extra_attribute_jobId_job_id FOREIGN KEY (jobId) REFERENCES job (id) ON UPDATE CASCADE ON DELETE CASCADE;

to:

mysql --password=<passwd> -D creamdb -u root -e 'ALTER TABLE extra_attribute ADD CONSTRAINT fk_extra_attribute_jobId_job_id FOREIGN KEY (jobId) REFERENCES job (id) ON UPDATE NO ACTION ON DELETE NO ACTION; CREATE INDEX commandGroupId_Idx ON JOB_MANAGEMENT (commandGroupId);'

July 09, 2009, at 05:05 PM by 193.205.157.206 -
Added lines 3-15:
  • There is a bug in lcas, which crashes (and therefore glexec doesn't work) if the number of delegation is higher than the number of RDNs in the subject. For example the following proxy:
subject   : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy/CN=proxy
issuer    : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy
identity  : /O=GermanGrid/OU=GSI/CN=Kilian Schwarz/CN=proxy/CN=proxy/CN=proxy
type      : proxy
strength  : 1024 bits
is affected by the problem, since the number of RDN is 3 (O=GermanGrid, OU=GSI, CN=Kilian Schwarz) and the number of delegations is 4.
Fix provided with patch #3084
July 09, 2009, at 12:42 PM by 193.205.157.206 -
Added line 8:
July 09, 2009, at 12:42 PM by 193.205.157.206 -
Changed line 6 from:

Waiting for the official fix, it is suggested to create the index using the following mysql command

to:
Waiting for the official fix, it is suggested to create the index using the following mysql command
July 09, 2009, at 12:42 PM by 193.205.157.206 -
Added lines 3-10:
  • Bug #52876:The extra_attribute table in the CREAM DB has no keys/indexes defined. This results in performance problems for some operations

Waiting for the official fix, it is suggested to create the index using the following mysql command

use creamdb;
ALTER TABLE extra_attribute ADD CONSTRAINT fk_extra_attribute_jobId_job_id FOREIGN KEY (jobId) REFERENCES job (id) ON UPDATE CASCADE ON DELETE CASCADE;
July 09, 2009, at 12:32 PM by 193.205.157.206 -
Added line 7:
Changed lines 36-38 from:
  • Because of bug #47152 (in LCMAPS) there might be problems if many-to-one static accounts mapping is used. This results in a glexec failure. As workaround, voms pool account should be used instead of static ones
to:
Changed lines 58-60 from:
  • There are problems if the CREAM RPM is updated, and this is not followed by a reconfiguration
to:
  • After an update of the CREAM RPM, it is mandatory to reconfigure (via yaim)
Added line 70:
Added lines 98-100:
  • Because of bug #47152 (in LCMAPS) there might be problems if many-to-one static accounts mapping is used. This results in a glexec failure. As workaround, voms pool account should be used instead of static ones. Fix provided with gLite 3.1 Update 49
June 17, 2009, at 05:03 PM by 193.205.157.206 -
Changed line 69 from:
  • Bug #47804: for a LSF based CREAM CE, the yaim variable BATCH_CONF_DIR must be set to the directory where there is the lsf.conf. yaim-cream-ce assumes that in the same directory there is also the lsf.profile script, while this is not always the case. Waiting for the fix for this bug, the workaround is to edit /opt/glite/etc/blah.config (setting the proper path of the lsf.profile script), and restart tomact
to:
  • Bug #47804: for a LSF based CREAM CE, the yaim variable BATCH_CONF_DIR must be set to the directory where there is the lsf.conf. yaim-cream-ce assumes that in the same directory there is also the lsf.profile script, while this is not always the case. Waiting for the fix for this bug, the workaround is to edit /opt/glite/etc/blah.config (setting the proper path of the lsf.profile script), and restart tomcat
June 17, 2009, at 05:03 PM by 193.205.157.206 -
Added lines 67-69:
  • Bug #47804: for a LSF based CREAM CE, the yaim variable BATCH_CONF_DIR must be set to the directory where there is the lsf.conf. yaim-cream-ce assumes that in the same directory there is also the lsf.profile script, while this is not always the case. Waiting for the fix for this bug, the workaround is to edit /opt/glite/etc/blah.config (setting the proper path of the lsf.profile script), and restart tomact
June 15, 2009, at 06:37 PM by 151.81.128.157 -
Changed lines 5-9 from:
  • Because of bug #44924, if the CREAM jobwrapper fails to download the proxy from the CREAM CE node, after 5 attempts it gives up and cancels the job with "proxy expired", even if the proxy is still valid. The recent changes in yaim-core (which introduced a limit on the number of concurrent gridftp connections), can trigger this problem. For the time being the workaround is to remove /opt/globus/etc/gridftp.conf from the CREAM CE and restart the gridftpd
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitly or by the automatic purger) when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830
to:
  • Because of bug #44924, if the CREAM jobwrapper fails to download the proxy from the CREAM CE node, after 5 attempts it gives up and cancels the job with "proxy expired", even if the proxy is still valid. The recent changes in yaim-core (which introduced a limit on the number of concurrent gridftp connections), can trigger this problem. For the time being the workaround is to remove /opt/globus/etc/gridftp.conf from the CREAM CE and restart the gridftpd: fix provided with patch #2666
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitly or by the automatic purger) when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830: fix provided with patch #2666
Changed lines 23-25 from:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is however managed by the yaim-cream-ce conf procedure
to:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is however managed by the yaim-cream-ce conf procedure. With patch #2666 VOMS server certificates are not needed anymore
Changed lines 29-31 from:
  • Because of bug #36470 (in LB) LB processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim. Fix provided with patch #2805
to:
  • Because of bug #36470 (in LB) LB processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim. Fix provided with patch #3042
Changed lines 50-56 from:
  • Bug #42401: The JDL attribute MWVersion is not properly managed
  • Bug #43830: There are problems if there are more than 32000 active jobs for a given user
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed
to:
  • Bug #42401: The JDL attribute MWVersion is not properly managed: fix provided with patch #2666
  • Bug #43830: There are problems if there are more than 32000 active jobs for a given user: fix provided with patch #2666
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed: fix provided with patch #2666
May 21, 2009, at 04:41 PM by 82.54.247.237 -
Added lines 4-5:
  • Because of bug #44924, if the CREAM jobwrapper fails to download the proxy from the CREAM CE node, after 5 attempts it gives up and cancels the job with "proxy expired", even if the proxy is still valid. The recent changes in yaim-core (which introduced a limit on the number of concurrent gridftp connections), can trigger this problem. For the time being the workaround is to remove /opt/globus/etc/gridftp.conf from the CREAM CE and restart the gridftpd
May 08, 2009, at 07:24 PM by 62.218.228.5 -
Changed lines 64-92 from:

@]

to:

@]

  • After introducing the fix for Bug #45887, YAIM has stopped to create /opt/edg/var/info directories. This is a mistake since the version of lcg-tags that will be able to write in the new directory /opt/glite/var/info/<SubClusterUniqueId>/<vo> is released in Patch #2940 that hasn't been certified yet. Old directories need to be supported for a while. The workaround is needed in clean installations or when a new VO is added in the CE. Edit $INSTALL_ROOT/glite/yaim/functions/cofig_gip_vo_tag and add at the end the old code to create the /opt/edg/var/info directory:
    for VO in $VOS; do
        dir=${INSTALL_ROOT}/edg/var/info/$VO
        mkdir -p $dir
                f=$dir/$VO.list
                [ -f $f ] || touch $f
        # work out the sgm user for this VO
        sgmusers=`users_getspecialusers $VO sgm`
        sgmuser=`echo $sgmusers | cut -d " " -f 1`
        vogroup=`users_getvogroup ${VO}`
        sgmgroup=`users_getspecialgroup ${VO} sgm`

        sgmgroup=`id -g -n $sgmuser`
        chown -R ${sgmuser}:${sgmgroup} $dir
        yaimlog DEBUG "$vogroup, $sgmgroup"
        if [ "x$vogroup" = "x$sgmgroup" ]; then
                yaimlog DEBUG "Removing grop writeability of files in $dir, sgm's primary group is equal to pool account's primary group."
                chmod -R go-w $dir
        else
                yaimlog DEBUG "Adding grop writeability of files in $dir, sgm's primary group is different to pool account's primary group."
                chmod -R ug+rw,o-w $dir
        fi
    done
April 23, 2009, at 01:10 PM by 193.205.157.206 -
Changed lines 18-20 from:
  • Old (expired) proxies delegated to a CREAM based CE are not deleted (bug #33730)
to:
  • Old (expired) proxies delegated to a CREAM based CE are not deleted (bugs #33730 and #49497)
Changed lines 27-29 from:
  • Because of bug #36470 (in LB) LB processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim
to:
  • Because of bug #36470 (in LB) LB processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim. Fix provided with patch #2805
Deleted lines 33-35:
  • Jobs may be aborted with "killed by signal 15" reason. Patch #2750 provides a fix which will reduce the probability of such errors
April 15, 2009, at 10:42 AM by 193.205.157.206 -
Changed lines 5-19 from:
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitely or by the automatic purger)

when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830

  • Bug #47700: glexec operations in CREAM could fail reporting in syslog something like:
glexec[2869]: directory is writable by others: (/tmp)
The workaround is to edit /opt/glite/etc/glite-ce-cream/cream-config.xml, replacing /tmp with /opt/glite/var/tmp for the JOBS_SCRATCH_DIR property. Then restart tomcat:
service tomcat5 restart
Fix provided with patch #2748
to:
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitly or by the automatic purger) when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830
Added line 17:
Added line 20:
Changed lines 23-24 from:
  • The information about software is not published in a CREAM based CE (bug #42777 and bug #45844): fix provided with patch #2750
to:
Added line 26:
Changed lines 29-30 from:
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454): fix provided with patch #2845
to:
Changed lines 32-41 from:
  • The purge operation can trigger a "too many open files" problem: bugs #45437 and #46024 (fix provided with patch #2748)
  • There is a memory leak in the BLAH BLparser for LSF (bug #46283): fix provided with patch #2748
  • There might be crashes of the BLAH BLparser or failures in sending notifications to CREAM (bugs #45718 and #47375): fix provided with patch #2748
  • There are problems if a job submitted via the WMS is resubmitted to the same CREAM CE (bug #45736): fix provided with patch #2748
  • Proxy renewal is not done if a job is not yet in IDLE status when the proxy renewal operation is issued (bug #45913): fix provided with patch #2748
to:
Added line 35:
Added line 38:
Changed lines 50-55 from:
  • Bug #47209: The glite-ce-blparser startup script assumes that ${GLITE_LOCATION_VAR} exists (while it doesn't necessarily exist on the BLParser host). Because of this, there might be problems starting the blparser be started. Fix provided with patch #2748
  • Bug #45983: in some cases BLAH can report that the submission to the batch system failed (and CREAM acts accordingly) while the job has been actually submitted. Fix provided with patch #2748
  • Bug #47655: the proxy used for glexec operations is not refreshed with the proxy renewal operation. This means that a proxy renewal operation can fail if this proxy expires. Fix provided with patch #2748
to:
Added line 53:
Added line 56:
Added line 59:
Added line 61:
March 16, 2009, at 02:14 PM by 82.52.180.181 -
Added lines 5-9:
  • Bug #48144: the CREAM job purger directory is not cleared when the purge operation is called (explicitely or by the automatic purger)

when the group which the user is mapped is different than the name of the VO. This can help to trigger bug #43830

Added lines 18-19:
Fix provided with patch #2748
Changed line 37 from:
  • Because of bug #36470 (in LB) lb processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim
to:
  • Because of bug #36470 (in LB) LB processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim
March 09, 2009, at 10:42 AM by 193.205.157.206 -
Changed lines 73-79 from:
  • There are problems if the CREAM RPM is updated, and this is not followed by a reconfiguration
to:
  • There are problems if the CREAM RPM is updated, and this is not followed by a reconfiguration
  • Because of bug #37366 (in gsoap-plugin) some error messages are not propagated properly, and in this case user simply get something like:
Received NULL fault; the error is due to another cause: : FaultString=[Client fault] - FaultCode=[SOAP-ENV:Client]
March 06, 2009, at 04:40 PM by 79.1.55.204 -
Changed lines 71-73 from:
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed
to:
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed
  • There are problems if the CREAM RPM is updated, and this is not followed by a reconfiguration
March 06, 2009, at 04:28 PM by 79.1.55.204 -
Changed lines 65-71 from:
  • Bug #47655: the proxy used for glexec operations is not refreshed with the proxy renewal operation. This means that a proxy renewal operation can fail if this proxy expires. Fix provided with patch #2748
to:
  • Bug #47655: the proxy used for glexec operations is not refreshed with the proxy renewal operation. This means that a proxy renewal operation can fail if this proxy expires. Fix provided with patch #2748
  • Bug #42401: The JDL attribute MWVersion is not properly managed
  • Bug #43830: There are problems if there are more than 32000 active jobs for a given user
  • Bug #47447: The JDL attribute MaxOutputSandboxSize is not properly managed
March 06, 2009, at 03:53 PM by 79.1.55.204 -
Changed lines 40-41 from:
  • There might be crashes of the BLAH BLparser for PBS (bug #45718): fix provided with patch #2748
to:
  • There might be crashes of the BLAH BLparser or failures in sending notifications to CREAM (bugs #45718 and #47375): fix provided with patch #2748
Added lines 63-65:
  • Bug #45983: in some cases BLAH can report that the submission to the batch system failed (and CREAM acts accordingly) while the job has been actually submitted. Fix provided with patch #2748
  • Bug #47655: the proxy used for glexec operations is not refreshed with the proxy renewal operation. This means that a proxy renewal operation can fail if this proxy expires. Fix provided with patch #2748
March 06, 2009, at 02:10 PM by 79.1.55.204 -
Changed lines 21-27 from:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is the following:
    • replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one
    • stop tomcat: service tomcat5 stop
    • rm -Rf /opt/glite/var/cream_sandbox
    • start tomcat: service tomcat5 start
Fix provided with patch #2667
  • The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2669
to:
Changed lines 23-25 from:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399: fix provided by patch #2667)
to:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is however managed by the yaim-cream-ce conf procedure
Added line 27:
Added line 29:
Changed lines 31-33 from:
  • The BLParser could crash if there are incomplete lines in the log files (bug #44642): fix provided with patch #2669
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454): fix provided with patch #2803
  • If you see an error message such as "log_success_msg: command not found" starting/stopping tomcat, please check this page
to:
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454): fix provided with patch #2845
  • If you see an error message such as "log_success_msg: command not found" starting/stopping tomcat, please check this page.
Added line 37:
Added line 39:
Added line 41:
Added line 43:
Changed lines 45-47 from:
  • Because of bug #47152 (in LCMAPS) there might be problems if many-to-one static accounts mapping is used
to:
  • Because of bug #47152 (in LCMAPS) there might be problems if many-to-one static accounts mapping is used. This results in a glexec failure. As workaround, voms pool account should be used instead of static ones
Added line 49:
March 05, 2009, at 11:58 AM by 193.205.157.206 -
Changed line 11 from:
@service tomcat5 restart@@
to:
service tomcat5 restart
March 05, 2009, at 11:58 AM by 193.205.157.206 -
Changed lines 9-11 from:
The workaround is to edit /opt/glite/etc/glite-ce-cream/cream-config.xml, replacing /tmp with /opt/glite/var/tmp for the JOBS_SCRATCH_DIR property
to:
The workaround is to edit /opt/glite/etc/glite-ce-cream/cream-config.xml, replacing /tmp with /opt/glite/var/tmp for the JOBS_SCRATCH_DIR property. Then restart tomcat:
@service tomcat5 restart@@
March 05, 2009, at 11:51 AM by 193.205.157.206 -
Added lines 4-9:
  • Bug #47700: glexec operations in CREAM could fail reporting in syslog something like:
glexec[2869]: directory is writable by others: (/tmp)
The workaround is to edit /opt/glite/etc/glite-ce-cream/cream-config.xml, replacing /tmp with /opt/glite/var/tmp for the JOBS_SCRATCH_DIR property
February 23, 2009, at 11:35 AM by 193.205.157.206 -
Changed line 26 from:
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454): fix provided with patch #2665
to:
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454): fix provided with patch #2803
February 23, 2009, at 11:34 AM by 193.205.157.206 -
Changed line 22 from:
  • The information about software is not published in a CREAM based CE (bug #42777 and bug #45844)
to:
  • The information about software is not published in a CREAM based CE (bug #42777 and bug #45844): fix provided with patch #2750
February 23, 2009, at 11:33 AM by 193.205.157.206 -
Added lines 5-12:
  • Bug #47254: if the proxy used to talk with a CREAM based CE is shorter than 10 minutes, the following problem could be seen:
CREAM Register returned error "MethodName=[jobRegister] Timestamp=[Fri 20 Feb 2009 16:24:32] ErrorCode=[0] Description=[system error]
FaultCause=[cannot create the job's working directory! The problem seems to be related to glexec]"
Actually in these cases glexec is not to blame: the problem is instead in the proxy used by CREAM for this glexec operation
Added lines 45-46:
  • Bug #47209: The glite-ce-blparser startup script assumes that ${GLITE_LOCATION_VAR} exists (while it doesn't necessarily exist on the BLParser host). Because of this, there might be problems starting the blparser be started. Fix provided with patch #2748
February 20, 2009, at 12:54 PM by 193.205.157.206 -
Added line 26:
  • Jobs may be aborted with "killed by signal 15" reason. Patch #2750 provides a fix which will reduce the probability of such errors
February 20, 2009, at 12:50 PM by 193.205.157.206 -
Changed lines 20-25 from:
  • The purge operation can trigger a "too many open files" problem: bugs #45437 and #46024
to:
  • The purge operation can trigger a "too many open files" problem: bugs #45437 and #46024 (fix provided with patch #2748)
  • There is a memory leak in the BLAH BLparser for LSF (bug #46283): fix provided with patch #2748
  • There might be crashes of the BLAH BLparser for PBS (bug #45718): fix provided with patch #2748
  • There are problems if a job submitted via the WMS is resubmitted to the same CREAM CE (bug #45736): fix provided with patch #2748
  • Proxy renewal is not done if a job is not yet in IDLE status when the proxy renewal operation is issued (bug #45913): fix provided with patch #2748
  • Because of bug #47152 (in LCMAPS) there might be problems if many-to-one static accounts mapping is used
February 11, 2009, at 09:25 AM by 193.205.157.206 -
Deleted lines 13-16:
  • Old (forgotten) jobs are not automatically purged (bug #38420): users should purge their jobs when they are in a final state: fix provided with patch #2415
  • Memory leaks in CREAM and CEMon, due to a memory leak in jclassads (bug #39131 and #39132): fix provided with patch #2415
  • CERequirements doesn't work properly (bug #41716): fix provided with patch #2415
  • CREAM doesn't properly manage the JDL attribute MWVersion (bug #42401): fix provided with patch #2415
February 11, 2009, at 09:23 AM by 193.205.157.206 -
Changed lines 6-7 from:
  • replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one
  • stop tomcat: @service tomcat5 stop@
to:
  • replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one
  • stop tomcat: service tomcat5 stop
February 11, 2009, at 09:22 AM by 193.205.157.206 -
Changed lines 5-10 from:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is to replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one: fix provided with patch #2667
to:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is the following:
    • replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one
    • stop tomcat: @service tomcat5 stop@
    • rm -Rf /opt/glite/var/cream_sandbox
    • start tomcat: service tomcat5 start
Fix provided with patch #2667
January 20, 2009, at 04:12 PM by 193.205.157.206 -
Changed lines 20-21 from:
  • Sometimes glexec (used by CREAM/BLAH) can fail reporting in syslog something like:
to:
  • Bug #45914 (in glexec): sometimes glexec (used by CREAM/BLAH) can fail reporting in syslog something like:
Changed lines 25-26 from:

IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Alessio_Gianelle_dteam_Role_NULL_C apability_NULL/https3A2F2Fdevel152Ecnaf2Einfn2Eit3A90002FGOWAw6pOslnknloKZj12DdA

to:

IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Alessio_Gianelle_dteam_Role_NULL_Capability_NULL/https3A2F2Fdevel152Ecnaf2Einfn2Eit3A90002FGOWAw6pOslnknloKZj12DdA

Changed line 29 from:
to:
January 20, 2009, at 04:11 PM by 193.205.157.206 -
Changed line 17 from:
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454)
to:
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454): fix provided with patch #2665
Added lines 19-30:
  • The purge operation can trigger a "too many open files" problem: bugs #45437 and #46024
  • Sometimes glexec (used by CREAM/BLAH) can fail reporting in syslog something like:
Dec 18 17:44:35 cream-32 glexec[18612]: File
'/opt/glite/var/cream/user_proxy/C_
IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Alessio_Gianelle_dteam_Role_NULL_C
apability_NULL/https3A2F2Fdevel152Ecnaf2Einfn2Eit3A90002FGOWAw6pOslnknloKZj12DdA
_deleg.proxy.lmt' has changed during opening.
Dec 18 17:44:35 cream-32 glexec[18612]: Error in LCAS/LCMAPS, rc = 120
January 13, 2009, at 11:36 PM by 82.48.233.136 -
Changed line 13 from:
  • The information about software is not published in a CREAM based CE (bug #42777): fix provided with patch #2667
to:
  • The information about software is not published in a CREAM based CE (bug #42777 and bug #45844)
January 12, 2009, at 05:02 PM by 193.205.157.206 -
Changed line 18 from:
to:
  • If you see an error message such as "log_success_msg: command not found" starting/stopping tomcat, please check this page
December 15, 2008, at 04:39 PM by 193.205.157.206 -
Changed lines 5-6 from:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is to replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one
  • The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2552
to:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is to replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one: fix provided with patch #2667
  • The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2669
Changed line 8 from:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399: fix provided by patch #2619)
to:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399: fix provided by patch #2667)
Changed line 13 from:
  • The information about software is not published in a CREAM based CE (bug #42777): fix provided with patch #2619
to:
  • The information about software is not published in a CREAM based CE (bug #42777): fix provided with patch #2667
Changed line 16 from:
  • The BLParser could crash if there are incomplete lines in the log files (bug #44642): fix provided with patch #2552
to:
  • The BLParser could crash if there are incomplete lines in the log files (bug #44642): fix provided with patch #2669
December 04, 2008, at 02:55 PM by 193.205.157.206 -
Changed lines 5-6 from:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is to replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with rgis one* The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2552
to:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is to replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with this one
  • The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2552
December 04, 2008, at 02:55 PM by 193.205.157.206 -
Changed line 5 from:
  • The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2552
to:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712): the workaround is to replace the file /opt/glite/etc/lcmaps/lcmaps-suexec.db with rgis one* The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2552
Changed line 17 from:
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712)
to:
November 30, 2008, at 10:23 PM by 79.24.246.237 -
Added lines 16-18:
  • Problems with transfer of ISB files using the CREAM CLI (bug #44454)
  • Because of a problem in the lcmaps configuration, in some cases the same user is mapped to different local accounts by glexec and gridftpd (bug #44712)
November 30, 2008, at 09:22 PM by 79.24.246.237 -
Changed lines 15-16 from:
to:
  • The BLParser could crash if there are incomplete lines in the log files (bug #44642): fix provided with patch #2552
November 28, 2008, at 11:15 PM by 79.16.22.138 -
Changed line 5 from:
  • The proxy renewal solution in production requires that a range of port is open on the WN: being fixed (see task #8176)
to:
  • The proxy renewal solution in production requires that a range of port is open on the WN: fix provided with patch #2552
Changed lines 7-8 from:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399)
  • Old (forgotten) jobs are not autocally purged (bug #38420): users should purge their jobs when they are in a final state: fix provided with patch #2415
to:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399: fix provided by patch #2619)
  • Old (forgotten) jobs are not automatically purged (bug #38420): users should purge their jobs when they are in a final state: fix provided with patch #2415
Changed lines 12-14 from:
  • There might be problems with the yaim based configuration procedure with LSF (bug #38822): fix provided with patch #2417
  • There are problems with the yaim based configuration procedure of the accounts are defined in ldap (bug #42142): fix provided with patch #2417
  • The information about software is not published in a CREAM based CE (bug #42777)
to:
  • The information about software is not published in a CREAM based CE (bug #42777): fix provided with patch #2619
November 14, 2008, at 02:53 PM by 193.205.157.206 -
Changed lines 7-8 from:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but

yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399)

to:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399)
November 14, 2008, at 02:52 PM by 193.205.157.206 -
Changed lines 7-8 from:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure
to:
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure, but

yaim-cream-ce renames everything in /etc/grid-security/vomsdir/file as file.pem, including directories (bug #43399)

Changed lines 17-18 from:
  • Because of bug #36470 (in LB) lb processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim
to:
  • Because of bug #36470 (in LB) lb processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim
November 13, 2008, at 10:18 AM by 79.24.246.131 -
November 13, 2008, at 10:03 AM by 79.24.246.131 -
Changed lines 16-17 from:
  • Because of bug #17046 (in trustmanager) if there are CA changes, it is necessary to restart tomcat
to:
  • Because of bug #17046 (in trustmanager) if there are CA changes, it is necessary to restart tomcat
  • Because of bug #36470 (in LB) lb processes in the CE could not run properly after a yaim (re)configuration. Please check the "Cream CE post-configuration" in the CREAM CE conf instructions via yaim
October 21, 2008, at 11:48 AM by 82.50.182.219 -
Changed line 5 from:
to:
  • The proxy renewal solution in production requires that a range of port is open on the WN: being fixed (see task #8176)
Added line 8:
Changed lines 15-16 from:
  • The information about software is not published in a CREAM based CE (bug #42777)
to:
  • The information about software is not published in a CREAM based CE (bug #42777)
  • Because of bug #17046 (in trustmanager) if there are CA changes, it is necessary to restart tomcat
October 21, 2008, at 11:43 AM by 82.50.182.219 -
Changed lines 2-5 from:

(the list refer to known problem affecting the latest release of the software)

to:

(the list refer to known problem affecting the release of the software in production)

Changed lines 8-11 from:
  • Old (forgotten) jobs are not autocally purged (bug #38420): users should purge their jobs when they are in a final state
  • Memory leaks in CREAM and CEMon, due to a memory leak in jclassads (bug #39131 and #39132)
  • CERequirements doesn't work properly (bug #41716)
to:
  • Old (forgotten) jobs are not autocally purged (bug #38420): users should purge their jobs when they are in a final state: fix provided with patch #2415
  • Memory leaks in CREAM and CEMon, due to a memory leak in jclassads (bug #39131 and #39132): fix provided with patch #2415
  • CERequirements doesn't work properly (bug #41716): fix provided with patch #2415
  • CREAM doesn't properly manage the JDL attribute MWVersion (bug #42401): fix provided with patch #2415
  • There might be problems with the yaim based configuration procedure with LSF (bug #38822): fix provided with patch #2417
  • There are problems with the yaim based configuration procedure of the accounts are defined in ldap (bug #42142): fix provided with patch #2417
  • The information about software is not published in a CREAM based CE (bug #42777)
October 02, 2008, at 02:09 PM by 79.6.45.54 -
Changed lines 6-8 from:
  • Bug #21616: old (expired) proxies delegated to a CREAM based CE are not deleted
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix
  • Because of bug #26817, the JDL sent to a CREAM CE shouldn't contain the cerequirements attribute
to:
  • Old (expired) proxies delegated to a CREAM based CE are not deleted (bug #33730)
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix (bug #22436): this is managed by the yaim-cream-ce conf procedure
  • Old (forgotten) jobs are not autocally purged (bug #38420): users should purge their jobs when they are in a final state
  • Memory leaks in CREAM and CEMon, due to a memory leak in jclassads (bug #39131 and #39132)
  • CERequirements doesn't work properly (bug #41716)
February 28, 2008, at 04:58 PM by 193.205.157.206 -
Deleted lines 7-8:
  • Because of bug #22437, after a restart of tomcat, the first operations could fail for authorization problems
  • From time to time glexec fails because of bug #23534. The problem hasn't been fully understood yet
Changed lines 9-10 from:
  • Because of bug #26884, from time to time CREAM job status changes get overwritten (instead of appended) by other status changes. This causes problems in particular to ICE which is not able to properly detect the job status changes
  • Because of bug #27211, from time to time a CREAM job is stuck in PENDING status, even if it run properly
to:
August 07, 2007, at 09:39 AM by 193.205.157.206 -
Deleted line 6:
  • Bug #16129: if the submission to PBS/LSF/... fails because e.g. the specified queue doesn't exist, because the queue is closed, etc., a proper error message is not returned
July 06, 2007, at 01:54 PM by 193.205.157.40 -
Deleted line 10:
  • Bug #24952: there are problems obtaining the WSDL form the CREAMDelegation service
Deleted lines 13-14:
  • Bug #27682: The SOAP message sent as response to the CREAM jobRegister operation has a format which is not WS-I compliant
  • Bug #27748: The check on JobType in CREAM is not case insensitive
July 05, 2007, at 10:16 AM by 193.205.157.206 -
Changed lines 1-3 from:

Known problems in CREAM software or in other software modules affecting a CREAM based CE

  • Because
to:

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)

  • Bug #21616: old (expired) proxies delegated to a CREAM based CE are not deleted
  • Bug #16129: if the submission to PBS/LSF/... fails because e.g. the specified queue doesn't exist, because the queue is closed, etc., a proper error message is not returned
  • Because of bug #22436, the cert file of VOMS servers (the ones in /etc/grid-security/vomsdir) must have .pem has suffix
  • Because of bug #22437, after a restart of tomcat, the first operations could fail for authorization problems
  • From time to time glexec fails because of bug #23534. The problem hasn't been fully understood yet
  • Bug #24952: there are problems obtaining the WSDL form the CREAMDelegation service
  • Because of bug #26817, the JDL sent to a CREAM CE shouldn't contain the cerequirements attribute
  • Because of bug #26884, from time to time CREAM job status changes get overwritten (instead of appended) by other status changes. This causes problems in particular to ICE which is not able to properly detect the job status changes
  • Because of bug #27211, from time to time a CREAM job is stuck in PENDING status, even if it run properly
  • Bug #27682: The SOAP message sent as response to the CREAM jobRegister operation has a format which is not WS-I compliant
  • Bug #27748: The check on JobType in CREAM is not case insensitive
July 05, 2007, at 10:00 AM by 193.205.157.206 -
Added lines 1-3:

Known problems in CREAM software or in other software modules affecting a CREAM based CE

  • Because