Well I've installed the RFT update, but still gettin the same problem and while doin grid-url-copy, its givin same connection refused error
following is the output [EMAIL PROTECTED] globus-4.0.7]# globus-url-copy gsiftp://[EMAIL PROTECTED]/etc/groupfile:///tmp/foo.test.copy error: globus_xio: Unable to connect to [EMAIL PROTECTED]:2811 globus_xio: System error in connect: Connection refused globus_xio: A system call failed: Connection refused thanx in advance On 6/4/08, Charles Bacon <[EMAIL PROTECTED]> wrote: > > I suppose the problem could be with the GridFTP servers listed in the > rft.xfr file. Can you run a globus-url-copy of the files listed in your > rft.xfr? > > Also, though this probably isn't the problem, you should also install the > RFT update package (globus_wsrf_rft_service_java-0.39 ) from > http://www.globus.org/toolkit/advisories.html > > > Charles > > On Jun 4, 2008, at 3:44 AM, ninja warrior wrote: > > Hi, >> I want to mention I have checked rftDatabase containts, >> >> Everytime when I try to check rft with >> $ rft -h hostname -f /tmp/rft.xfr >> >> It updates respective information in >> TABLE request >> TABLE requestid >> TABLE tranfer >> TABLE transferid >> >> That means connection is doing well, so what is the possible cause for >> connection refuse. >> thanx in advance. >> >> regards >> Ninja >> >> On 6/4/08, ninja warrior <[EMAIL PROTECTED]> wrote: Hi, >> Thanx for the raply, Following is the output when I start container, >> >> [EMAIL PROTECTED] ~]# globus-start-container >> Starting SOAP server at: https://172.16.16.111:8443/wsrf/services/ >> With the following services: >> >> [1]: https://172.16.16.111:8443/wsrf/services/AdminService >> [2]: https://172.16.16.111:8443/wsrf/services/AuthzCalloutTestService >> [3]: https://172.16.16.111:8443/wsrf/services/CASService >> [4]: >> https://172.16.16.111:8443/wsrf/services/ContainerRegistryEntryService >> [5]: https://172.16.16.111:8443/wsrf/services/ContainerRegistryService >> [6]: https://172.16.16.111:8443/wsrf/services/CounterService >> [7]: https://172.16.16.111:8443/wsrf/services/DefaultIndexService >> [8]: https://172.16.16.111:8443/wsrf/services/DefaultIndexServiceEntry >> [9]: https://172.16.16.111:8443/wsrf/services/DefaultTriggerService >> [10]: https://172.16.16.111:8443/wsrf/services/DefaultTriggerServiceEntry >> [11]: https://172.16.16.111:8443/wsrf/services/DelegationFactoryService >> [12]: https://172.16.16.111:8443/wsrf/services/DelegationService >> [13]: https://172.16.16.111:8443/wsrf/services/DelegationTestService >> [14]: https://172.16.16.111:8443/wsrf/services/InMemoryServiceGroup >> [15]: https://172.16.16.111:8443/wsrf/services/InMemoryServiceGroupEntry >> [16]: >> https://172.16.16.111:8443/wsrf/services/InMemoryServiceGroupFactory >> [17]: https://172.16.16.111:8443/wsrf/services/IndexFactoryService >> [18]: https://172.16.16.111:8443/wsrf/services/IndexService >> [19]: https://172.16.16.111:8443/wsrf/services/IndexServiceEntry >> [20]: https://172.16.16.111:8443/wsrf/services/JWSCoreVersion >> [21]: >> https://172.16.16.111:8443/wsrf/services/ManagedExecutableJobService >> [22]: https://172.16.16.111:8443/wsrf/services/ManagedJobFactoryService >> [23]: https://172.16.16.111:8443/wsrf/services/ManagedMultiJobService >> [24]: https://172.16.16.111:8443/wsrf/services/ManagementService >> [25]: >> https://172.16.16.111:8443/wsrf/services/NotificationConsumerFactoryService >> [26]: >> https://172.16.16.111:8443/wsrf/services/NotificationConsumerService >> [27]: https://172.16.16.111:8443/wsrf/services/NotificationTestService >> [28]: >> https://172.16.16.111:8443/wsrf/services/PersistenceTestSubscriptionManager >> [29]: >> https://172.16.16.111:8443/wsrf/services/ReliableFileTransferFactoryService >> [30]: >> https://172.16.16.111:8443/wsrf/services/ReliableFileTransferService >> [31]: https://172.16.16.111:8443/wsrf/services/RendezvousFactoryService >> [32]: https://172.16.16.111:8443/wsrf/services/SampleAuthzService >> [33]: https://172.16.16.111:8443/wsrf/services/SecureCounterService >> [34]: https://172.16.16.111:8443/wsrf/services/SecurityTestService >> [35]: https://172.16.16.111:8443/wsrf/services/ShutdownService >> [36]: https://172.16.16.111:8443/wsrf/services/SubscriptionManagerService >> [37]: https://172.16.16.111:8443/wsrf/services/TestAuthzService >> [38]: https://172.16.16.111:8443/wsrf/services/TestRPCService >> [39]: https://172.16.16.111:8443/wsrf/services/TestService >> [40]: https://172.16.16.111:8443/wsrf/services/TestServiceRequest >> [41]: https://172.16.16.111:8443/wsrf/services/TestServiceWrongWSDL >> [42]: https://172.16.16.111:8443/wsrf/services/TriggerFactoryService >> [43]: https://172.16.16.111:8443/wsrf/services/TriggerService >> [44]: https://172.16.16.111:8443/wsrf/services/TriggerServiceEntry >> [45]: https://172.16.16.111:8443/wsrf/services/Version >> [46]: https://172.16.16.111:8443/wsrf/services/WidgetNotificationService >> [47]: https://172.16.16.111:8443/wsrf/services/WidgetService >> [48]: https://172.16.16.111:8443/wsrf/services/gsi/AuthenticationService >> [49]: >> https://172.16.16.111:8443/wsrf/services/mds/test/execsource/IndexService >> [50]: >> https://172.16.16.111:8443/wsrf/services/mds/test/execsource/IndexServiceEntry >> [51]: >> https://172.16.16.111:8443/wsrf/services/mds/test/subsource/IndexService >> [52]: >> https://172.16.16.111:8443/wsrf/services/mds/test/subsource/IndexServiceEntry >> >> and finally I get >> 2008-06-04 11:31:41,524 INFO impl.DefaultIndexService >> [ServiceThread-117,processConfigFile:107] Reading default registration >> configuration from file: >> /usr/local/globus-4.0.7/etc/globus_wsrf_mds_index/hierarchy.xml >> >> >> >> >> >> On Mon, Jun 2, 2008 at 7:51 PM, Charles Bacon <[EMAIL PROTECTED]> wrote: >> What shows up on your container side? It sounds like RFT can't connect to >> the database you configured. >> >> >> Charles >> >> >> On Jun 2, 2008, at 5:05 AM, ninja warrior wrote: >> >> Hi, >> I have installed Globus tool lit 4.0.7 successfully, now when I try to >> check RFT it gives following error, >> >> Error:Connection creation error [Caused by: Connection refused] >> All Transfers failed ! >> >> >> $ rft -h hostname -f /tmp/rft.xfr [ in my case hostname is like >> [EMAIL PROTECTED] ] >> Number of transfers in this request: 1 >> Subscribed for overall status >> Termination time to set: 60 minutes >> >> Overall status of transfer: >> Finished/Active/Failed/Retrying/Pending >> 0/0/0/1/0 >> Error:Connection creation error [Caused by: Connection refused] >> . >> . >> . >> . and so on >> Overall status of transfer: >> Finished/Active/Failed/Retrying/Pending >> 0/0/1/0/0 >> Error:Connection creation error [Caused by: Connection refused] >> All Transfers failed ! >> >> >> I get failed status, any pointer in this direction will be very helpful. >> >> regards >> Ninja >> >> >> >> >> -- >> Keep safe distance... >> Ninja DA warrior >> >> >
