gLite 3.1
gLite MyProxy known issues
When myproxy.cern.ch was upgraded to gLite 3.1 it was found
that the myproxy-server daemon will hang when it is started
from a non-interactive shell. It appears to work fine when
started from an interactive shell.
The cause of the problem is that the myproxy-server has been
linked against a multi-threaded flavor of Globus instead of
the single-threaded flavor expected by the code.
Unfortunately this mismatch was not discovered in the
certification process, possibly because the myproxy-server
had only been started interactively (by running YAIM).
We have asked the VDT project for an urgent rebuild of the
code against the correct Globus flavor. We will certify
the new rpm and release it to production with high priority.
In the meantime sites can either stay with the MyProxy
service provided by gLite 3.0, or restart the myproxy-server
interactively as needed.
|
gLite wide known issues
Please also check the gLite wide
known issues. |
|
