Hi Lukasz!

Thank for your support!

I had detected the problem. In my /etc/sudoers file, I had omited to
configure the right grid-mapfile directory. Now It's OK.

My /etc/sudoers's file before:
......
globus ALL=(nykibas) NOPASSWD:
/opt/globus-4.2.1/libexec/globus-gridmap-and-execute -g
/opt/globus-4.2.1/etc/grid-mapfile
/opt/globus-4.2.1/libexec/globus-job-manager-script.pl *

globus ALL=(nykibas) NOPASSWD:
/opt/globus-4.2.1/libexec/globus-gridmap-and-execute -g
/opt/globus-4.2.1/etc/grid-mapfile
/opt/globus-4.2.1/libexec/globus-gram-local-proxy-tool *

Now :
........
globus ALL=(nykibas) NOPASSWD:
/usr/local/globus-4.2.1/libexec/globus-gridmap-and-execute -g
/etc/grid-security/grid-mapfile
/usr/local/globus-4.2.1/libexec/globus-job-manager-script.pl *

globus ALL=(nykibas) NOPASSWD:
/usr/local/globus-4.2.1/libexec/globus-gridmap-and-execute -g
/etc/grid-security/grid-mapfile
/usr/local/globus-4.2.1/libexec/globus-gram-local-proxy-tool *

2010/5/4, Lukasz Lacinski <[email protected]>:
> Hi Yannick,
>
> As you can notice the command sudo asks the user globus for a password. It
> means that you didn't configure sudo properly. GRAM4 runs as the user
> globus. It means that if you want to execute a program as the user nykibas
> the user globus has to be able to change effective uid from globus to
> nykibas. It's possible if there is an appropriate entry in /etc/sudoers for
> the user globus. You can find more information at
> http://www.globus.org/toolkit/docs/4.2/4.2.1/execution/gram4/admin/#gram4-configsudo
> Please execute: man sudo, man sudoers.
>
> Regards,
> Lukasz
>
> On May 3, 2010, at 7:32 AM, Yannick Nzau wrote:
>
>> Hi Lukasz!
>> I had created a user on "nykibas" on labo-debian.unikin.cd and when I
>> entered again the command, I get this:
>>
>> nyki...@labo1-debian:~$ globusrun-ws -submit -streaming -F
>> https://labo-debian.unikin.cd:8443/wsrf/services/ManagedJobFactoryService
>> -c /usr/bin/whoami
>> Delegating user credentials...Done.
>> Submitting job...Done.
>> Job ID: uuid:94f580f6-56ad-11df-831e-0013205351e8
>> Termination time: 05/03/3010 12:15 GMT
>> Current job state: Failed
>> Destroying job...Done.
>> Cleaning up any delegated credentials...Done.
>> globusrun-ws: Job failed: Error code: 201Script stderr:
>> We trust you have received the usual lecture from the local
>> SystemAdministrator. It usually boils down to these three things:
>> #1) Respect the privacy of others.    #2) Think before you type.
>> #3) With great power comes great responsibility.[sudo] password for
>> globus:
>>
>> What does this means?
>>
>> There is the container' s log:
>>
>> Starting SOAP server at https://10.10.80.186:8443/wsrf/services/
>> 2010-05-03T12:46:15.013+01:00 INFO  impl.DefaultIndexService
>> [ServiceThread-57,performDefaultRegistrations:261]
>> guid=79c639a0-56a9-11df-aeca-9c6fdc015c43
>> event=org.globus.mds.index.performDefaultRegistrations.end status=0
>>
>> With the following services:
>>
>> [1]: https://10.10.80.186:8443/wsrf/services/AdminService
>> [2]: https://10.10.80.186:8443/wsrf/services/AttachmentTestService
>> [3]: https://10.10.80.186:8443/wsrf/services/AuthzCalloutTestService
>> [4]: https://10.10.80.186:8443/wsrf/services/CASService
>> [5]: https://10.10.80.186:8443/wsrf/services/ContainerRegistryEntryService
>> [6]: https://10.10.80.186:8443/wsrf/services/ContainerRegistryService
>> [7]: https://10.10.80.186:8443/wsrf/services/CounterService
>> [8]: https://10.10.80.186:8443/wsrf/services/DefaultIndexService
>> [9]: https://10.10.80.186:8443/wsrf/services/DefaultIndexServiceEntry
>> [10]: https://10.10.80.186:8443/wsrf/services/DelegationFactoryService
>> [11]: https://10.10.80.186:8443/wsrf/services/DelegationService
>> [12]: https://10.10.80.186:8443/wsrf/services/DelegationTestService
>> [13]: https://10.10.80.186:8443/wsrf/services/DeployService
>> [14]: https://10.10.80.186:8443/wsrf/services/GKrellmService
>> [15]: https://10.10.80.186:8443/wsrf/services/InMemoryServiceGroup
>> [16]: https://10.10.80.186:8443/wsrf/services/InMemoryServiceGroupEntry
>> [17]: https://10.10.80.186:8443/wsrf/services/InMemoryServiceGroupFactory
>> [18]: https://10.10.80.186:8443/wsrf/services/IndexFactoryService
>> [19]: https://10.10.80.186:8443/wsrf/services/IndexService
>> [20]: https://10.10.80.186:8443/wsrf/services/IndexServiceEntry
>> [21]: https://10.10.80.186:8443/wsrf/services/JWSCoreVersion
>> [22]: https://10.10.80.186:8443/wsrf/services/LoggingService
>> [23]: https://10.10.80.186:8443/wsrf/services/ManagedExecutableJobService
>> [24]: https://10.10.80.186:8443/wsrf/services/ManagedJobFactoryService
>> [25]: https://10.10.80.186:8443/wsrf/services/ManagedMultiJobService
>> [26]: https://10.10.80.186:8443/wsrf/services/ManagementService
>> [27]:
>> https://10.10.80.186:8443/wsrf/services/NotificationConsumerFactoryService
>> [28]: https://10.10.80.186:8443/wsrf/services/NotificationConsumerService
>> [29]: https://10.10.80.186:8443/wsrf/services/NotificationTestService
>> [30]:
>> https://10.10.80.186:8443/wsrf/services/PersistenceTestSubscriptionManager
>> [31]: https://10.10.80.186:8443/wsrf/services/QueryTestService
>> [32]: https://10.10.80.186:8443/wsrf/services/RPParamTestService
>> [33]:
>> https://10.10.80.186:8443/wsrf/services/ReliableFileTransferFactoryService
>> [34]: https://10.10.80.186:8443/wsrf/services/ReliableFileTransferService
>> [35]: https://10.10.80.186:8443/wsrf/services/RendezvousFactoryService
>> [36]: https://10.10.80.186:8443/wsrf/services/ReplicationService
>> [37]: https://10.10.80.186:8443/wsrf/services/SAMLAuthzTestService
>> [38]: https://10.10.80.186:8443/wsrf/services/SampleAuthzService
>> [39]: https://10.10.80.186:8443/wsrf/services/SecureCounterService
>> [40]: https://10.10.80.186:8443/wsrf/services/SecurityTestService
>> [41]: https://10.10.80.186:8443/wsrf/services/ShutdownService
>> [42]: https://10.10.80.186:8443/wsrf/services/SubscriptionManagerService
>> [43]: https://10.10.80.186:8443/wsrf/services/TestAuthzService
>> [44]: https://10.10.80.186:8443/wsrf/services/TestCASService
>> [45]: https://10.10.80.186:8443/wsrf/services/TestEnumService
>> [46]: https://10.10.80.186:8443/wsrf/services/TestLoginModuleService
>> [47]: https://10.10.80.186:8443/wsrf/services/TestPDPService
>> [48]: https://10.10.80.186:8443/wsrf/services/TestParamAuthzService
>> [49]: https://10.10.80.186:8443/wsrf/services/TestRPCService
>> [50]: https://10.10.80.186:8443/wsrf/services/TestService
>> [51]: https://10.10.80.186:8443/wsrf/services/TestServiceRequest
>> [52]: https://10.10.80.186:8443/wsrf/services/TestServiceWrongWSDL
>> [53]: https://10.10.80.186:8443/wsrf/services/TriggerFactoryService
>> [54]: https://10.10.80.186:8443/wsrf/services/TriggerRegistrationService
>> [55]:
>> https://10.10.80.186:8443/wsrf/services/TriggerRegistrationServiceEntry
>> [56]: https://10.10.80.186:8443/wsrf/services/TriggerService
>> [57]: https://10.10.80.186:8443/wsrf/services/Version
>> [58]: https://10.10.80.186:8443/wsrf/services/WidgetNotificationService
>> [59]: https://10.10.80.186:8443/wsrf/services/WidgetService
>> [60]: https://10.10.80.186:8443/wsrf/services/gsi/AuthenticationService
>> [61]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/execsource/IndexService
>> [62]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/execsource/IndexServiceEntry
>> [63]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/httpsource/IndexService
>> [64]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/httpsource/IndexServiceEntry
>> [65]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/subsource/IndexService
>> [66]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/subsource/IndexServiceEntry
>> [67]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/usefulrp/IndexService
>> [68]:
>> https://10.10.80.186:8443/wsrf/services/mds/test/usefulrp/IndexServiceEntry
>> 2010-05-03T12:47:40.022+01:00 ERROR container.ServiceThread
>> [ServiceThread-58,run:497] [JWSCORE-193] Unexpected error during
>> request processingnull
>> 2010-05-03T12:48:57.417+01:00 INFO
>> PersistentManagedExecutableJobResource.dac639d0-56a9-11df-aeca-9c6fdc015c43
>> [ServiceThread-58,start:761] Job dac639d0-56a9-11df-aeca-9c6fdc015c43
>> with client submission-id d99413f2-56a9-11df-8fc7-0013205351e8
>> accepted for local user 'nykibas'
>> 2010-05-03T12:48:59.741+01:00 WARN  helper.ProcessingFaultHelper
>> [pool-1-thread-3,createFaultFromErrorCode:233] Unhandled fault code
>> 201.
>> 2010-05-03T12:49:09.404+01:00 WARN  helper.CacheCleanUpHelper
>> [pool-1-thread-6,cacheCleanUp:55] Unable to do cache cleanup: script
>> command: cache_cleanup, error code: 201, script failure message:
>> Script stderr:
>> We trust you have received the usual lecture from the local
>> SystemAdministrator. It usually boils down to these three things:
>> #1) Respect the privacy of others.    #2) Think before you type.
>> #3) With great power comes great responsibility.[sudo] password for
>> globus:
>> 2010-05-03T12:49:10.509+01:00 INFO
>> handler.FinalizeTerminationStateHandler
>> [pool-1-thread-7,handleFailedState:100] Job
>> dac639d0-56a9-11df-aeca-9c6fdc015c43 failed. Fault #1: Description:
>> Error code: 201Script stderr:
>> We trust you have received the usual lecture from the local
>> SystemAdministrator. It usually boils down to these three things:
>> #1) Respect the privacy of others.    #2) Think before you type.
>> #3) With great power comes great responsibility.[sudo] password for
>> globus:  Cause: org.globus.exec.generated.FaultType: Error code:
>> 201Script stderr:
>> We trust you have received the usual lecture from the local
>> SystemAdministrator. It usually boils down to these three things:
>> #1) Respect the privacy of others.    #2) Think before you type.
>> #3) With great power comes great responsibility.[sudo] password for
>> globus:  caused by [0: org.oasis.wsrf.faults.BaseFaultType: Script
>> stderr:
>> We trust you have received the usual lecture from the local
>> SystemAdministrator. It usually boils down to these three things:
>> #1) Respect the privacy of others.    #2) Think before you type.
>> #3) With great power comes great responsibility.[sudo] password for
>> globus: ]
>>
>>
>> 2010/5/2, Lukasz Lacinski <[email protected]>:
>>> Hi Yannick,
>>>
>>> The Distinguish Name you use submitting the job (
>>> /O=Grid/OU=GlobusTest/OU=simpleCA-labo-debian.unikin.cd/OU=unikin.cd/CN=Yannick
>>> NZAU) is mapped on the user account "nykibas". Unfortunately the user
>>> account "nykibas" do not exist on the machine labo-debian.unikin.cd or
>>> the
>>> file /etc/passwd ois not readable by others. You have to create this user
>>> account or mapped the DN on an existing account or set permissions on
>>> /etc/passwd properly.
>>> If you find out what exactly causes the problem, please let us know.
>>>
>>> Regards,
>>> Lukasz
>>>
>>>
>>> On May 1, 2010, at 11:28 AM, Yannick Nzau wrote:
>>>
>>>> I  succeded to solve the previous problem! But I get now an other one.
>>>> I had created a new user. I get for him a certificate. But when I run
>>>> the
>>>> globus-ws, I get this error.
>>>>
>>>> nyki...@labo1-debian:~$ grid-proxy-init
>>>> Your identity: /O=Grid/OU=GlobusTest/OU=
>>>> simpleCA-labo-debian.unikin.cd/OU=unikin.cd/CN=Yannick NZAU
>>>> Enter GRID pass phrase for this identity:
>>>> Creating proxy ........................................................
>>>> Done
>>>> Your proxy is valid until: Sun May  2 04:40:56 2010
>>>> nyki...@labo1-debian:~$ globusrun-ws -submit -streaming -F
>>>> https://labo-debian.unikin.cd:8443/wsrf/services/ManagedJobFactoryService
>>>> -c
>>>> /usr/bin/whoami
>>>> Delegating user credentials...Done.
>>>> Submitting job...Done.
>>>> Job ID: uuid:0fb993c6-5538-11df-a7ba-0013205351e8
>>>> Termination time: 05/01/3010 15:41 GMT
>>>> Current job state: Failed
>>>> Destroying job...Done.
>>>> Cleaning up any delegated credentials...Done.
>>>> globusrun-ws: Job failed: Error code: 201Script stderr:
>>>> sudo: no passwd entry for nykibas!
>>>> globusrun-ws: Job failed: Staging error for RSL element
>>>> failureFileCleanUp.
>>>> Authentication with credential only failed on server
>>>> labo-debian.unikin.cd[Caused by: Server refused performing the
>>>> request. Custom message: Bad
>>>> password. (error code 1) [Nested exception message:  Custom message:
>>>> Unexpected reply: 530 Login incorrect. : Mapped user 'nykibas' is
>>>> invalid.]]
>>>>
>>>> PLEASE, HELP ME!
>>>>
>>>> this is the log of the container:
>>>> glo...@labo-debian:~$ globus-start-container
>>>> Starting SOAP server at https://10.10.80.186:8443/wsrf/services/
>>>> 2010-05-01T17:02:24.118+01:00 INFO  impl.DefaultIndexService
>>>> [ServiceThread-57,performDefaultRegistrations:261]
>>>> guid=edb60f40-553a-11df-9245-af2f8310ecca
>>>> event=org.globus.mds.index.performDefaultRegistrations.end status=0
>>>>
>>>> With the following services:
>>>>
>>>> [1]: https://10.10.80.186:8443/wsrf/services/AdminService
>>>> [2]: https://10.10.80.186:8443/wsrf/services/AttachmentTestService
>>>> [3]: https://10.10.80.186:8443/wsrf/services/AuthzCalloutTestService
>>>> [4]: https://10.10.80.186:8443/wsrf/services/CASService
>>>> [5]:
>>>> https://10.10.80.186:8443/wsrf/services/ContainerRegistryEntryService
>>>> [6]: https://10.10.80.186:8443/wsrf/services/ContainerRegistryService
>>>> [7]: https://10.10.80.186:8443/wsrf/services/CounterService
>>>> [8]: https://10.10.80.186:8443/wsrf/services/DefaultIndexService
>>>> [9]: https://10.10.80.186:8443/wsrf/services/DefaultIndexServiceEntry
>>>> [10]: https://10.10.80.186:8443/wsrf/services/DelegationFactoryService
>>>> [11]: https://10.10.80.186:8443/wsrf/services/DelegationService
>>>> [12]: https://10.10.80.186:8443/wsrf/services/DelegationTestService
>>>> [13]: https://10.10.80.186:8443/wsrf/services/DeployService
>>>> [14]: https://10.10.80.186:8443/wsrf/services/GKrellmService
>>>> [15]: https://10.10.80.186:8443/wsrf/services/InMemoryServiceGroup
>>>> [16]: https://10.10.80.186:8443/wsrf/services/InMemoryServiceGroupEntry
>>>> [17]:
>>>> https://10.10.80.186:8443/wsrf/services/InMemoryServiceGroupFactory
>>>> [18]: https://10.10.80.186:8443/wsrf/services/IndexFactoryService
>>>> [19]: https://10.10.80.186:8443/wsrf/services/IndexService
>>>> [20]: https://10.10.80.186:8443/wsrf/services/IndexServiceEntry
>>>> [21]: https://10.10.80.186:8443/wsrf/services/JWSCoreVersion
>>>> [22]: https://10.10.80.186:8443/wsrf/services/LoggingService
>>>> [23]:
>>>> https://10.10.80.186:8443/wsrf/services/ManagedExecutableJobService
>>>> [24]: https://10.10.80.186:8443/wsrf/services/ManagedJobFactoryService
>>>> [25]: https://10.10.80.186:8443/wsrf/services/ManagedMultiJobService
>>>> [26]: https://10.10.80.186:8443/wsrf/services/ManagementService
>>>> [27]:
>>>> https://10.10.80.186:8443/wsrf/services/NotificationConsumerFactoryService
>>>> [28]:
>>>> https://10.10.80.186:8443/wsrf/services/NotificationConsumerService
>>>> [29]: https://10.10.80.186:8443/wsrf/services/NotificationTestService
>>>> [30]:
>>>> https://10.10.80.186:8443/wsrf/services/PersistenceTestSubscriptionManager
>>>> [31]: https://10.10.80.186:8443/wsrf/services/QueryTestService
>>>> [32]: https://10.10.80.186:8443/wsrf/services/RPParamTestService
>>>> [33]:
>>>> https://10.10.80.186:8443/wsrf/services/ReliableFileTransferFactoryService
>>>> [34]:
>>>> https://10.10.80.186:8443/wsrf/services/ReliableFileTransferService
>>>> [35]: https://10.10.80.186:8443/wsrf/services/RendezvousFactoryService
>>>> [36]: https://10.10.80.186:8443/wsrf/services/ReplicationService
>>>> [37]: https://10.10.80.186:8443/wsrf/services/SAMLAuthzTestService
>>>> [38]: https://10.10.80.186:8443/wsrf/services/SampleAuthzService
>>>> [39]: https://10.10.80.186:8443/wsrf/services/SecureCounterService
>>>> [40]: https://10.10.80.186:8443/wsrf/services/SecurityTestService
>>>> [41]: https://10.10.80.186:8443/wsrf/services/ShutdownService
>>>> [42]: https://10.10.80.186:8443/wsrf/services/SubscriptionManagerService
>>>> [43]: https://10.10.80.186:8443/wsrf/services/TestAuthzService
>>>> [44]: https://10.10.80.186:8443/wsrf/services/TestCASService
>>>> [45]: https://10.10.80.186:8443/wsrf/services/TestEnumService
>>>> [46]: https://10.10.80.186:8443/wsrf/services/TestLoginModuleService
>>>> [47]: https://10.10.80.186:8443/wsrf/services/TestPDPService
>>>> [48]: https://10.10.80.186:8443/wsrf/services/TestParamAuthzService
>>>> [49]: https://10.10.80.186:8443/wsrf/services/TestRPCService
>>>> [50]: https://10.10.80.186:8443/wsrf/services/TestService
>>>> [51]: https://10.10.80.186:8443/wsrf/services/TestServiceRequest
>>>> [52]: https://10.10.80.186:8443/wsrf/services/TestServiceWrongWSDL
>>>> [53]: https://10.10.80.186:8443/wsrf/services/TriggerFactoryService
>>>> [54]: https://10.10.80.186:8443/wsrf/services/TriggerRegistrationService
>>>> [55]:
>>>> https://10.10.80.186:8443/wsrf/services/TriggerRegistrationServiceEntry
>>>> [56]: https://10.10.80.186:8443/wsrf/services/TriggerService
>>>> [57]: https://10.10.80.186:8443/wsrf/services/Version
>>>> [58]: https://10.10.80.186:8443/wsrf/services/WidgetNotificationService
>>>> [59]: https://10.10.80.186:8443/wsrf/services/WidgetService
>>>> [60]: https://10.10.80.186:8443/wsrf/services/gsi/AuthenticationService
>>>> [61]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/execsource/IndexService
>>>> [62]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/execsource/IndexServiceEntry
>>>> [63]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/httpsource/IndexService
>>>> [64]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/httpsource/IndexServiceEntry
>>>> [65]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/subsource/IndexService
>>>> [66]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/subsource/IndexServiceEntry
>>>> [67]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/usefulrp/IndexService
>>>> [68]:
>>>> https://10.10.80.186:8443/wsrf/services/mds/test/usefulrp/IndexServiceEntry
>>>> 2010-05-01T17:03:01.988+01:00 INFO
>>>> PersistentManagedExecutableJobResource.048041f0-553b-11df-9245-af2f8310ecca
>>>> [ServiceThread-57,start:761] Job 048041f0-553b-11df-9245-af2f8310ecca
>>>> with client submission-id 0253b6aa-553b-11df-8b8a-0013205351e8
>>>> accepted for local user 'nykibas'
>>>> 2010-05-01T17:03:02.503+01:00 WARN  helper.ProcessingFaultHelper
>>>> [pool-1-thread-3,createFaultFromErrorCode:233] Unhandled fault code
>>>> 201.
>>>> 2010-05-01T17:03:06.045+01:00 ERROR service.TransferWork
>>>> [Thread-9,oldLog:175] Transient transfer error
>>>> Authentication with credential only failed on server
>>>> labo-debian.unikin.cd [Caused by: Server refused performing the
>>>> request. Custom message: Bad password. (error code 1) [Nested
>>>> exception message:  Custom message: Unexpected reply: 530 Login
>>>> incorrect. : Mapped user 'nykibas' is invalid.]]
>>>> Authentication with credential only failed on server
>>>> labo-debian.unikin.cd. Caused by
>>>> org.globus.ftp.exception.ServerException: Server refused performing
>>>> the request. Custom message: Bad password. (error code 1) [Nested
>>>> exception message:  Custom message: Unexpected reply: 530 Login
>>>> incorrect. : Mapped user 'nykibas' is invalid.].  Nested exception is
>>>> org.globus.ftp.exception.UnexpectedReplyCodeException:  Custom
>>>> message: Unexpected reply: 530 Login incorrect. : Mapped user
>>>> 'nykibas' is invalid.
>>>>       at
>>>> org.globus.ftp.extended.GridFTPControlChannel.authenticate(GridFTPControlChannel.java:294)
>>>>       at
>>>> org.globus.ftp.GridFTPClient.authenticate(GridFTPClient.java:107)
>>>>       at
>>>> org.globus.ftp.GridFTPClient.authenticate(GridFTPClient.java:92)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.SingleConnectionImpl.<init>(SingleConnectionImpl.java:101)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.ConnectionManager.createNewConnection(ConnectionManager.java:328)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.ConnectionManager.getConnection(ConnectionManager.java:191)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.ConnectionManager.getConnection(ConnectionManager.java:128)
>>>>       at
>>>> org.globus.transfer.reliable.service.client.DeleteClient.<init>(DeleteClient.java:43)
>>>>       at
>>>> org.globus.transfer.reliable.service.client.ClientFactory.createDeleteClient(ClientFactory.java:62)
>>>>       at
>>>> org.globus.transfer.reliable.service.TransferWork.run(TransferWork.java:348)
>>>>       at
>>>> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
>>>> Source)
>>>>       at java.lang.Thread.run(Thread.java:636)
>>>> 2010-05-01T17:03:09.035+01:00 WARN  helper.CacheCleanUpHelper
>>>> [pool-1-thread-6,cacheCleanUp:55] Unable to do cache cleanup: script
>>>> command: cache_cleanup, error code: 201, script failure message:
>>>> Script stderr:
>>>> sudo: no passwd entry for nykibas!
>>>> 2010-05-01T17:03:10.320+01:00 INFO
>>>> handler.FinalizeTerminationStateHandler
>>>> [pool-1-thread-7,handleFailedState:100] Job
>>>> 048041f0-553b-11df-9245-af2f8310ecca failed. Fault #1: Description:
>>>> Error code: 201Script stderr:
>>>> sudo: no passwd entry for nykibas! Cause:
>>>> org.globus.exec.generated.FaultType: Error code: 201Script stderr:
>>>> sudo: no passwd entry for nykibas! caused by [0:
>>>> org.oasis.wsrf.faults.BaseFaultType: Script stderr:
>>>> sudo: no passwd entry for nykibas!] Fault #2: Description: Staging
>>>> error for RSL element failureFileCleanUp. Authentication with
>>>> credential only failed on server labo-debian.unikin.cd [Caused by:
>>>> Server refused performing the request. Custom message: Bad password.
>>>> (error code 1) [Nested exception message:  Custom message: Unexpected
>>>> reply: 530 Login incorrect. : Mapped user 'nykibas' is invalid.]]
>>>> Cause: org.globus.exec.generated.StagingFaultType: Staging error for
>>>> RSL element failureFileCleanUp. Authentication with credential only
>>>> failed on server labo-debian.unikin.cd [Caused by: Server refused
>>>> performing the request. Custom message: Bad password. (error code 1)
>>>> [Nested exception message:  Custom message: Unexpected reply: 530
>>>> Login incorrect. : Mapped user 'nykibas' is invalid.]]
>>>> 2010-05-01T17:03:10.829+01:00 ERROR service.TransferWork
>>>> [Thread-7,oldLog:175] Transient transfer error
>>>> Authentication with credential only failed on server
>>>> labo-debian.unikin.cd [Caused by: Server refused performing the
>>>> request. Custom message: Bad password. (error code 1) [Nested
>>>> exception message:  Custom message: Unexpected reply: 530 Login
>>>> incorrect. : Mapped user 'nykibas' is invalid.]]
>>>> Authentication with credential only failed on server
>>>> labo-debian.unikin.cd. Caused by
>>>> org.globus.ftp.exception.ServerException: Server refused performing
>>>> the request. Custom message: Bad password. (error code 1) [Nested
>>>> exception message:  Custom message: Unexpected reply: 530 Login
>>>> incorrect. : Mapped user 'nykibas' is invalid.].  Nested exception is
>>>> org.globus.ftp.exception.UnexpectedReplyCodeException:  Custom
>>>> message: Unexpected reply: 530 Login incorrect. : Mapped user
>>>> 'nykibas' is invalid.
>>>>       at
>>>> org.globus.ftp.extended.GridFTPControlChannel.authenticate(GridFTPControlChannel.java:294)
>>>>       at
>>>> org.globus.ftp.GridFTPClient.authenticate(GridFTPClient.java:107)
>>>>       at
>>>> org.globus.ftp.GridFTPClient.authenticate(GridFTPClient.java:92)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.SingleConnectionImpl.<init>(SingleConnectionImpl.java:101)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.ConnectionManager.createNewConnection(ConnectionManager.java:328)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.ConnectionManager.getConnection(ConnectionManager.java:191)
>>>>       at
>>>> org.globus.transfer.reliable.service.cache.ConnectionManager.getConnection(ConnectionManager.java:128)
>>>>       at
>>>> org.globus.transfer.reliable.service.client.DeleteClient.<init>(DeleteClient.java:43)
>>>>       at
>>>> org.globus.transfer.reliable.service.client.ClientFactory.createDeleteClient(ClientFactory.java:62)
>>>>       at
>>>> org.globus.transfer.reliable.service.TransferWork.run(TransferWork.java:348)
>>>>       at
>>>> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
>>>> Source)
>>>>       at java.lang.Thread.run(Thread.java:636)
>>>>
>>>>
>>>> --
>>>> Yannick NZAU KIBASONGA
>>>> 3614 HOME 30 UNIKIN
>>>> 2x, Av. Yakawumbu Q./ Musey
>>>> BINZA-OZONE C./ NGALIEMA
>>>> (+243)0899468921-0810632471
>>>
>>>
>>
>>
>> --
>> Yannick NZAU KIBASONGA
>> 3614 HOME 30 UNIKIN
>> 2x, Av. Yakawumbu Q./ Musey
>> BINZA-OZONE C./ NGALIEMA
>> (+243)0899468921-0810632471
>
>


-- 
Yannick NZAU KIBASONGA
3614 HOME 30 UNIKIN
2x, Av. Yakawumbu Q./ Musey
BINZA-OZONE C./ NGALIEMA
(+243)0899468921-0810632471

Reply via email to