Hi,
I looked deeper into my problem and one thing I found was that the UMD WMS installation contained some new packages (not part of the EMI WMS installation)
> globus-callout-0.7-8.el5
> globus-common-11.6-5.el5
> globus-gsi-callback-2.8-2.el5
> globus-gsi-cert-utils-6.7-2.el5
> globus-gsi-credential-3.5-3.el5
> globus-gsi-openssl-error-0.14-8.el5
> globus-gsi-proxy-core-4.7-2.el5
> globus-gsi-proxy-ssl-2.3-3.el5
> globus-gsi-sysconfig-3.2-1.el5
> globus-gssapi-error-2.5-8.el5
> globus-gssapi-gsi-7.8-1.el5
> globus-gss-assist-5.10-1.el5
> globus-openssl-module-1.3-3.el5
> globus-xio-2.8-4.el5
My assumption is that there is a correlation between these new installed packages and the problem with globus-gridftp server.
Any advice?
Cheers,
Catalin
> -----Original Message-----
> From: LHC Computer Grid - Rollout [mailto:[log in to unmask]]
> On Behalf Of Catalin Condurache
> Sent: 03 February 2012 14:39
> To: [log in to unmask]
> Subject: [LCG-ROLLOUT] globus-gridftp issues on UMD WMS
>
> Hi,
>
> Last week I've installed an EMI WMS node using the EMI repository and
> emi-wms-1.0.2-0.sl5 as metapackage. Test submissions went fine.
>
> This week I tried a similar installation using the UMD repository with
> the same emi-wms-1.0.2-0.sl5 as metapackage. However this time the yaim
> configuration showed an error
>
>
> ...
> INFO: Copying the /etc/grid-security/voms-grid-mapfile in the
> standard location /etc/grid-security/grid-mapfile
> INFO: Executing function: config_vomsdir_setenv
> INFO: Executing function: config_vomsdir
> INFO: Executing function: config_vomses
> Error: Failed to initialize:
> an unknown error occurred
> INFO: Executing function: config_gip_wms
> INFO: Executing function: config_info_service_wms_setenv
> INFO: Executing function: config_info_service_wms
> INFO: Executing function: config_globus_gridftp_setenv
> INFO: Executing function: config_globus_gridftp
> INFO: Starting gridftp service :
> Stopping globus-gridftp-server: [FAILED]
> Starting globus-gridftp-server: [FAILED]
> INFO: Executing function: config_lcas_lcmaps_gt4_setenv
> INFO: Executing function: config_lcas_lcmaps_gt4
> INFO: Creating LCAS_DB_FILE in /etc/lcas/lcas.db
> INFO: Creating LCMAPS_DB_FILE in /etc/lcmaps/lcmaps.db.gridftp
> INFO: Executing function: config_condor_wms_setenv
> INFO: Executing function: config_condor_wms
> INFO: Executing function: config_glite_wms_setenv
> INFO: Executing function: config_glite_wms
> INFO: config_glite_wms: Configuration file
> INFO: config_glite_wms: Creating /etc/glite-
> wms/glite_wms.conf.yaimnew_20120203_090212 ...
> WARNING: /usr/sbin/glite_wms_wmproxy_load_monitor found
> Error: The proxy credential could not be written to the output file.
> Use -debug for further information.
> Error: Failed to initialize:
> an unknown error occurred
> Your identity:
> /C=UK/O=eScience/OU=CLRC/L=RAL/CN=lcgwms03.gridpp.rl.ac.uk/emailAddress
> [log in to unmask]
> Creating proxy ............................................ Done
> INFO: Executing function: config_gliteservices_wms_setenv
> INFO: Executing function: config_gliteservices_wms
> Stopping globus-gridftp-server: [FAILED]
> Starting globus-gridftp-server: [FAILED]
> stopping workload manager... ok
> starting workload manager... ok
> Restarting JobController daemon(s)
> Stopping JobController... [ OK ]
> A stale lock file still exists, removing it.. [ OK ]
> Stopping CondorG...Create jobdir queue object.
> [ OK ]
> Starting JobController... [ OK ]
> Starting CondorG... [ OK ]
> Stopping LogMonitor... [ OK ]
> A stale lock file still exists, removing it.. [ OK ]
> Starting LogMonitor... [ OK ]
> stopping ICE... ok
> starting ICE... ok
> Stopping ProxyRenewal Daemon: glite-proxy-renewd ... done
> Starting ProxyRenewal Daemon: glite-proxy-renewd ... done
> Starting Condor-C Launcher
> condorc-launcher already submitted!
> Skipping Condor-C Launcher
> Starting Condor-C Advertiser
> condorc-advertiser already submitted!
> Skipping Condor-C Advertiser
> Starting Condor-C Authorizer
> condorc-authorizer already submitted!
> Skipping Condor-C Authorizer
> Starting Condor-C VO Advertiser
> condorc-vo-advertiser already submitted!
> Skipping Condor-C VO Advertiser
> INFO: Executing function: config_cron_wms_setenv
> INFO: Executing function: config_cron_wms
> INFO: Executing function: config_glite_lb_setenv
> INFO: Executing function: config_glite_lb
> INFO: Configuring nodes [WMS], using L&B mode: proxy
> WARNING: Database lbserver20 already exists
> * got an empty brokers list from BDII
> Stopping glite-lb-notif-interlogd (20452) ... done
> Stopping glite-lb-bkserverd (20399) ... done
> glite-jp-importer not running
> Stopping glite-lb-interlogd (20489) ... done
> Starting glite-lb-bkserver ... done
> Starting glite-lb-notif-interlogd ... done
> Starting glite-lb-interlog for proxy ... done
> INFO: Executing function: config_glite_locallogger_setenv
> INFO: Executing function: config_glite_locallogger
> INFO: GLITE_LB_TYPE=proxy: nothing to do.
> INFO: Executing function: config_bdii_5.2
> Stopping BDII update process: [ OK ]
> Stopping BDII slapd: [ OK ]
> Starting BDII slapd: [ OK ]
> Starting BDII update process: [ OK ]
> INFO: Executing function: config_glite_initd
>
> [ INFO: Configuration Complete.
> INFO: YAIM terminated succesfully.
>
>
>
> It appeared to be a problem with globus-gridftp
>
> [root@lcgwms03 ~]# /etc/init.d/globus-gridftp status
> globus-gridftp-server dead but subsys locked
> [root@lcgwms03 ~]# /etc/init.d/globus-gridftp stop
> [root@lcgwms03 ~]# /etc/init.d/globus-gridftp start
> Starting globus-gridftp-server: Error: Failed to initialize:
> an unknown error occurred
> [FAILED]
>
>
> Unless I was doing some silly mistakes (but I followed the same
> configuration steps post-installation for both installations), I assume
> there is something wrong with a newer package in the UMD release.
>
> Has anyone experienced something similar recently?
>
> Many thanks,
>
> Catalin Condurache
> RAL Tier1 Grid Services
|