12:24:47.061 Getting current directory name. 12:24:44.217 Startup conversation with host finished. 12:24:43.936 Doing startup conversation with host. 12:24:41.483 Initialised HMAC-SHA1 server->client MAC algorithm 12:24:41.483 Initialised AES-256 CBC server->client encryption 12:24:41.421 Initialised HMAC-SHA1 client->server MAC algorithm 12:24:41.421 Initialised AES-256 CBC client->server encryption 12:24:41.186 Doing Diffie-Hellman key exchange with hash SHA-1 12:24:41.186 Using Diffie-Hellman with standard group "group1" 12:24:41.139 Using SSH protocol version 2 12:24:41.139 GSSKEX disabled: The operation completed successfully. 12:24:41.139 Cannot convert IP address to SPN: DNS is not trusted 12:24:41.139 SSPI: acquired credentials for: user 12:24:40.952 Cache directory changes: Yes, Permanent: Yes 12:24:40.952 Local directory: D:\Programe\WinSCP\winscp419, Remote directory: home, Update: No, Cache: Yes 12:24:40.952 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes 12:24:40.952 Return code variable: Autodetect Lookup user groups: Yes 12:24:40.952 Ciphers: aes,blowfish,3des,WARN,arcfour,des Ssh2DES: No 12:24:40.952 Try agent: Yes Agent forwarding: No TIS/CryptoCard: No KI: Yes GSSAPI: No 12:24:40.952 SSH protocol version: 2 Compression: No 12:24:40.952 User name: down (Password: Yes, Key file: No) I retrieve the same error for version 419 and 423beta. When the abnormal program termination box pops up 11:54:12.942 Fatal error while disposing the SFTP queue. 11:54:12.942 Attempt to close connection due to fatal exception: 11:54:12.942 Host has not answered for 300 seconds. 11:54:12.942 Waiting for data timed out, asking user what to do. 11:49:12.837 Binary transfer mode selected. This is a terrific program by the way, and we have found the synchonize feature to be indispensable. Would it be possible to revisit and hotfix this problem? Instead of a code 4 being returned to the DOS batch caller, we are getting a dialog box indicating there was an Abnormal program Termination which effectively stalls our automated process (it runs at 11 pm in evening).Ī google search indicates that this issue was raised a couple years back. Since the disk quota is beyond our control, our immediate concern is being able to trap the error. We are trying to PUT data to an SFTP site via script, but we suspect we've maxed out our disk quota so we are getting an SSH status/error code of 4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |