I managed to get a packet capture when the error happened and have figured out what the issue is.
The issue appears to be that PM opens an SFTP session to the server and does not close the session. Presumably it keeps it open under the premise that if you were to upload additional images it would be quicker. However, what I saw was that the end user did an upload at the 11am hour. I saw in the server logs that the session was closed by the server later in that hour. Then at the 3pm hour the user attempted to upload an additional image. At that point I saw PM attempt to use what it thought was an existing SFTP session. Since the server had long since closed the session it naturally errored out and unfortunately PM seems to not attempt to reconnect for that specific image upload.
Other than coaching the user to close the upload task, is there a setting in PM to have it immediately close or auto-close an idle session? As it stands the end user has the impression that the server errored, when in fact PM was trying to use a long since closed session.
If you'd like to replicate the issue, then follow these steps:
1. In PM, upload an image and do not close the task.
2. On the SFTP server, kill the ssh process. Either that or wait for the server to timeout. In the case of a default openssh on CentOS, it appears to be 30 minutes.
3. On PM, attempt to upload an image. It should error out.
Thanks!
