remote open("X to Y"): Failure error is not failed in Automic Workload Automation

[SUBHA KRISHNA PRIYA DHARSINI]

Hi Team,

We could see the below error message that runs on unix agent box and the automic WLA V12 is failed to indicate the failure notification, inturn the job got completed successfully with the status "Ended_Ok-ended normally" with exit status code 0(0 is the success code for this job). We are receiving the notification for the other errors for the same job.

Please let us know is that any parameters that needs to address from automic end and also any fix for this issue.

sftp> put /uc4sftp/PRD/dwftp/upload/XXX.csv
Uploading /uc4sftp/PRD/dwftp/upload/XXX.csv to YYY.csv
remote open("/xommon/ftpuserdist/prod/daily/dob/XXX.csv"): Failure

debug1: client_input_channel_req: channel 0 rtype exit-status reply 0

debug1: channel 0: free: client-session, nchannels 1

debug1: fd 0 clearing O_NONBLOCK

debug1: fd 2 clearing O_NONBLOCK

Transferred: sent 4368, received 3064 bytes, in 0.1 seconds

Bytes per second: sent 59706.4, received 41881.9

debug1: Exit status 0

[Carsten Schmitz]

Hi.

This doesn't look like the RA agent or anything, it looks like you are doing a scripted SFTP transfer from within Automic, using the sftp client native on your machine.

Thus, this problem as frankly nothing to do with Automic​. It appears your native sftp client can't transfer the file to the target destination. It will probably fail just the same if you were to do this without any Automic at all. Maybe the target directory doesn't exist, maybe the file already exists and is write protected or some other permission issue. There is insufficient information here to determine the exact cause.

> Automic failed to indicate the failure notification

The sftp command returns a status code of zero, as demonstrated in the last line of your output. Automic can't do anything about this - zero means ENDED_OK by default. The fault, if anything, lies with the client program (sftp client). You CAN tell Automic to interpret a return code of zero as a failure, but you don't want to do that here; otherwise you'd treat even a successfull sftp transfer as a failure with no way to reasonably distinguish between them (you could solve this with an "output scan" but I don't think this would be very advisable, either).

I'm afraid it looks to me you need to diagnose your sftp client or destination file system issues, and everything else should then fall into place.

Best regards,
Carsten

[SUBHA KRISHNA PRIYA DHARSINI]

Thankyou Carsten for your response. It helps us to sort the issue from application server and not from Automic.

[Carsten Schmitz]

​Hi,

You are welcome, and thanks for the update :)