Exit Status 0 After Connection Issues
Hi,
I'm using WinSCP from the command line. We recently had issues with uploading files to an endpoint where their server allowed our connection but then could not continue due to issues on their end.
Both log files had "Waiting for data timed out, asking user what to do" after the "Connected to " the remote host IP address. One time the last message in the log file was "Script: Server unexpectedly closed network connection", the other time it was "Script: Timeout waiting for server to respond".
The business partner that receives these files acknowledged they were having some issues, and these problems appear to have been resolved.
My question is, why did WinSCP return a status 0 on exit when these issues happened? Neither log file included the normal "Script: Exit code 0" or "Session sent command exit status 0", but the application's exit status code was 0 so our check in the script did not alert us to the errors.
Thanks,
JamesB
I'm using WinSCP from the command line. We recently had issues with uploading files to an endpoint where their server allowed our connection but then could not continue due to issues on their end.
Both log files had "Waiting for data timed out, asking user what to do" after the "Connected to " the remote host IP address. One time the last message in the log file was "Script: Server unexpectedly closed network connection", the other time it was "Script: Timeout waiting for server to respond".
The business partner that receives these files acknowledged they were having some issues, and these problems appear to have been resolved.
My question is, why did WinSCP return a status 0 on exit when these issues happened? Neither log file included the normal "Script: Exit code 0" or "Session sent command exit status 0", but the application's exit status code was 0 so our check in the script did not alert us to the errors.
Thanks,
JamesB
