Hallo Dimitri,
> I have another thing to report regarding cream at emi2/sge:
>
> the cluster status is located in /etc/lrms/cluster.state.
> But changed it for example to "draining" doesn't have an effect doing ldapsearch from remote:
> ldapsearch -x -LLL -h cream-ge-3-kit:2170 -b o=grid | grep Status
> GlueCEStateStatus: Production
> GlueCEStateStatus: Production
> GlueServiceStatus: OK
> ...
>
> But on the host itself:
> [root@cream-ge-3-kit ~]# /var/lib/bdii/gip/plugin/glite-info-dynamic-ce | grep Status
> Use of uninitialized value in printf at /usr/libexec/glite-info-dynamic-sge line 428.
> GlueCEStateStatus: Draining
> GlueCEStateStatus: Draining
>
> So, ldap could not update .ldif files properly. why?
Maybe because you ran such commands as root, thereby making
(temporary) files/directories unwritable for user "ldap"?
I tried having a closer look, but:
-----------------------------------------------------------------------
$ uberftp cream-ge-3-kit.gridka.de
220 cream-ge-3-kit.gridka.de GridFTP Server 6.14 (gcc64, 1342551528-83)
[Globus Toolkit 5.2.1] ready.
globus_ftp_control: gss_init_sec_context failed
GSS Major Status: Authentication Failed
globus_gsi_gssapi: SSLv3 handshake problems
globus_gsi_gssapi: Unable to verify remote side's credentials
globus_gsi_gssapi: SSLv3 handshake problems: Couldn't do ssl handshake
OpenSSL Error: s3_clnt.c:915: in library: SSL routines,
function SSL3_GET_SERVER_CERTIFICATE: certificate verify failed
globus_gsi_callback_module: Could not verify credential
globus_gsi_callback_module: Could not verify credential
globus_gsi_callback_module: The certificate has been revoked:
Serial number = 19172 (0x4AE4)
Subject=/C=DE/O=GermanGrid/OU=KIT/CN=cream-ge-3-kit.gridka.de
Closing connection to service.
-----------------------------------------------------------------------
|