AFT - Resource temporarily unavailable

[baralem]

We're having an aleatory issue with AFT transfers. Transfers are cancelling sometimes and job's log shows that the job disappeared.

Agent and server are on the same host. AFT transfers are made to other servers.
Platform: HP-UX B.11.23 U ia64 (cluster)
Agent version: 6.3.01.300
AFT version: 6.3.01.000
Server version: 6.3.01.401

The job cancels and job's log shows:
17/02/10 08:00:16 TR5120 JOB STATE CHANGED TO Executing
==>17/02/10 08:31:57 TR5102 DISAPPEARED AT 20100217083157. RUNCNT 1
17/02/10 08:31:57 TR5134 ENDED NOTOK
17/02/10 08:31:57 TR5120 JOB STATE CHANGED TO Analyzed
17/02/10 08:31:57 SL5120 JOB STATE CHANGED TO Post processed

AFT log with Diagnostic Level ON shows aleatory error "Resource temporarily unavailable":
0217 11:22:47:404 Transferred: 0 Elapsed: 0sec Percent: 0 status: In Progress
==>0217 11:22:51:374 Resource temporarily unavailable
==>0217 11:22:53:204 Resource temporarily unavailable
==>0217 11:22:55:934 Resource temporarily unavailable
==>0217 11:22:56:844 Resource temporarily unavailable
==>0217 11:22:56:914 Resource temporarily unavailable
0217 11:22:57:084 Transferred: 2232320 Elapsed: 10sec Percent: 0 status: In Progress
0217 11:23:05:484 Transferred: 4509696 Elapsed: 18sec Percent: 1 status: In Progress
==>0217 11:23:13:554 Resource temporarily unavailable
0217 11:23:15:014 Transferred: 7380992 Elapsed: 28sec Percent: 1 status: In Progress

AT log shows:
>>> Start dump buffer 1 [0]
>>> End dump buffer 1
>>> Start dump buffer 0 [97]
==>0217 09:23:16:11 AT:AG_watch_check_status - return DISAPPEARED from CM for file 19gqf_0003.dsect
>>> End dump buffer 0
>>> Start dump buffer 1 [0]
>>> End dump buffer 1
>>> Start dump buffer 0 [97]
==>0217 10:51:23:73 AT:AG_watch_check_status - return DISAPPEARED from CM for file 19gqf_0004.dsect
>>> End dump buffer 0

Any clue?
Thanks in advance.

martin.

[hipikll]

During the time of transfer, were your nodes (from you are copying and the targed host) available?
It seems like agent was temporary down. ... or?

[Nigel]

Hi Martin

Did you manage to resolve this issue?

I have seen it before. We upgraded ssh on the machines. It worked for some but for others we still get the error.

It's exactly the same symptoms as you are having