Hi,
> Any useful log information in /var/log/glite/wmproxy.log ?
It seems that there is some problem related to RGMA :
02 Feb, 03:03:25 -I- PID: 20684 - "wmproxy::main": ------- Starting Server
Instance -------
02 Feb, 03:03:25 -D- PID: 20684 - "wmproxy::main": Log
file: /var/log/glite/wmproxy.log
02 Feb, 03:03:25 -D- PID: 20684 - "WMPLBSelector::setWeightsFilePath": LB
server weights file
path: /var/glite/wmproxy/LBServerWeightsFile.wms1.cyf-kr.edu.pl
02 Feb, 03:03:25 -D- PID: 20684 - "WMPLBSelector::toWeightsFileAttributeName":
Input string: localhost:9000
02 Feb, 03:03:25 -D- PID: 20684 - "WMPLBSelector::toWeightsFileAttributeName":
Output string: Alocalhost|9000
02 Feb, 03:03:25 -D- PID: 20684 - "WMPLBSelector::updateLBServerAd": Adding
conf LB server: localhost:9000
02 Feb, 03:03:25 -D- PID: 20684 - "WMPLBSelector::updateLBServerAd": Calling
Service Discovery...
02 Feb, 03:03:25 -D- PID: 20684 - "WMPLBSelector::callServiceDiscovery":
Querying Service Discovery...
02 Feb, 03:04:07 -E- PID: 20684 - "WMPLBSelector::callServiceDiscovery":
Service Discovery failed: R-GMA API reported error (Can't connect to servlet
(authentication failed).).
02 Feb, 03:04:07 -D- PID: 20684 - "WMPLBSelector::updateLBServerAd": Service
Discovery returned 0 LB server[s]
02 Feb, 03:04:07 -D- PID: 20684 - "WMPLBSelector::updateLBServerAd": Setting
old weight for LB server Attribute: Alocalhost|9000
02 Feb, 03:04:07 -I- PID: 20684 - "wmproxy::main": Running as a FastCGI
program
02 Feb, 03:04:07 -I- PID: 20684 - "wmproxy::main": Entering the FastCGI accept
loop...
02 Feb, 03:04:07 -I- PID:
20684 - "wmproxy::main": ----------------------------------------
Regards,
--
Ćukasz Flis
|