More info: I now suspect that this is a permission/ownership issue. When I use my cert and run my globusrun-ws as the globus user, it works ok. Perhaps globus is trying to do something after it gives up its sudo?
mike On Thu, Sep 11, 2008 at 04:06:39PM +0200, mike packard wrote: > > Can you send us the server-side container logfile? > > (typically $GLOBUS_LOCATION/var/container.log) > > Thanks for the response. > > Here it is after a fresh restart. Not much to go on, I'm afraid. I can turn > on > the debug firehose if it would help. > > mike > > --- > > > # cat container.log > Starting SOAP server at: https://123.456.789.123:8443/wsrf/services/ > With the following services: > > [1]: https://123.456.789.123:8443/wsrf/services/AdminService > [2]: https://123.456.789.123:8443/wsrf/services/AuthzCalloutTestService > [3]: https://123.456.789.123:8443/wsrf/services/CASService > [4]: https://123.456.789.123:8443/wsrf/services/ContainerRegistryEntryService > [5]: https://123.456.789.123:8443/wsrf/services/ContainerRegistryService > [6]: https://123.456.789.123:8443/wsrf/services/CounterService > [7]: https://123.456.789.123:8443/wsrf/services/DefaultIndexService > [8]: https://123.456.789.123:8443/wsrf/services/DefaultIndexServiceEntry > [9]: https://123.456.789.123:8443/wsrf/services/DefaultTriggerService > [10]: https://123.456.789.123:8443/wsrf/services/DefaultTriggerServiceEntry > [11]: https://123.456.789.123:8443/wsrf/services/DelegationFactoryService > [12]: https://123.456.789.123:8443/wsrf/services/DelegationService > [13]: https://123.456.789.123:8443/wsrf/services/DelegationTestService > [14]: https://123.456.789.123:8443/wsrf/services/InMemoryServiceGroup > [15]: https://123.456.789.123:8443/wsrf/services/InMemoryServiceGroupEntry > [16]: https://123.456.789.123:8443/wsrf/services/InMemoryServiceGroupFactory > [17]: https://123.456.789.123:8443/wsrf/services/IndexFactoryService > [18]: https://123.456.789.123:8443/wsrf/services/IndexService > [19]: https://123.456.789.123:8443/wsrf/services/IndexServiceEntry > [20]: https://123.456.789.123:8443/wsrf/services/JWSCoreVersion > [21]: https://123.456.789.123:8443/wsrf/services/ManagedExecutableJobService > [22]: https://123.456.789.123:8443/wsrf/services/ManagedJobFactoryService > [23]: https://123.456.789.123:8443/wsrf/services/ManagedMultiJobService > [24]: https://123.456.789.123:8443/wsrf/services/ManagementService > [25]: > https://123.456.789.123:8443/wsrf/services/NotificationConsumerFactoryService > [26]: https://123.456.789.123:8443/wsrf/services/NotificationConsumerService > [27]: https://123.456.789.123:8443/wsrf/services/NotificationTestService > [28]: > https://123.456.789.123:8443/wsrf/services/PersistenceTestSubscriptionManager > [29]: > https://123.456.789.123:8443/wsrf/services/ReliableFileTransferFactoryService > [30]: https://123.456.789.123:8443/wsrf/services/ReliableFileTransferService > [31]: https://123.456.789.123:8443/wsrf/services/RendezvousFactoryService > [32]: https://123.456.789.123:8443/wsrf/services/ReplicationService > [33]: https://123.456.789.123:8443/wsrf/services/SampleAuthzService > [34]: https://123.456.789.123:8443/wsrf/services/SecureCounterService > [35]: https://123.456.789.123:8443/wsrf/services/SecurityTestService > [36]: https://123.456.789.123:8443/wsrf/services/ShutdownService > [37]: https://123.456.789.123:8443/wsrf/services/SubscriptionManagerService > [38]: https://123.456.789.123:8443/wsrf/services/TestAuthzService > [39]: https://123.456.789.123:8443/wsrf/services/TestRPCService > [40]: https://123.456.789.123:8443/wsrf/services/TestService > [41]: https://123.456.789.123:8443/wsrf/services/TestServiceRequest > [42]: https://123.456.789.123:8443/wsrf/services/TestServiceWrongWSDL > [43]: https://123.456.789.123:8443/wsrf/services/TriggerFactoryService > [44]: https://123.456.789.123:8443/wsrf/services/TriggerService > [45]: https://123.456.789.123:8443/wsrf/services/TriggerServiceEntry > [46]: https://123.456.789.123:8443/wsrf/services/Version > [47]: https://123.456.789.123:8443/wsrf/services/WidgetNotificationService > [48]: https://123.456.789.123:8443/wsrf/services/WidgetService > [49]: https://123.456.789.123:8443/wsrf/services/gsi/AuthenticationService > [50]: > https://123.456.789.123:8443/wsrf/services/mds/test/execsource/IndexService > [51]: > https://123.456.789.123:8443/wsrf/services/mds/test/execsource/IndexServiceEntry > [52]: > https://123.456.789.123:8443/wsrf/services/mds/test/subsource/IndexService > [53]: > https://123.456.789.123:8443/wsrf/services/mds/test/subsource/IndexServiceEntry > 2008-09-11 16:01:24,936 INFO impl.DefaultIndexService > [ServiceThread-77,processConfigFile:107] Reading default registration > configuration from file: > /opt/globus-4.0.8/etc/globus_wsrf_mds_index/hierarchy.xml > 2008-09-11 16:01:24,993 INFO exec.StateMachine > [RunQueueThread_1,logJobAccepted:3424] Job > 1ec9e8c0-800a-11dd-b54f-e4e72347b2a4 accepted for local user 'mpackard' for > DN '/O=University of Zurich/OU=OCI/OU=Baldridge group/OU=unizh.ch/CN=Mike > Packard' > 2008-09-11 16:01:25,373 INFO exec.StateMachine > [RunQueueThread_2,logJobSubmitted:3437] Job > 1ec9e8c0-800a-11dd-b54f-e4e72347b2a4 submitted with local job ID > '1f3ec0c8-800a-11dd-8c10-00142272b1a0:27594' > > > > > On Thu, Sep 11, 2008 at 08:43:10AM -0500, Martin Feller wrote: > > Mike, > > > > Can you send us the server-side container logfile? > > (typically $GLOBUS_LOCATION/var/container.log) > > > > Thanks, Martin > > > > mike packard wrote: > >> Good Morning, > >> > >> I am using globus 4.0.8 flavor gcc32 with on Suse enterprise 9 32-bit, > >> kernel > >> 2.6.5-7.308-bigsmp. > >> > >> I installed Globus using the quickstart guide here: > >> http://www.globus.org/toolkit/docs/4.0/admin/docbook/quickstart.html > >> > >> But when I try to run globusrun-ws it hangs at the CleanUp step. I hit > >> ctrl-c and > >> it hangs again at the "Destroying job..." step. I hit ctrl-c again and it > >> quits. Same thing when I use the SGE jobmanager. > >> > >> I know that credentials are ok because I can file transfer via both > >> globus-url-copy & rft. Also, I can submit jobs to another host (which had > >> globus setup already) just fine. Some examples are below. > >> > >> Any help would be greatly appreciated. > >> > >> Kind Regards, > >> Mike Packard > >> UZH > >> > >> > >> --- > >> Failed job: > >> > >>> globusrun-ws -submit -F https://host01.unizh.ch -Ft Fork -streaming -c > >>> /bin/hostname > >> Delegating user credentials...Done. > >> Submitting job...Done. > >> Job ID: uuid:c23483cc-7fd2-11dd-96d7-00142272b1a0 > >> Termination time: 09/12/2008 07:25 GMT > >> Current job state: Active > >> Current job state: CleanUp-Hold > >> host01.unizh.ch > >> Current job state: CleanUp > >> > >> "ctrl-c" > >> > >> Canceling...Canceled. > >> Destroying job... > >> > >> "ctrl-c" > >> > >> Canceling...Failed. > >> globusrun-ws: Operation was canceled > >> globusrun-ws: Unable to destroy job: Error destroying job > >> globus_soap_message_module: Failed receiving response > >> ManagedJobPortType_Destroy. > >> globus_soap_message_module: SOAP Message transport failed: Error in HTTP > >> response > >> globus_xio: Operation was canceled > >> > >> --- > >> Successful job to other host: > >> > >>> globusrun-ws -submit -F https://host02.unizh.ch -Ft Fork -streaming -c > >>> /bin/hostname > >> Delegating user credentials...Done. > >> Submitting job...Done. > >> Job ID: uuid:ce733836-7fd2-11dd-a805-00142272b1a0 > >> Termination time: 09/12/2008 07:25 GMT > >> Current job state: Active > >> Current job state: CleanUp-Hold > >> host02.unizh.ch > >> Current job state: CleanUp > >> Current job state: Done > >> Destroying job...Done. > >> Cleaning up any delegated credentials...Done. > >> > >> > >> > >> --- > >> > >> Here is the container log for the failed job: > >> > >> > >> 2008-09-11 09:29:56,467 INFO exec.StateMachine > >> [RunQueueThread_0,logJobAccepted:3424] Job > >> 6ec0f7b0-7fd3-11dd-9f10-bf807922599c accepted for local user 'mpackard' > >> for DN '/O=University of Zurich/OU=OCI/OU=Baldridge > >> group/OU=unizh.ch/CN=Mike Packard' > >> 2008-09-11 09:29:56,708 INFO exec.StateMachine > >> [RunQueueThread_6,logJobSubmitted:3437] Job > >> 6ec0f7b0-7fd3-11dd-9f10-bf807922599c submitted with local job ID > >> '6eedf9d6-7fd3-11dd-845b-00142272b1a0:536' > >> > >> > > >
