error code 4 (server failure)
- Reply to topic
- Log in
Advertisement
-
mdude
Guest
2004-11-05 06:58
Hi all. When I try connecting to WinSCP (Win XP Pro) I am able to connect, but whenever I try to add folders to my server or upload any files, I receive the following error:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 14
Does anyone know the root of this? I exited my firewall, and other people can connect to the server with different usernames and passwords (I am accessing a college shared network). Thank you.
—Scott
Reply with quote
Advertisement
- Guest
2004-11-05 07:00
Hi all. When I try connecting to WinSCP (Win XP Pro) I am able to connect, but whenever I try to add folders to my server or upload any files, I receive the following error:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 14Does anyone know the root of this? I exited my firewall, and other people can connect to the server with different usernames and passwords (I am accessing a college shared network). Thank you.
—Scott
Sorry all for the duplicate post. The error I receive when trying to upload files is:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 6
The request code is 14 when I try to create new folders. Sorry again!
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2004-11-05
Only thing I can think of is some permissions problem. Can you upload files with other SCP/SFTP clients (even some command-line like PSCP from Putty package).
Reply with quote
-
Brian
Guest
2004-11-05 09:25
martin wrote:
Only thing I can think of is some permissions problem. Can you upload files with other SCP/SFTP clients (even some command-line like PSCP from Putty package).
Hi, this is actually the person with the problem, my friend was just posting for me at the time.
I tried uploading the web pages and the changes I made using Macromedia Dreamweaver and it gets the error as well.
No settings have been changed since it was able to last upload/update files.
Any other suggestions?
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2004-11-05
Brian wrote:
Hi, this is actually the person with the problem, my friend was just posting for me at the time.
I tried uploading the web pages and the changes I made using Macromedia Dreamweaver and it gets the error as well.
No settings have been changed since it was able to last upload/update files.
Any other suggestions?
And are you able to write the files if you login using terminal. Also try SCP protocol, maybe it will display more meaningful message.
Reply with quote
Advertisement
-
Rafi
Guest
2004-11-18 22:52
We had the exact same error, and after checking permissions and other things, it turned to be a simple problem …. filesystem was 100% full 
Good luck!
martin wrote:
Brian wrote:
Hi, this is actually the person with the problem, my friend was just posting for me at the time.
I tried uploading the web pages and the changes I made using Macromedia Dreamweaver and it gets the error as well.
No settings have been changed since it was able to last upload/update files.
Any other suggestions?
And are you able to write the files if you login using terminal. Also try SCP protocol, maybe it will display more meaningful message.
Reply with quote
-
martin◆
Site Admin -
2004-11-19
Rafi wrote:
We had the exact same error, and after checking permissions and other things, it turned to be a simple problem …. filesystem was 100% full
Thanks for info!! I can help other users. Unfortunatelly OpenSSH SFTP servers have terrible error reporting.
Reply with quote
-
martin◆
Site Admin -
2009-01-04
See documentation for possible reasons you may be getting the error.
Reply with quote
-
PublisherGuest1230
Guest
2009-07-09 21:46
Hello,
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. (see log excerpt below).
Since the disk quota is beyond our control, our immediate concern is being able to trap the error. 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).
A google search indicates that this issue was raised a couple years back. Would it be possible to revisit and hotfix this problem?
This is a terrific program by the way, and we have found the synchonize feature to be indispensable.
We’re running Windows Server 2003 SP2.
Thank you.
—LOG FILE EXCERPT START
. 2009-07-09 11:49:12.837 Binary transfer mode selected.
. 2009-07-09 11:49:12.837 Checking existence of file.
> 2009-07-09 11:49:12.837 Type: SSH_FXP_LSTAT, Size: 79, Number: 263
< 2009-07-09 11:49:12.853 Type: SSH_FXP_STATUS, Size: 29, Number: 263
< 2009-07-09 11:49:12.853 Status/error code: 2
. 2009-07-09 11:49:12.853 Checking existence of partially transfered file.
> 2009-07-09 11:49:12.853 Type: SSH_FXP_LSTAT, Size: 88, Number: 519
< 2009-07-09 11:49:12.884 Type: SSH_FXP_ATTRS, Size: 37, Number: 519
. 2009-07-09 11:49:12.884 Resuming file transfer.
. 2009-07-09 11:49:12.884 Opening remote file.
> 2009-07-09 11:49:12.884 Type: SSH_FXP_OPEN, Size: 96, Number: 771
< 2009-07-09 11:49:12.884 Type: SSH_FXP_HANDLE, Size: 13, Number: 771
> 2009-07-09 11:49:12.884 Type: SSH_FXP_WRITE, Size: 4121, Number: 1286
< 2009-07-09 11:49:12.946 Status/error code: 4, Message: 2566, Server: Failure, Language:
. 2009-07-09 11:54:12.942 Waiting for data timed out, asking user what to do.
. 2009-07-09 11:54:12.942 Asking user:
. 2009-07-09 11:54:12.942 Host has not answered for 300 seconds.
. 2009-07-09 11:54:12.942
. 2009-07-09 11:54:12.942 Wait for another 300 seconds? ()
. 2009-07-09 11:54:12.942 Attempt to close connection due to fatal exception:
* 2009-07-09 11:54:12.942 Terminated by user.
. 2009-07-09 11:54:12.942 Closing connection.
. 2009-07-09 11:54:12.942 Sending special code: 12
. 2009-07-09 11:54:12.942 Sent EOF message
. 2009-07-09 11:54:12.942 Fatal error while disposing the SFTP queue.
—When the abnormal program termination box pops up
—LOG FILE EXCERPT END
Reply with quote
Advertisement
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2009-07-10
PublisherGuest1230 wrote:
Since the disk quota is beyond our control, our immediate concern is being able to trap the error. 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).
What version of WinSCP are you using? Have you tried the latest one? If you are able reproduce the problem with the latest one, can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.
You will find my address (if you log in) in my forum profile.
Reply with quote
-
Guest
Guest
2009-07-10 13:40
Version 4.1.9 Build 416
Thanks.
Reply with quote
-
martin◆
Site Admin -
2009-07-13
Can you try 4.2.2 beta?
Reply with quote
-
guest
Guest
2009-07-14 15:14
I try to download some files from a HP NonStop System.
I’m able to download files witch are stored on the server as ASCII files, but when I try to download files stored as binary I receive the following error:
Copying files from remote side failed.
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 5
I try to download same file using FileZilla and WS_FTP Pro and both of them work fine.
Is there some settings that I must use to download these files ?
Reply with quote
Advertisement
-
martin◆
Site Admin -
2009-07-15
Please post a log file.
Reply with quote
-
guest
Guest
2009-08-26 10:50
Please see bellow the log for this.
I retrieve the same error for version 419 and 423beta.
. 2009-08-26 12:24:40.952 —————————————————————————
. 2009-08-26 12:24:40.952 WinSCP Version 4.1.9 (Build 416) (OS 5.1.2600 Service Pack 2)
. 2009-08-26 12:24:40.952 Login time: Wednesday, August 26, 2009 12:24:40 PM
. 2009-08-26 12:24:40.952 —————————————————————————
. 2009-08-26 12:24:40.952 Session name: down@10.10.7.21
. 2009-08-26 12:24:40.952 Host name: 10.10.7.17 (Port: 22)
. 2009-08-26 12:24:40.952 User name: down (Password: Yes, Key file: No)
. 2009-08-26 12:24:40.952 Tunnel: No
. 2009-08-26 12:24:40.952 Transfer Protocol: SFTP (SCP)
. 2009-08-26 12:24:40.952 Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. 2009-08-26 12:24:40.952 Proxy: none
. 2009-08-26 12:24:40.952 SSH protocol version: 2; Compression: No
. 2009-08-26 12:24:40.952 Bypass authentication: No
. 2009-08-26 12:24:40.952 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. 2009-08-26 12:24:40.952 Ciphers: aes,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2009-08-26 12:24:40.952 SSH Bugs: -,-,-,-,-,-,-,-
. 2009-08-26 12:24:40.952 SFTP Bugs: -,-
. 2009-08-26 12:24:40.952 Return code variable: Autodetect; Lookup user groups: Yes
. 2009-08-26 12:24:40.952 Shell: default, EOL: 0
. 2009-08-26 12:24:40.952 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. 2009-08-26 12:24:40.952 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2009-08-26 12:24:40.952 Local directory: D:ProgrameWinSCPwinscp419, Remote directory: home, Update: No, Cache: Yes
. 2009-08-26 12:24:40.952 Cache directory changes: Yes, Permanent: Yes
. 2009-08-26 12:24:40.952 DST mode: 1
. 2009-08-26 12:24:40.952 —————————————————————————
. 2009-08-26 12:24:40.983 Looking up host «10.10.7.17»
. 2009-08-26 12:24:40.983 Connecting to 10.10.7.17 port 22
. 2009-08-26 12:24:41.124 Server version: SSH-2.0-1.36 sshlib: T9999G06_15Apr2008_comForte_SSH2_0079
. 2009-08-26 12:24:41.124 We claim version: SSH-2.0-WinSCP_release_4.1.9
. 2009-08-26 12:24:41.139 SSPI: acquired credentials for: user
. 2009-08-26 12:24:41.139 Cannot convert IP address to SPN: DNS is not trusted
. 2009-08-26 12:24:41.139 GSSKEX disabled: The operation completed successfully.. 2009-08-26 12:24:41.139 Using SSH protocol version 2
. 2009-08-26 12:24:41.186 Using Diffie-Hellman with standard group «group1»
. 2009-08-26 12:24:41.186 Doing Diffie-Hellman key exchange with hash SHA-1
. 2009-08-26 12:24:41.421 Host key fingerprint is:
. 2009-08-26 12:24:41.421 ssh-dss 1024 22:a3:1e:60:52:95:11:62:be:5a:60:4c:7f:75:f5:04
. 2009-08-26 12:24:41.421 Initialised AES-256 CBC client->server encryption
. 2009-08-26 12:24:41.421 Initialised HMAC-SHA1 client->server MAC algorithm
. 2009-08-26 12:24:41.483 Initialised AES-256 CBC server->client encryption
. 2009-08-26 12:24:41.483 Initialised HMAC-SHA1 server->client MAC algorithm
! 2009-08-26 12:24:41.530 Using username «down».
. 2009-08-26 12:24:41.624 Prompt (6, SSH password, , &Password: )
. 2009-08-26 12:24:41.624 Using stored password.
. 2009-08-26 12:24:41.624 Sent password
. 2009-08-26 12:24:42.905 Access granted
. 2009-08-26 12:24:42.967 Opened channel for session
. 2009-08-26 12:24:43.921 Started a shell/command
. 2009-08-26 12:24:43.921 —————————————————————————
. 2009-08-26 12:24:43.921 Using SFTP protocol.
. 2009-08-26 12:24:43.936 Doing startup conversation with host.
> 2009-08-26 12:24:43.936 Type: SSH_FXP_INIT, Size: 5, Number: -1
< 2009-08-26 12:24:43.983 Type: SSH_FXP_VERSION, Size: 5, Number: -1
. 2009-08-26 12:24:43.983 SFTP version 3 negotiated.
. 2009-08-26 12:24:43.983 We believe the server has signed timestamps bug
. 2009-08-26 12:24:43.983 We will use UTF-8 strings for status messages only
. 2009-08-26 12:24:43.983 Getting current directory name.
. 2009-08-26 12:24:43.983 Getting real path for ‘.’
> 2009-08-26 12:24:43.983 Type: SSH_FXP_REALPATH, Size: 10, Number: 16
< 2009-08-26 12:24:44.046 Type: SSH_FXP_NAME, Size: 55, Number: 16
. 2009-08-26 12:24:44.046 Real path is ‘upl’
. 2009-08-26 12:24:44.046 Listing directory «upl».
> 2009-08-26 12:24:44.046 Type: SSH_FXP_OPENDIR, Size: 26, Number: 267
< 2009-08-26 12:24:44.108 Type: SSH_FXP_HANDLE, Size: 13, Number: 267
> 2009-08-26 12:24:44.108 Type: SSH_FXP_READDIR, Size: 13, Number: 524
< 2009-08-26 12:24:44.171 Type: SSH_FXP_NAME, Size: 455, Number: 524
> 2009-08-26 12:24:44.171 Type: SSH_FXP_READDIR, Size: 13, Number: 780
< 2009-08-26 12:24:44.217 Type: SSH_FXP_STATUS, Size: 28, Number: 780
< 2009-08-26 12:24:44.217 Status/error code: 1
> 2009-08-26 12:24:44.217 Type: SSH_FXP_CLOSE, Size: 13, Number: 1028
. 2009-08-26 12:24:44.217 Startup conversation with host finished.
. 2009-08-26 12:24:47.061 Cached directory change via «/G» to «/G».
. 2009-08-26 12:24:47.061 Getting current directory name.
. 2009-08-26 12:24:47.061 Listing directory «/G».
> 2009-08-26 12:24:47.061 Type: SSH_FXP_OPENDIR, Size: 11, Number: 1291
< 2009-08-26 12:24:47.061 Type: SSH_FXP_STATUS, Size: 24, Number: 1028
. 2009-08-26 12:24:47.061 Discarding reserved response
< 2009-08-26 12:24:47.124 Type: SSH_FXP_HANDLE, Size: 13, Number: 1291
> 2009-08-26 12:24:47.124 Type: SSH_FXP_READDIR, Size: 13, Number: 1548
< 2009-08-26 12:24:47.952 Type: SSH_FXP_NAME, Size: 10787, Number: 1548
> 2009-08-26 12:24:47.952 Type: SSH_FXP_READDIR, Size: 13, Number: 1804
< 2009-08-26 12:24:48.358 Type: SSH_FXP_NAME, Size: 10809, Number: 1804
> 2009-08-26 12:24:48.358 Type: SSH_FXP_READDIR, Size: 13, Number: 2060
< 2009-08-26 12:24:48.780 Type: SSH_FXP_NAME, Size: 10807, Number: 2060
> 2009-08-26 12:24:48.780 Type: SSH_FXP_READDIR, Size: 13, Number: 2316
< 2009-08-26 12:24:49.030 Type: SSH_FXP_NAME, Size: 3029, Number: 2316
> 2009-08-26 12:24:49.030 Type: SSH_FXP_READDIR, Size: 13, Number: 2572
< 2009-08-26 12:24:49.092 Type: SSH_FXP_STATUS, Size: 28, Number: 2572
< 2009-08-26 12:24:49.092 Status/error code: 1
> 2009-08-26 12:24:49.092 Type: SSH_FXP_CLOSE, Size: 13, Number: 2820
. 2009-08-26 12:24:54.702 Cached directory change via «bpbu01» to «upl».
. 2009-08-26 12:24:54.702 Getting current directory name.
. 2009-08-26 12:24:54.702 Listing directory «upl».
> 2009-08-26 12:24:54.702 Type: SSH_FXP_OPENDIR, Size: 18, Number: 3083
< 2009-08-26 12:24:54.702 Type: SSH_FXP_STATUS, Size: 24, Number: 2820
. 2009-08-26 12:24:54.702 Discarding reserved response
< 2009-08-26 12:24:54.858 Type: SSH_FXP_HANDLE, Size: 13, Number: 3083
> 2009-08-26 12:24:54.858 Type: SSH_FXP_READDIR, Size: 13, Number: 3340
< 2009-08-26 12:24:54.952 Type: SSH_FXP_NAME, Size: 1339, Number: 3340
> 2009-08-26 12:24:54.952 Type: SSH_FXP_READDIR, Size: 13, Number: 3596
< 2009-08-26 12:24:54.999 Type: SSH_FXP_STATUS, Size: 28, Number: 3596
< 2009-08-26 12:24:54.999 Status/error code: 1
> 2009-08-26 12:24:54.999 Type: SSH_FXP_CLOSE, Size: 13, Number: 3844
. 2009-08-26 12:24:58.874 Cached directory change via «dbn» to «upl/dbn».
. 2009-08-26 12:24:58.874 Getting current directory name.
. 2009-08-26 12:24:58.874 Listing directory «upl/dbn».
> 2009-08-26 12:24:58.874 Type: SSH_FXP_OPENDIR, Size: 26, Number: 4107
< 2009-08-26 12:24:58.874 Type: SSH_FXP_STATUS, Size: 24, Number: 3844
. 2009-08-26 12:24:58.874 Discarding reserved response
< 2009-08-26 12:24:58.952 Type: SSH_FXP_HANDLE, Size: 13, Number: 4107
> 2009-08-26 12:24:58.952 Type: SSH_FXP_READDIR, Size: 13, Number: 4364
< 2009-08-26 12:24:59.217 Type: SSH_FXP_NAME, Size: 11205, Number: 4364
> 2009-08-26 12:24:59.217 Type: SSH_FXP_READDIR, Size: 13, Number: 4620
< 2009-08-26 12:24:59.921 Type: SSH_FXP_NAME, Size: 11203, Number: 4620
> 2009-08-26 12:24:59.921 Type: SSH_FXP_READDIR, Size: 13, Number: 4876
< 2009-08-26 12:25:00.327 Type: SSH_FXP_NAME, Size: 11204, Number: 4876
> 2009-08-26 12:25:00.327 Type: SSH_FXP_READDIR, Size: 13, Number: 5132
< 2009-08-26 12:25:00.561 Type: SSH_FXP_NAME, Size: 6618, Number: 5132
> 2009-08-26 12:25:00.561 Type: SSH_FXP_READDIR, Size: 13, Number: 5388
< 2009-08-26 12:25:00.608 Type: SSH_FXP_STATUS, Size: 28, Number: 5388
< 2009-08-26 12:25:00.608 Status/error code: 1
> 2009-08-26 12:25:00.608 Type: SSH_FXP_CLOSE, Size: 13, Number: 5636
. 2009-08-26 12:25:06.327 File: «upl/dbn/test»
. 2009-08-26 12:25:06.327 Copying «upl/dbn/test» to local directory started.
. 2009-08-26 12:25:06.327 Binary transfer mode selected.
. 2009-08-26 12:25:06.327 Checking existence of partially transfered file.
. 2009-08-26 12:25:06.327 Opening remote file.
> 2009-08-26 12:25:06.327 Type: SSH_FXP_OPEN, Size: 43, Number: 5891
< 2009-08-26 12:25:06.327 Type: SSH_FXP_STATUS, Size: 24, Number: 5636
. 2009-08-26 12:25:06.327 Discarding reserved response
< 2009-08-26 12:25:06.639 Type: SSH_FXP_HANDLE, Size: 13, Number: 5891
> 2009-08-26 12:25:06.639 Type: SSH_FXP_FSTAT, Size: 13, Number: 6152
> 2009-08-26 12:25:06.639 Type: SSH_FXP_READ, Size: 25, Number: 6405
. 2009-08-26 12:25:06.702 3 skipped SSH_FXP_WRITE, SSH_FXP_READ, SSH_FXP_DATA and SSH_FXP_STATUS packets.
< 2009-08-26 12:25:06.702 Type: SSH_FXP_ATTRS, Size: 37, Number: 6152
. 2009-08-26 12:25:06.702 Storing reserved response
< 2009-08-26 12:25:07.061 Status/error code: 4, Message: 8197, Server: Failure, Language:
. 2009-08-26 12:25:07.249 18 skipped SSH_FXP_WRITE, SSH_FXP_READ, SSH_FXP_DATA and SSH_FXP_STATUS packets.
> 2009-08-26 12:25:07.249 Type: SSH_FXP_CLOSE, Size: 13, Number: 9220
* 2009-08-26 12:25:07.249 (ECommand) Copying files from remote side failed.
* 2009-08-26 12:25:07.249 General failure (server should provide error description).
* 2009-08-26 12:25:07.249 Error code: 4
* 2009-08-26 12:25:07.249 Error message from server: Failure
* 2009-08-26 12:25:07.249 Request code: 5
. 2009-08-26 12:25:10.311 Closing connection.
. 2009-08-26 12:25:10.311 Sending special code: 12
. 2009-08-26 12:25:10.311 Sent EOF message
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2009-08-31
guest wrote:
Please see bellow the log for this.
I retrieve the same error for version 419 and 423beta.
…
You wrote about download before. But the log shows upload. So is it upload? Can you post a log file from Filezilla as well?
Reply with quote
-
Guest
Guest
2009-10-27 16:20
Hello,
Bellow you can find log from WinSCP 419, 424 and FileZilla 3.2.7.1.
Sorry for my big post.
Log from WinSCP 419:
. 2009-10-27 16:31:49.225 —————————————————————————
. 2009-10-27 16:31:49.225 WinSCP Version 4.1.9 (Build 416) (OS 5.1.2600 Service Pack 2)
. 2009-10-27 16:31:49.225 Login time: Tuesday, October 27, 2009 4:31:49 PM
. 2009-10-27 16:31:49.225 —————————————————————————
. 2009-10-27 16:31:49.225 Session name: user@10.10.5.15
. 2009-10-27 16:31:49.225 Host name: 10.10.5.15 (Port: 22)
. 2009-10-27 16:31:49.225 User name: user (Password: Yes, Key file: No)
. 2009-10-27 16:31:49.225 Tunnel: No
. 2009-10-27 16:31:49.225 Transfer Protocol: SFTP (SCP)
. 2009-10-27 16:31:49.225 Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. 2009-10-27 16:31:49.225 Proxy: none
. 2009-10-27 16:31:49.225 SSH protocol version: 2; Compression: No
. 2009-10-27 16:31:49.225 Bypass authentication: No
. 2009-10-27 16:31:49.225 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. 2009-10-27 16:31:49.225 Ciphers: aes,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2009-10-27 16:31:49.225 SSH Bugs: -,-,-,-,-,-,-,-
. 2009-10-27 16:31:49.225 SFTP Bugs: -,-
. 2009-10-27 16:31:49.225 Return code variable: Autodetect; Lookup user groups: Yes
. 2009-10-27 16:31:49.225 Shell: default, EOL: 0
. 2009-10-27 16:31:49.225 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. 2009-10-27 16:31:49.225 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2009-10-27 16:31:49.225 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2009-10-27 16:31:49.225 Cache directory changes: Yes, Permanent: Yes
. 2009-10-27 16:31:49.225 DST mode: 1
. 2009-10-27 16:31:49.225 —————————————————————————
. 2009-10-27 16:31:49.256 Looking up host «10.10.5.15»
. 2009-10-27 16:31:49.256 Connecting to 10.10.5.15 port 22
. 2009-10-27 16:31:49.459 Server version: SSH-2.0-1.36 sshlib: T9999G06_15Apr2008_comForte_SSH2_0079
. 2009-10-27 16:31:49.459 We claim version: SSH-2.0-WinSCP_release_4.1.9
. 2009-10-27 16:31:49.475 SSPI: acquired credentials for: user@domain
. 2009-10-27 16:31:49.475 Cannot convert IP address to SPN: DNS is not trusted
. 2009-10-27 16:31:49.475 GSSKEX disabled: The operation completed successfully.
. 2009-10-27 16:31:49.475 Using SSH protocol version 2
. 2009-10-27 16:31:49.553 Using Diffie-Hellman with standard group «group1»
. 2009-10-27 16:31:49.553 Doing Diffie-Hellman key exchange with hash SHA-1
. 2009-10-27 16:31:49.881 Host key fingerprint is:
. 2009-10-27 16:31:49.881 ssh-dss 1024 22:a3:1e:60:52:95:11:62:be:5a:60:4c:7f:75:f5:04
. 2009-10-27 16:31:49.881 Initialised AES-256 CBC client->server encryption
. 2009-10-27 16:31:49.881 Initialised HMAC-SHA1 client->server MAC algorithm
. 2009-10-27 16:31:49.975 Initialised AES-256 CBC server->client encryption
. 2009-10-27 16:31:49.975 Initialised HMAC-SHA1 server->client MAC algorithm
! 2009-10-27 16:31:50.069 Using username «user».
. 2009-10-27 16:31:50.178 Prompt (6, SSH password, , &Password: )
. 2009-10-27 16:31:50.178 Using stored password.
. 2009-10-27 16:31:50.178 Sent password
. 2009-10-27 16:31:51.303 Access granted
. 2009-10-27 16:31:51.397 Opened channel for session
. 2009-10-27 16:31:51.803 Started a shell/command
. 2009-10-27 16:31:51.803 —————————————————————————
. 2009-10-27 16:31:51.803 Using SFTP protocol.
. 2009-10-27 16:31:51.803 Doing startup conversation with host.
> 2009-10-27 16:31:51.803 Type: SSH_FXP_INIT, Size: 5, Number: -1
< 2009-10-27 16:31:51.897 Type: SSH_FXP_VERSION, Size: 5, Number: -1
. 2009-10-27 16:31:51.897 SFTP version 3 negotiated.
. 2009-10-27 16:31:51.897 We believe the server has signed timestamps bug
. 2009-10-27 16:31:51.897 We will use UTF-8 strings for status messages only
. 2009-10-27 16:31:51.897 Getting current directory name.
. 2009-10-27 16:31:51.897 Getting real path for ‘.’
> 2009-10-27 16:31:51.897 Type: SSH_FXP_REALPATH, Size: 10, Number: 16
< 2009-10-27 16:31:52.006 Type: SSH_FXP_NAME, Size: 55, Number: 16
. 2009-10-27 16:31:52.006 Real path is ‘/G/test00/test’
. 2009-10-27 16:31:52.006 Listing directory «/G/test00/test».
> 2009-10-27 16:31:52.006 Type: SSH_FXP_OPENDIR, Size: 26, Number: 267
< 2009-10-27 16:31:52.147 Type: SSH_FXP_HANDLE, Size: 13, Number: 267
> 2009-10-27 16:31:52.147 Type: SSH_FXP_READDIR, Size: 13, Number: 524
< 2009-10-27 16:31:52.241 Type: SSH_FXP_NAME, Size: 345, Number: 524
> 2009-10-27 16:31:52.241 Type: SSH_FXP_READDIR, Size: 13, Number: 780
< 2009-10-27 16:31:52.334 Type: SSH_FXP_STATUS, Size: 28, Number: 780
< 2009-10-27 16:31:52.334 Status/error code: 1
> 2009-10-27 16:31:52.334 Type: SSH_FXP_CLOSE, Size: 13, Number: 1028
. 2009-10-27 16:31:52.334 Startup conversation with host finished.
. 2009-10-27 16:31:54.178 Changing directory to «/G/test00».
. 2009-10-27 16:31:54.178 Getting real path for ‘/G/test00’
> 2009-10-27 16:31:54.178 Type: SSH_FXP_REALPATH, Size: 18, Number: 1296
< 2009-10-27 16:31:54.178 Type: SSH_FXP_STATUS, Size: 24, Number: 1028
. 2009-10-27 16:31:54.178 Discarding reserved response
< 2009-10-27 16:31:54.272 Type: SSH_FXP_NAME, Size: 39, Number: 1296
. 2009-10-27 16:31:54.272 Real path is ‘/G/test00’
. 2009-10-27 16:31:54.272 Trying to open directory «/G/test00».
> 2009-10-27 16:31:54.272 Type: SSH_FXP_LSTAT, Size: 18, Number: 1543
< 2009-10-27 16:31:54.381 Type: SSH_FXP_ATTRS, Size: 37, Number: 1543
. 2009-10-27 16:31:54.381 Getting current directory name.
. 2009-10-27 16:31:54.381 Listing directory «/G/test00».
> 2009-10-27 16:31:54.381 Type: SSH_FXP_OPENDIR, Size: 18, Number: 1803
< 2009-10-27 16:31:54.491 Type: SSH_FXP_HANDLE, Size: 13, Number: 1803
> 2009-10-27 16:31:54.491 Type: SSH_FXP_READDIR, Size: 13, Number: 2060
< 2009-10-27 16:31:54.928 Type: SSH_FXP_NAME, Size: 4793, Number: 2060
> 2009-10-27 16:31:54.928 Type: SSH_FXP_READDIR, Size: 13, Number: 2316
< 2009-10-27 16:31:55.022 Type: SSH_FXP_STATUS, Size: 28, Number: 2316
< 2009-10-27 16:31:55.022 Status/error code: 1
> 2009-10-27 16:31:55.022 Type: SSH_FXP_CLOSE, Size: 13, Number: 2564
. 2009-10-27 16:31:59.866 Cached directory change via «/G/test01/test» to «/G/test01/test».
. 2009-10-27 16:31:59.866 Getting current directory name.
. 2009-10-27 16:31:59.866 Listing directory «/G/test01/test».
> 2009-10-27 16:31:59.866 Type: SSH_FXP_OPENDIR, Size: 26, Number: 2827
< 2009-10-27 16:31:59.866 Type: SSH_FXP_STATUS, Size: 24, Number: 2564
. 2009-10-27 16:31:59.866 Discarding reserved response
< 2009-10-27 16:32:00.022 Type: SSH_FXP_HANDLE, Size: 13, Number: 2827
> 2009-10-27 16:32:00.022 Type: SSH_FXP_READDIR, Size: 13, Number: 3084
< 2009-10-27 16:32:00.397 Type: SSH_FXP_NAME, Size: 11205, Number: 3084
> 2009-10-27 16:32:00.397 Type: SSH_FXP_READDIR, Size: 13, Number: 3340
< 2009-10-27 16:32:00.772 Type: SSH_FXP_NAME, Size: 11203, Number: 3340
> 2009-10-27 16:32:00.772 Type: SSH_FXP_READDIR, Size: 13, Number: 3596
< 2009-10-27 16:32:01.085 Type: SSH_FXP_NAME, Size: 11204, Number: 3596
> 2009-10-27 16:32:01.085 Type: SSH_FXP_READDIR, Size: 13, Number: 3852
< 2009-10-27 16:32:01.444 Type: SSH_FXP_NAME, Size: 7402, Number: 3852
> 2009-10-27 16:32:01.444 Type: SSH_FXP_READDIR, Size: 13, Number: 4108
< 2009-10-27 16:32:01.585 Type: SSH_FXP_STATUS, Size: 28, Number: 4108
< 2009-10-27 16:32:01.585 Status/error code: 1
> 2009-10-27 16:32:01.585 Type: SSH_FXP_CLOSE, Size: 13, Number: 4356
. 2009-10-27 16:32:11.194 File: «/G/test01/test/file»
. 2009-10-27 16:32:11.194 Copying «/G/test01/test/file» to local directory started.
. 2009-10-27 16:32:11.194 Binary transfer mode selected.
. 2009-10-27 16:32:11.194 Checking existence of partially transfered file.
. 2009-10-27 16:32:11.194 Opening remote file.
> 2009-10-27 16:32:11.194 Type: SSH_FXP_OPEN, Size: 43, Number: 4611
< 2009-10-27 16:32:11.194 Type: SSH_FXP_STATUS, Size: 24, Number: 4356
. 2009-10-27 16:32:11.194 Discarding reserved response
< 2009-10-27 16:32:11.319 Type: SSH_FXP_HANDLE, Size: 13, Number: 4611
> 2009-10-27 16:32:11.319 Type: SSH_FXP_FSTAT, Size: 13, Number: 4872
> 2009-10-27 16:32:11.319 Type: SSH_FXP_READ, Size: 25, Number: 5125
. 2009-10-27 16:32:11.413 3 skipped SSH_FXP_WRITE, SSH_FXP_READ, SSH_FXP_DATA and SSH_FXP_STATUS packets.
< 2009-10-27 16:32:11.413 Type: SSH_FXP_ATTRS, Size: 37, Number: 4872
. 2009-10-27 16:32:11.413 Storing reserved response
< 2009-10-27 16:32:11.929 Status/error code: 4, Message: 6917, Server: Failure, Language:
. 2009-10-27 16:32:12.226 18 skipped SSH_FXP_WRITE, SSH_FXP_READ, SSH_FXP_DATA and SSH_FXP_STATUS packets.
> 2009-10-27 16:32:12.226 Type: SSH_FXP_CLOSE, Size: 13, Number: 7940
* 2009-10-27 16:32:12.226 (ECommand) Copying files from remote side failed.
* 2009-10-27 16:32:12.226 General failure (server should provide error description).
* 2009-10-27 16:32:12.226 Error code: 4
* 2009-10-27 16:32:12.226 Error message from server: Failure
* 2009-10-27 16:32:12.226 Request code: 5
. 2009-10-27 16:32:15.460 Closing connection.
. 2009-10-27 16:32:15.460 Sending special code: 12
. 2009-10-27 16:32:15.460 Sent EOF message
Log from WinSCP 424:
. 2009-10-27 16:37:57.251 —————————————————————————
. 2009-10-27 16:37:57.251 WinSCP Version 4.2.4 (Build 610) (OS 5.1.2600 Service Pack 2)
. 2009-10-27 16:37:57.251 Login time: Tuesday, October 27, 2009 4:37:57 PM
. 2009-10-27 16:37:57.251 —————————————————————————
. 2009-10-27 16:37:57.251 Session name: user@10.10.5.15
. 2009-10-27 16:37:57.251 Host name: 10.10.5.15 (Port: 22)
. 2009-10-27 16:37:57.251 User name: user (Password: Yes, Key file: No)
. 2009-10-27 16:37:57.251 Tunnel: No
. 2009-10-27 16:37:57.251 Transfer Protocol: SFTP (SCP)
. 2009-10-27 16:37:57.251 Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. 2009-10-27 16:37:57.251 Proxy: none
. 2009-10-27 16:37:57.251 SSH protocol version: 2; Compression: No
. 2009-10-27 16:37:57.251 Bypass authentication: No
. 2009-10-27 16:37:57.251 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. 2009-10-27 16:37:57.251 Ciphers: aes,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2009-10-27 16:37:57.251 SSH Bugs: -,-,-,-,-,-,-,-,-
. 2009-10-27 16:37:57.251 SFTP Bugs: -,-
. 2009-10-27 16:37:57.251 Return code variable: Autodetect; Lookup user groups: Yes
. 2009-10-27 16:37:57.251 Shell: default, EOL: 0
. 2009-10-27 16:37:57.251 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. 2009-10-27 16:37:57.251 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2009-10-27 16:37:57.251 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2009-10-27 16:37:57.251 Cache directory changes: Yes, Permanent: Yes
. 2009-10-27 16:37:57.251 DST mode: 1
. 2009-10-27 16:37:57.251 —————————————————————————
. 2009-10-27 16:37:57.283 Looking up host «10.10.5.15»
. 2009-10-27 16:37:57.283 Connecting to 10.10.5.15 port 22
. 2009-10-27 16:37:57.548 Server version: SSH-2.0-1.36 sshlib: T9999G06_15Apr2008_comForte_SSH2_0079
. 2009-10-27 16:37:57.548 Using SSH protocol version 2
. 2009-10-27 16:37:57.548 We claim version: SSH-2.0-WinSCP_release_4.2.4
. 2009-10-27 16:37:57.642 Using Diffie-Hellman with standard group «group1»
. 2009-10-27 16:37:57.642 Doing Diffie-Hellman key exchange with hash SHA-1
. 2009-10-27 16:37:57.908 Asking user:
. 2009-10-27 16:37:57.908 The server’s host key was not found in the cache. You have no guarantee that the server is the computer you think it is.
. 2009-10-27 16:37:57.908
. 2009-10-27 16:37:57.908 The server’s dss key fingerprint is:
. 2009-10-27 16:37:57.908 ssh-dss 1024 22:a3:1e:60:52:95:11:62:be:5a:60:4c:7f:75:f5:04
. 2009-10-27 16:37:57.908
. 2009-10-27 16:37:57.908 If you trust this host, press Yes. To connect without adding host key to the cache, press No. To abandon the connection press Cancel.
. 2009-10-27 16:37:57.908
. 2009-10-27 16:37:57.908 Continue connecting and add host key to the cache? ()
. 2009-10-27 16:37:59.752 Host key fingerprint is:
. 2009-10-27 16:37:59.752 ssh-dss 1024 22:a3:1e:60:52:95:11:62:be:5a:60:4c:7f:75:f5:04
. 2009-10-27 16:37:59.752 Initialised AES-256 CBC client->server encryption
. 2009-10-27 16:37:59.752 Initialised HMAC-SHA1 client->server MAC algorithm
. 2009-10-27 16:37:59.752 Initialised AES-256 CBC server->client encryption
. 2009-10-27 16:37:59.752 Initialised HMAC-SHA1 server->client MAC algorithm
! 2009-10-27 16:37:59.986 Using username «user».
. 2009-10-27 16:38:00.080 Prompt (6, SSH password, , &Password: )
. 2009-10-27 16:38:00.080 Using stored password.
. 2009-10-27 16:38:00.080 Sent password
. 2009-10-27 16:38:00.987 Access granted
. 2009-10-27 16:38:01.080 Opened channel for session
. 2009-10-27 16:38:01.674 Started a shell/command
. 2009-10-27 16:38:01.674 —————————————————————————
. 2009-10-27 16:38:01.674 Using SFTP protocol.
. 2009-10-27 16:38:01.674 Doing startup conversation with host.
> 2009-10-27 16:38:01.674 Type: SSH_FXP_INIT, Size: 5, Number: -1
< 2009-10-27 16:38:01.768 Type: SSH_FXP_VERSION, Size: 5, Number: -1
. 2009-10-27 16:38:01.768 SFTP version 3 negotiated.
. 2009-10-27 16:38:01.768 We believe the server has signed timestamps bug
. 2009-10-27 16:38:01.768 We will use UTF-8 strings for status messages only
. 2009-10-27 16:38:01.784 Getting current directory name.
. 2009-10-27 16:38:01.784 Getting real path for ‘.’
> 2009-10-27 16:38:01.784 Type: SSH_FXP_REALPATH, Size: 10, Number: 16
< 2009-10-27 16:38:01.862 Type: SSH_FXP_NAME, Size: 55, Number: 16
. 2009-10-27 16:38:01.862 Real path is ‘/G/test00/test’
. 2009-10-27 16:38:01.862 Listing directory «/G/test00/test».
> 2009-10-27 16:38:01.862 Type: SSH_FXP_OPENDIR, Size: 26, Number: 267
< 2009-10-27 16:38:01.971 Type: SSH_FXP_HANDLE, Size: 13, Number: 267
> 2009-10-27 16:38:01.971 Type: SSH_FXP_READDIR, Size: 13, Number: 524
< 2009-10-27 16:38:02.065 Type: SSH_FXP_NAME, Size: 345, Number: 524
> 2009-10-27 16:38:02.065 Type: SSH_FXP_READDIR, Size: 13, Number: 780
< 2009-10-27 16:38:02.159 Type: SSH_FXP_STATUS, Size: 28, Number: 780
< 2009-10-27 16:38:02.159 Status code: 1
> 2009-10-27 16:38:02.159 Type: SSH_FXP_CLOSE, Size: 13, Number: 1028
. 2009-10-27 16:38:02.159 Startup conversation with host finished.
. 2009-10-27 16:38:07.066 Changing directory to «/G/test01/test».
. 2009-10-27 16:38:07.066 Getting real path for ‘/G/test01/test’
> 2009-10-27 16:38:07.066 Type: SSH_FXP_REALPATH, Size: 26, Number: 1296
< 2009-10-27 16:38:07.066 Type: SSH_FXP_STATUS, Size: 24, Number: 1028
. 2009-10-27 16:38:07.066 Discarding reserved response
< 2009-10-27 16:38:07.160 Type: SSH_FXP_NAME, Size: 55, Number: 1296
. 2009-10-27 16:38:07.160 Real path is ‘/G/test01/test’
. 2009-10-27 16:38:07.160 Trying to open directory «/G/test01/test».
> 2009-10-27 16:38:07.160 Type: SSH_FXP_LSTAT, Size: 26, Number: 1543
< 2009-10-27 16:38:07.254 Type: SSH_FXP_ATTRS, Size: 37, Number: 1543
. 2009-10-27 16:38:07.254 Getting current directory name.
. 2009-10-27 16:38:07.254 Listing directory «/G/test01/test».
> 2009-10-27 16:38:07.254 Type: SSH_FXP_OPENDIR, Size: 26, Number: 1803
< 2009-10-27 16:38:07.410 Type: SSH_FXP_HANDLE, Size: 13, Number: 1803
> 2009-10-27 16:38:07.410 Type: SSH_FXP_READDIR, Size: 13, Number: 2060
< 2009-10-27 16:38:07.816 Type: SSH_FXP_NAME, Size: 11205, Number: 2060
> 2009-10-27 16:38:07.816 Type: SSH_FXP_READDIR, Size: 13, Number: 2316
< 2009-10-27 16:38:08.238 Type: SSH_FXP_NAME, Size: 11203, Number: 2316
> 2009-10-27 16:38:08.238 Type: SSH_FXP_READDIR, Size: 13, Number: 2572
< 2009-10-27 16:38:08.738 Type: SSH_FXP_NAME, Size: 11204, Number: 2572
> 2009-10-27 16:38:08.738 Type: SSH_FXP_READDIR, Size: 13, Number: 2828
< 2009-10-27 16:38:08.973 Type: SSH_FXP_NAME, Size: 7402, Number: 2828
> 2009-10-27 16:38:08.973 Type: SSH_FXP_READDIR, Size: 13, Number: 3084
< 2009-10-27 16:38:09.051 Type: SSH_FXP_STATUS, Size: 28, Number: 3084
< 2009-10-27 16:38:09.051 Status code: 1
> 2009-10-27 16:38:09.051 Type: SSH_FXP_CLOSE, Size: 13, Number: 3332
. 2009-10-27 16:38:19.866 File: «/G/test01/test/file»
. 2009-10-27 16:38:19.866 Copying «/G/test01/test/file» to local directory started.
. 2009-10-27 16:38:19.866 Binary transfer mode selected.
. 2009-10-27 16:38:19.866 Checking existence of partially transfered file.
. 2009-10-27 16:38:19.866 Opening remote file.
> 2009-10-27 16:38:19.866 Type: SSH_FXP_OPEN, Size: 43, Number: 3587
< 2009-10-27 16:38:19.866 Type: SSH_FXP_STATUS, Size: 24, Number: 3332
. 2009-10-27 16:38:19.866 Discarding reserved response
< 2009-10-27 16:38:20.116 Type: SSH_FXP_HANDLE, Size: 13, Number: 3587
> 2009-10-27 16:38:20.116 Type: SSH_FXP_FSTAT, Size: 13, Number: 3848
> 2009-10-27 16:38:20.116 Type: SSH_FXP_READ, Size: 25, Number: 4101
. 2009-10-27 16:38:20.226 3 skipped SSH_FXP_WRITE, SSH_FXP_READ, SSH_FXP_DATA and SSH_FXP_STATUS packets.
< 2009-10-27 16:38:20.226 Type: SSH_FXP_ATTRS, Size: 37, Number: 3848
. 2009-10-27 16:38:20.226 Storing reserved response
< 2009-10-27 16:38:21.007 Status code: 4, Message: 5893, Server: Failure, Language:
. 2009-10-27 16:38:21.210 18 skipped SSH_FXP_WRITE, SSH_FXP_READ, SSH_FXP_DATA and SSH_FXP_STATUS packets.
> 2009-10-27 16:38:21.210 Type: SSH_FXP_CLOSE, Size: 13, Number: 6916
* 2009-10-27 16:38:21.210 (ECommand) Copying files from remote side failed.
* 2009-10-27 16:38:21.210 General failure (server should provide error description).
* 2009-10-27 16:38:21.210 Error code: 4
* 2009-10-27 16:38:21.210 Error message from server: Failure
* 2009-10-27 16:38:21.210 Request code: 5
. 2009-10-27 16:38:25.867 Closing connection.
. 2009-10-27 16:38:25.867 Sending special code: 12
. 2009-10-27 16:38:25.867 Sent EOF message
Log from FileZilla 3.2.7.1:
2009-10-27 16:59:41 4084 0 Status: Connecting to 10.10.5.15…
2009-10-27 16:59:41 4084 0 Trace: Going to execute D:ProgrameFileZillaPortableAppfilezillafzsftp.exe
2009-10-27 16:59:41 4084 0 Response: fzSftp started
2009-10-27 16:59:41 4084 0 Trace: CSftpControlSocket::ConnectParseResponse(fzSftp started)
2009-10-27 16:59:41 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:41 4084 0 Trace: CSftpControlSocket::ConnectSend()
2009-10-27 16:59:41 4084 0 Command: open «user@10.10.5.15» 22
2009-10-27 16:59:41 4084 0 Trace: Looking up host «10.10.5.15»
2009-10-27 16:59:41 4084 0 Trace: Connecting to 10.10.5.15 port 22
2009-10-27 16:59:41 4084 0 Trace: Server version: SSH-2.0-1.36 sshlib: T9999G06_15Apr2008_comForte_SSH2_0079
2009-10-27 16:59:41 4084 0 Trace: Using SSH protocol version 2
2009-10-27 16:59:41 4084 0 Trace: We claim version: SSH-2.0-PuTTY_Local:_Aug_23_2009_19:56:54
2009-10-27 16:59:41 4084 0 Trace: Using Diffie-Hellman with standard group «group1»
2009-10-27 16:59:41 4084 0 Trace: Doing Diffie-Hellman key exchange with hash SHA-1
2009-10-27 16:59:42 4084 0 Trace: Host key fingerprint is:
2009-10-27 16:59:42 4084 0 Trace: ssh-dss 1024 22:a3:1e:60:52:95:11:62:be:5a:60:4c:7f:75:f5:04
2009-10-27 16:59:42 4084 0 Trace: Initialised AES-256 CBC client->server encryption
2009-10-27 16:59:42 4084 0 Trace: Initialised HMAC-SHA1 client->server MAC algorithm
2009-10-27 16:59:42 4084 0 Trace: Initialised AES-256 CBC server->client encryption
2009-10-27 16:59:42 4084 0 Trace: Initialised HMAC-SHA1 server->client MAC algorithm
2009-10-27 16:59:42 4084 0 Command: Pass: *******
2009-10-27 16:59:42 4084 0 Trace: Sent password
2009-10-27 16:59:42 4084 0 Trace: Access granted
2009-10-27 16:59:42 4084 0 Trace: Opened channel for session
2009-10-27 16:59:44 4084 0 Trace: Started a shell/command
2009-10-27 16:59:44 4084 0 Status: Connected to 10.10.5.15
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::ConnectParseResponse()
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 16:59:44 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 16:59:44 4084 0 Status: Retrieving directory listing…
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::ChangeDirSend()
2009-10-27 16:59:44 4084 0 Command: pwd
2009-10-27 16:59:44 4084 0 Response: Current directory is: «/G/test00/test»
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 16:59:44 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::ParseSubcommandResult(0)
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::ListSubcommandResult()
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:44 4084 0 Trace: CSftpControlSocket::ListSend()
2009-10-27 16:59:44 4084 0 Command: ls
2009-10-27 16:59:44 4084 0 Status: Listing directory /G/test00/test
2009-10-27 16:59:45 4084 0 Listing: -rwx—— 0 57093 223 2856 Oct 26 16:03 filetest
2009-10-27 16:59:45 4084 0 Trace: CSftpControlSocket::ListParseResponse()
2009-10-27 16:59:45 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:45 4084 0 Trace: CSftpControlSocket::ListSend()
2009-10-27 16:59:45 4084 0 Status: Calculating timezone offset of server…
2009-10-27 16:59:45 4084 0 Command: mtime «filetest»
2009-10-27 16:59:45 4084 0 Response: 1256569421
2009-10-27 16:59:45 4084 0 Trace: CSftpControlSocket::ListParseResponse(1256569421)
2009-10-27 16:59:45 4084 0 Status: Timezone offsets: Server: 3600 seconds. Local: 7200 seconds. Difference: 3600 seconds.
2009-10-27 16:59:45 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 16:59:45 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 16:59:45 4084 0 Status: Directory listing successful
2009-10-27 16:59:49 4084 0 Status: Retrieving directory listing…
2009-10-27 16:59:49 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:49 4084 0 Trace: CSftpControlSocket::ChangeDirSend()
2009-10-27 16:59:49 4084 0 Command: cd «..»
2009-10-27 16:59:49 4084 0 Response: New directory is: «/G/test00»
2009-10-27 16:59:49 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 16:59:49 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 16:59:49 4084 0 Trace: CSftpControlSocket::ParseSubcommandResult(0)
2009-10-27 16:59:49 4084 0 Trace: CSftpControlSocket::ListSubcommandResult()
2009-10-27 16:59:49 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:49 4084 0 Trace: CSftpControlSocket::ListSend()
2009-10-27 16:59:49 4084 0 Command: ls
2009-10-27 16:59:49 4084 0 Status: Listing directory /G/test00
2009-10-27 16:59:50 4084 0 Listing: drwxrwxrwx 0 65535 255 4096 Oct 27 15:59 test
2009-10-27 16:59:50 4084 0 Trace: CSftpControlSocket::ListParseResponse()
2009-10-27 16:59:50 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 16:59:50 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 16:59:50 4084 0 Status: Directory listing successful
2009-10-27 16:59:51 4084 0 Status: Retrieving directory listing…
2009-10-27 16:59:51 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:51 4084 0 Trace: CSftpControlSocket::ChangeDirSend()
2009-10-27 16:59:51 4084 0 Command: cd «..»
2009-10-27 16:59:51 4084 0 Response: New directory is: «/G»
2009-10-27 16:59:51 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 16:59:51 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 16:59:51 4084 0 Trace: CSftpControlSocket::ParseSubcommandResult(0)
2009-10-27 16:59:51 4084 0 Trace: CSftpControlSocket::ListSubcommandResult()
2009-10-27 16:59:51 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 16:59:51 4084 0 Trace: CSftpControlSocket::ListSend()
2009-10-27 16:59:51 4084 0 Command: ls
2009-10-27 16:59:51 4084 0 Status: Listing directory /G
2009-10-27 16:59:53 4084 0 Listing: drwxrwxrwx 0 65535 255 4096 Oct 27 15:59 test01
2009-10-27 16:59:53 4084 0 Listing: drwxrwxrwx 0 65535 255 4096 Oct 27 15:59 test00
2009-10-27 16:59:53 4084 0 Trace: CSftpControlSocket::ListParseResponse()
2009-10-27 16:59:53 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 16:59:53 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 16:59:53 4084 0 Status: Directory listing successful
2009-10-27 17:00:03 4084 0 Status: Retrieving directory listing…
2009-10-27 17:00:03 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 17:00:03 4084 0 Trace: CSftpControlSocket::ChangeDirSend()
2009-10-27 17:00:03 4084 0 Command: cd «test01»
2009-10-27 17:00:04 4084 0 Response: New directory is: «/G/test01»
2009-10-27 17:00:04 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 17:00:04 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 17:00:04 4084 0 Trace: CSftpControlSocket::ParseSubcommandResult(0)
2009-10-27 17:00:04 4084 0 Trace: CSftpControlSocket::ListSubcommandResult()
2009-10-27 17:00:04 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 17:00:04 4084 0 Trace: CSftpControlSocket::ListSend()
2009-10-27 17:00:04 4084 0 Command: ls
2009-10-27 17:00:04 4084 0 Status: Listing directory /G/test01
2009-10-27 17:00:04 4084 0 Listing: drwxrwxrwx 0 65535 255 4096 Oct 27 16:00 test
2009-10-27 17:00:04 4084 0 Trace: CSftpControlSocket::ListParseResponse()
2009-10-27 17:00:04 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 17:00:04 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 17:00:04 4084 0 Status: Directory listing successful
2009-10-27 17:00:06 4084 0 Status: Retrieving directory listing…
2009-10-27 17:00:06 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 17:00:06 4084 0 Trace: CSftpControlSocket::ChangeDirSend()
2009-10-27 17:00:06 4084 0 Command: cd «test»
2009-10-27 17:00:07 4084 0 Response: New directory is: «/G/test01/test»
2009-10-27 17:00:07 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 17:00:07 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 17:00:07 4084 0 Trace: CSftpControlSocket::ParseSubcommandResult(0)
2009-10-27 17:00:07 4084 0 Trace: CSftpControlSocket::ListSubcommandResult()
2009-10-27 17:00:07 4084 0 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 17:00:07 4084 0 Trace: CSftpControlSocket::ListSend()
2009-10-27 17:00:07 4084 0 Command: ls
2009-10-27 17:00:07 4084 0 Status: Listing directory /G/test01/test
2009-10-27 17:00:09 4084 0 Listing: -rwx—— 0 57343 223 6439680 Oct 27 02:02 file
2009-10-27 17:00:09 4084 0 Trace: CSftpControlSocket::ListParseResponse()
2009-10-27 17:00:09 4084 0 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 17:00:09 4084 0 Trace: CControlSocket::ResetOperation(0)
2009-10-27 17:00:09 4084 0 Status: Directory listing successful
2009-10-27 17:00:20 4084 1 Status: Connecting to 10.10.5.15…
2009-10-27 17:00:20 4084 1 Trace: Going to execute D:ProgrameFileZillaPortableAppfilezillafzsftp.exe
2009-10-27 17:00:20 4084 1 Response: fzSftp started
2009-10-27 17:00:20 4084 1 Trace: CSftpControlSocket::ConnectParseResponse(fzSftp started)
2009-10-27 17:00:20 4084 1 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 17:00:20 4084 1 Trace: CSftpControlSocket::ConnectSend()
2009-10-27 17:00:20 4084 1 Command: open «user@10.10.5.15» 22
2009-10-27 17:00:20 4084 1 Trace: Looking up host «10.10.5.15»
2009-10-27 17:00:20 4084 1 Trace: Connecting to 10.10.5.15 port 22
2009-10-27 17:00:21 4084 1 Trace: Server version: SSH-2.0-1.36 sshlib: T9999G06_15Apr2008_comForte_SSH2_0079
2009-10-27 17:00:21 4084 1 Trace: Using SSH protocol version 2
2009-10-27 17:00:21 4084 1 Trace: We claim version: SSH-2.0-PuTTY_Local:_Aug_23_2009_19:56:54
2009-10-27 17:00:21 4084 1 Trace: Using Diffie-Hellman with standard group «group1»
2009-10-27 17:00:21 4084 1 Trace: Doing Diffie-Hellman key exchange with hash SHA-1
2009-10-27 17:00:21 4084 1 Trace: Host key fingerprint is:
2009-10-27 17:00:21 4084 1 Trace: ssh-dss 1024 22:a3:1e:60:52:95:11:62:be:5a:60:4c:7f:75:f5:04
2009-10-27 17:00:21 4084 1 Trace: Initialised AES-256 CBC client->server encryption
2009-10-27 17:00:21 4084 1 Trace: Initialised HMAC-SHA1 client->server MAC algorithm
2009-10-27 17:00:21 4084 1 Trace: Initialised AES-256 CBC server->client encryption
2009-10-27 17:00:21 4084 1 Trace: Initialised HMAC-SHA1 server->client MAC algorithm
2009-10-27 17:00:21 4084 1 Command: Pass: *******
2009-10-27 17:00:21 4084 1 Trace: Sent password
2009-10-27 17:00:22 4084 1 Trace: Access granted
2009-10-27 17:00:22 4084 1 Trace: Opened channel for session
2009-10-27 17:00:24 4084 1 Trace: Started a shell/command
2009-10-27 17:00:24 4084 1 Status: Connected to 10.10.5.15
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::ConnectParseResponse()
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 17:00:24 4084 1 Trace: CControlSocket::ResetOperation(0)
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::FileTransfer(…)
2009-10-27 17:00:24 4084 1 Status: Starting download of /G/test01/test.file
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::ChangeDirSend()
2009-10-27 17:00:24 4084 1 Command: cd «/G/test01/test»
2009-10-27 17:00:24 4084 1 Response: New directory is: «/G/test01/test»
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 17:00:24 4084 1 Trace: CControlSocket::ResetOperation(0)
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::ParseSubcommandResult(0)
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::FileTransferSubcommandResult()
2009-10-27 17:00:24 4084 1 Trace: CSftpControlSocket::SendNextCommand()
2009-10-27 17:00:24 4084 1 Trace: FileTransferSend()
2009-10-27 17:00:24 4084 1 Command: get «file» «D:file»
2009-10-27 17:00:25 4084 1 Status: remote:/G/test01/test/file => local:D:file
2009-10-27 17:01:11 4084 1 Trace: FileTransferParseResponse()
2009-10-27 17:01:11 4084 1 Trace: CSftpControlSocket::ResetOperation(0)
2009-10-27 17:01:11 4084 1 Trace: CControlSocket::ResetOperation(0)
2009-10-27 17:01:11 4084 1 Status: File transfer successful
2009-10-27 17:01:14 4084 1 Trace: CSftpControlSocket::ResetOperation(66)
2009-10-27 17:01:14 4084 1 Trace: CControlSocket::ResetOperation(66)
2009-10-27 17:01:14 4084 0 Trace: CSftpControlSocket::ResetOperation(66)
2009-10-27 17:01:14 4084 0 Trace: CControlSocket::ResetOperation(66)
Reply with quote
Advertisement
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2009-10-28
Guest wrote:
Bellow you can find log from WinSCP 419, 424 and FileZilla 3.2.7.1.
Sorry for my big post.
It is hard to help you as the server does not indicate any reason why it fails. Can you see anything useful in the server’s log file?
Reply with quote
- Guest
2009-10-29 14:55
martin wrote:
It is hard to help you as the server does not indicate any reason why it fails. Can you see anything useful in the server’s log file?
Unfortunately I don’t have access to server log.
As i know, winscp is based on filezilla engine, why in filezilla everithing is working and here not ?
It is a different SFTP protocol, version or what ?
I cannot see SFTP verion in filezilla :|.
Regards,
G.
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2009-10-31
Anonymous wrote:
As i know, winscp is based on filezilla engine, why in filezilla everithing is working and here not ?
WinSCP uses only FTP code from Filezilla, not SFTP.
It is a different SFTP protocol, version or what ?
I cannot see SFTP verion in filezilla :|.
No. Filezilla knows only version 3.
Reply with quote
- Guest
2009-11-02 17:03
In FileZilla,I can select the type of the SFTP server, and I select HpNonStop.
Can I select these from WinSCP somehow ?
As I say previous, if I transfer an ascii file, this can be done, but if I transfer a binary file I receive an error.
It is something with the SFTP protocol that is used by HPNonStop SO.
Reply with quote
Advertisement
-
Guest
Guest
2009-11-04 16:10
Actually, when the transfer starts, 40KB are transfer, and then O receive the error.
I think that SFTP server from HP NonStop mainframe wants to verify if the transfer is OK.
Also, the ASCII file is not transfer with CRLF end of line, even if I select ASCII file type when transfer start.
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2009-11-05
Anonymous wrote:
In FileZilla,I can select the type of the SFTP server, and I select HpNonStop.
Can I select these from WinSCP somehow ?
There’s no point selecting this with SFTP. In Filezilla the option affects how it parses directory listing and interprets the file path format. It is important with FTP protocol as it does not enforce any standards on the formats. But SFTP does. WinSCP adheres to the standards. I’m not even sure that Filezilla takes the option into account with SFTP. And if it does, it is wrong.
Reply with quote
-
martin◆
Site Admin -
2009-11-05
Guest wrote:
I think that SFTP server from HP NonStop mainframe wants to verify if the transfer is OK.
What kind of verification do you mean?
Reply with quote
- Guest
2009-11-12 09:34
martin wrote:
Guest wrote:
I think that SFTP server from HP NonStop mainframe wants to verify if the transfer is OK.
What kind of verification do you mean?
Since the transfer start, and a part of the files is transferred, maybe the problem is with a file check (checksum of the file part transferred).
We got a similar problem with WS_FTP 12, and with the new version the problem was solve.
I ask them what is the cause, but the only answer was that the problem is fixed and I should move to the new version.
Regards,
G.
Reply with quote
Advertisement
-
Guest
Guest
2010-01-06 14:38
I try to make the same download from PSFTP, and is working fine.
I try also with WinSCP 4.2.5 but I receive the same error.
It downloads a part of the file (40,948 bytes), when I try again to download the file, it ask me if I want to resume the transfer, and download anothe pice of 40,948 bytes.
It is very strange.
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2010-01-08
Guest wrote:
I try to make the same download from PSFTP, and is working fine.
I try also with WinSCP 4.2.5 but I receive the same error.
It downloads a part of the file (40,948 bytes), when I try again to download the file, it ask me if I want to resume the transfer, and download anothe pice of 40,948 bytes.
It is very strange.
Please post a full log file showing the problem. Start a new topic for that.
To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. For posting extensive logs you may use pastebin or similar application. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
Reply with quote
-
Sanjay
Guest
2013-10-06 09:09
I had faced while uploading a file in Xen server using winscp due to space u have to copy a files in /var/run/sr-mount/55ff0e01-d851-6b80-2a01-24b793b8fbb0/ directory.
mdude wrote:
Hi all. When I try connecting to WinSCP (Win XP Pro) I am able to connect, but whenever I try to add folders to my server or upload any files, I receive the following error:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 14Does anyone know the root of this? I exited my firewall, and other people can connect to the server with different usernames and passwords (I am accessing a college shared network). Thank you.
—Scott
Reply with quote
-
kishore ghag
Guest
2015-03-11 21:20
I had also same issue. I was getting the error while copying the file over WInscp. getting Error code 4.
I have changed default protocol rom SFTP to SCP and then it worked .
Reply with quote
Advertisement
-
ajit.iyer
Guest
2015-12-09 07:51
HI ,
I am getting this below error. Please help me.
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 18
(A)bort, (R)etry, (S)kip, Ski(p) all:
[/quote]
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2015-12-10
ajit.iyer wrote:
I am getting this below error. Please help me.
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 18
(A)bort, (R)etry, (S)kip, Ski(p) all:
See documentation for possible reasons you may be getting the error.
Reply with quote
-
user123fromindia
Guest
2016-05-27 06:38
Thanks Rafi. I faced the same issue. After deleting non essential files, the issue was resolved.
Rafi wrote:
We had the exact same error, and after checking permissions and other things, it turned to be a simple problem …. filesystem was 100% full
Good luck!
martin wrote:
Brian wrote:
Hi, this is actually the person with the problem, my friend was just posting for me at the time.
I tried uploading the web pages and the changes I made using Macromedia Dreamweaver and it gets the error as well.
No settings have been changed since it was able to last upload/update files.
Any other suggestions?
And are you able to write the files if you login using terminal. Also try SCP protocol, maybe it will display more meaningful message.
Reply with quote
-
Chandra Mauli Singh
Guest
2017-01-23 10:28
kishore ghag wrote:
I had also same issue. I was getting the error while copying the file over WinSCP. was getting Error code 4.
I have changed default protocol from SFTP to SCP and then it worked .
I changed default protocol from SFTP to SCP. it worked.
Thanks
Reply with quote
Advertisement
-
t.venkib8@…
Guest
2017-04-13 21:53
When i’m trying to copy file from Local to server, it is throwing below error:
copying files to remote side failed General failure (server should provide error description). Error code: 4 Error message from server: Failure
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2017-04-18
t.venkib8@… wrote:
When i’m trying to copy file from Local to server, it is throwing below error:
copying files to remote side failed General failure (server should provide error description). Error code: 4 Error message from server: Failure
Please start a new thread and attach a full session log file showing the problem (using the latest version of WinSCP).
To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
Reply with quote
-
George_jorge
Guest
2017-06-27 20:23
Unable to overwrite file ‘/usr/local/fop2/buttons.cfg’
Press the ‘Delete’ button to delete the file and try again to overwrite it
General error (The server must have provided more information)
Error Code: 4
Error message from server: Failure
- 2017-06-27_10-46-20-ERROR-WINSCP.png (106.8 KB)
Description: I need you to help me please
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2017-06-29
George_jorge wrote:
Unable to overwrite file ‘/usr/local/fop2/buttons.cfg’
Press the ‘Delete’ button to delete the file and try again to overwrite it
General error (The server must have provided more information)
Error Code: 4
Error message from server: Failure
Please start a new thread and post a complete English session log file.
Reply with quote
Advertisement
- Guest
2018-02-09 19:10
This helped. Thanks!
Rafi wrote:
We had the exact same error, and after checking permissions and other things, it turned to be a simple problem …. filesystem was 100% full
Good luck!
martin wrote:
Brian wrote:
Hi, this is actually the person with the problem, my friend was just posting for me at the time.
I tried uploading the web pages and the changes I made using Macromedia Dreamweaver and it gets the error as well.
No settings have been changed since it was able to last upload/update files.
Any other suggestions?
And are you able to write the files if you login using terminal. Also try SCP protocol, maybe it will display more meaningful message.
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,959
- Location:
- Prague, Czechia
2018-02-09
Anonymous wrote:
This helped. Thanks!
Rafi wrote:
We had the exact same error, and after checking permissions and other things, it turned to be a simple problem …. filesystem was 100% full
Actually, as documented:
https://winscp.net/eng/docs/sftp_codes#code_4
Reply with quote
-
Chedimorchdi
Guest
2022-04-03 02:41
Rafi wrote:
We had the exact same error, and after checking permissions and other things, it turned to be a simple problem …. filesystem was 100% full
Good luck!
martin wrote:
Brian wrote:
Hi, this is actually the person with the problem, my friend was just posting for me at the time.
I tried uploading the web pages and the changes I made using Macromedia Dreamweaver and it gets the error as well.
No settings have been changed since it was able to last upload/update files.
Any other suggestions?
And are you able to write the files if you login using terminal. Also try SCP protocol, maybe it will display more meaningful message.
Reply with quote
-
martin◆
Site Admin -
2022-04-04
Reply with quote
Advertisement
- Reply to topic
- Log in
You can post new topics in this forum
Как сменить права доступа?
Centos 7
не могу не как поменять права доступа к папкам и фалам
логинюсь под root
file ‘/var/log/messages’: open error: Read-only file system [v8.24.0-41.el7_7.2 try www.rsyslog.com/e/2433 ]
Меняю с sftp ошибка:
Общая ошибка (сервер должен предоставить описание ошибки).
Код ошибки: 4
Сообщение ошибки от сервер: Failure
Меняю с консоли chmod 777 * -R /var/log/messages
права не меняются
Тут пишет что нет директории
chmod: cannot access ‘/var/lib/rsyslog/imjournal.state.tmp’: No such file or directory
хотя файл лежит именно в этой директории
-
Вопрос заданболее трёх лет назад
-
1164 просмотра
Пригласить эксперта
Возможно, всё дело в этом:
‘/var/log/messages’: open error: Read-only file system
1. Сначала запускайте mount без параметров, чтобы посмотреть на каком разделе находится данный путь (раздел может быть смонтирован на / , на /var/ , на /var/log/ )
2. Затем попробуйте перемонтировать данный раздел в режим Read-Write командой mount -o remount,rw /var. Вместо «/var» подставьте раздел, который смонтирован.
3. Если не получится, напишите — подумаю ещё.
По вопросу:
chmod: cannot access ‘/var/lib/rsyslog/imjournal.state.tmp’: No such file or directory
Выполните команду ls -lh /var/lib/rsyslog/ и приложите скриншот сюда. Будем думать.
ребутните сервер, проверьте FS если понадобится
У Вас файловая система примонтирована readonly, пока не перемонтируете в rw — ничего у Вас не получится.
-
Показать ещё
Загружается…
12 июн. 2023, в 23:59
10000 руб./за проект
12 июн. 2023, в 21:24
2000 руб./в час
12 июн. 2023, в 21:17
30000 руб./за проект
Минуточку внимания
I’m trying to move a file from my local machine to another machine into which I’ve SFTP-ed.
The file has 160MB. The transfer stops after a quarter of the file is moved over, with the following message:
Copying files to remote side failed
General Failure(server should provide error description)
Error code: 4
Error message from server: Failure
asked Jan 24, 2017 at 17:09
1
This may be because space is full on your server.
Try executing df -Th command to see.
Free space on your server and try again it works.
Dharman♦
30.5k22 gold badges84 silver badges133 bronze badges
answered Aug 14, 2020 at 10:43
This would typically be due to a full file system on the server or exceeded user quota.
Actually a complete error message suggests that:
Common reasons for the Error code 4 are:
- Renaming a file to a name of already existing file.
- Creating a directory that already exists.
- Moving a remote file to a different filesystem (HDD).
- Uploading a file to a full filesystem (HDD).
- Exceeding a user disk quota.
For details, see also WinSCP documentation on the SFTP code 4.
answered Feb 1, 2017 at 15:53
Martin PrikrylMartin Prikryl
186k54 gold badges479 silver badges964 bronze badges
Создайте рассылку в конструкторе за 15 минут. Отправляйте до 1500 писем в месяц бесплатно.
Ошибка 404, либо Error 404 Not Found появляется, если браузеру не удалось обнаружить на сервере указанный URL.
Сообщение об ошибке 404
Что означает ответ 404
Error 404 Not Found отображается по-разному: «HTTP 404 не найден», «Ошибка 404 Not Found», «404 Страница не найдена». Смысл надписи всегда остаётся тем же: страница отсутствует либо просто не работает. Not Found в переводе означает «не найдено».
Ошибка 404 — классический код ответа по протоколу HTTP. Он свидетельствует, что связь с сервером установлена, но информации по заданному запросу нет.
Однако если просто ввести в поисковую строку произвольный набор символов, то браузер не покажет ошибку 404 Not Found — появится сообщение, что установить соединение с конкретным сервером невозможно.
Разберёмся в техническом формировании ответа Error 404 Not Found.
Техническая сторона вопроса. При связи по HTTP браузер запрашивает указанный URL и ждёт цифрового ответа. То есть любой запрос пользователя направляется на сервер размещения искомого сайта. Когда браузеру удаётся связаться с сервером, он получает кодированный ответ. Если запрос корректный и страница найдена, отправляется ответ с кодом 200 OK, что соответствует благополучной загрузке. При отсутствии страницы отправляется ответ об ошибке.
Что значит код «404». В ответе 404 первая четвёрка указывает на то, что запрос был чрезмерно длительным или в самом адресе была ошибка. Ноль предполагает синтаксическую неточность. Завершающая цифра кода отображает конкретную причину ошибки — «4» означает отсутствие данной ссылки.
Какие ещё ошибки бывают. Ошибку 404 не нужно путать с другими ответами, которые указывают на невозможность связи с сервером. Например, ошибка 403 сообщает, что доступ к URL ограничен, а ответ «Сервер не найден» свидетельствует, что браузер не смог обнаружить место размещения сайта.
Google на 404 странице сообщает о возможных причинах ошибки
Причины ошибки
Причины, по которым HTTP возвращает ответ 404 Not Found:
В большинстве ситуаций ошибка 404 отображается, когда не удаётся обнаружить нужную страницу на доступном сервере.
Причины отсутствия страницы на сайте бывают разными
Возможные последствия для сайта
Нужно ли считать 404 ошибку опасной для сайтов? Кажется, что нет ничего плохого в том, что пользователь не смог открыть одну веб-страницу. Однако если такая ситуация будет повторяться регулярно, это чревато оттоком аудитории. Одни пользователи решат, что сайт вовсе не существует. Другие подумают, что лучше не заходить на сайт, который работает с ошибками. Третьи будут игнорировать ресурс, на котором не смогли получить обещанную информацию.
Поисковые системы относятся к Not Found более лояльно. Например, Google отмечает, что 404 страницы не влияют на рейтинг. Но если при индексации роботы будут находить все больше ошибочных страниц, вряд ли это приведёт к более высокому ранжированию.
Если вы хотите улучшить взаимодействие с посетителями, важно найти и исправить все ошибки 404 на сайте.
Как выявить ошибку
На небольшом ресурсе легко проверить работоспособность ссылок вручную. Но если на сайте сотни и тысячи страниц, без дополнительного софта не обойтись. Есть немало сервисов и программ, позволяющих находить битые ссылки. Рассмотрим некоторые из них.
Search Console Google
Консоль поиска Google позволяет находить страницы с ошибкой 404 за несколько кликов:
Чтобы получить список страниц с ошибками, подтвердите права на ресурс — добавьте проверочную запись TXT в записи DNS регистратора домена. Такая запись не повлияет на работу сайта. Подробнее о процедуре подтверждения, читайте в справке Google.
Для использования Search Console Google нужно подтвердить свои права на сайт
Яндекс Вебмастер
Сервис для вебмастеров от Яндекса поможет быстро найти все ошибки 404:
Чтобы использовать Яндекс. Вебмастер, также нужно подтвердить право владения сайтом — добавить метатег в HTML-код главной страницы.
Для входа в Вебмастер авторизуйтесь в Яндексе
Screaming Frog
Для начала загрузите и установите программу на компьютер. После запуска добавьте URL проверяемого сайта и начните поиск проблем. Неработающие ссылки можно искать даже в бесплатной версии.
Инструмент SEO-паук в Screaming Frog помогает найти технические неисправности сайта
SiteAnalyzer
Эта бесплатная десктопная программа позволяет обнаружить технические погрешности на сайте. SiteAnalyzer быстро отыщет нерабочие и несуществующие ссылки.
SiteAnalyzer бесплатно найдёт неработающие URL
Как исправить ошибку Not Found
Выбор конкретного решения зависит от причины ошибки:
Удалять и менять ссылки вручную удобно только на небольших сайтах. Исправление ошибок на крупных порталах лучше автоматизировать. Например, с помощью специальных плагинов для внутренней перелинковки (Terms Description, Dagon Design Sitemap Generator) и для автоматического формирования адресов страниц (Cyr-To-Lat).
Чтобы ошибки 404 появлялись как можно реже, достаточно соблюдать простые рекомендации:
Мы разобрались, как найти и исправить ошибки Not Found внутри сайта. Но неработающая ссылка может быть расположена и на стороннем ресурсе. Допустим, когда-то на другом сайте разместили рекламную публикацию со ссылкой на определённую страницу. Спустя какое-то время страницу удалили. В этом случае появится ошибка 404. Устранить её можно, связавшись с администрацией ссылающегося сайта. Если же удалить/исправить ссылку нельзя, постарайтесь использовать ошибку с выгодой.
Как сделать страницу 404 полезной
Грамотно оформленная страница с ошибкой Error 404 Not Found — действенный инструмент конвертации посетителей. Ограничений по использованию страницы с ошибкой 404 нет. При этом практически все CMS позволяют настраивать дизайн этой страницы.
Что публиковать на странице 404:
При оформлении страницы-ошибки желательно опираться на рекомендации поисковиков:
Главное — по возможности отказаться от стандартной страницы 404. Подумайте, как привлечь внимание пользователя. Расскажите ему об отсутствии искомой страницы и предложите взамен что-то полезное или интересное.
Примеры оформления страниц 404
Designzillas
Мультяшная страница креативной студии привлекает внимание и её хочется досмотреть до конца. Если прокрутить страницу, можно увидеть, как из яйца вылупится дракон. При этом на странице есть ссылки на все основные разделы сайта.
Меню на сайте Designzillas есть и на 404 странице
Domenart Studio
Веб-студия «Домен АРТ» использует красочную страницу 404, оформленную в единой стилистике ресурса. Заблудившимся пользователям предлагают попробовать ещё раз ввести адрес или перейти в нужный раздел.
Контакты, поиск, меню — и всё это на 404 странице Domenart Studio
«Эко Пауэр», дистрибьютор производителя источников питания, демонстрирует короткое замыкание как символ ошибки. Посетителям предлагают перейти на главную.
Ошибка 404 «Эко Пауэр» выглядит как страница входа
Дом со всем
Компания «Дом со всем», занимающаяся бурением скважин, разместила на странице 404 свои контакты и перечень услуг. Со страницы можно перейти в любой раздел сайта или заказать обратный звонок. С таким наполнением посетителю не нужно искать дополнительную информацию где-то ещё.
Компания «Дом со всем» предлагает заказать обратный звонок
Kualo
Страница 404 на веб-хостинге Kualo может заставить пользователя забыть, зачем он сюда пришёл. Увлекательная игра притягивает внимание. В конце игры посетителю предлагают посмотреть сайт хостинга.
На странице Kualo можно просто поиграть и заработать скидки
Рано или поздно с ошибкой 404 сталкивается большинство сайтов. При регулярной проверке можно своевременно исправить неработающие ссылки, чтобы в ответ пользователи получали код 200 OK. Но для крупного ресурса лучше настроить оригинальную страницу, которая будет отображаться при появлении ошибки Not Found и подскажет посетителям, что делать дальше.
Ошибка Internal Server Error: что это и как с ней бороться
Достаточно часто владельцы хостингов мучаются из-за постоянного возникновения сообщения об ошибке 500 (Internal Server Error). Она, как это называется, многим попросту отравляет жизнь. Сейчас мы попробуем кратко разобраться в сути самой ситуации и посмотрим, как же можно избавиться от появления ошибки в будущем.
Ошибка Internal Server Error: что это?
Итак, начнем, пожалуй, с самого значения этого словосочетания. В системе (каталоге) ошибок Windows (и не только) есть ошибка под номером 500, отвечающая компьютерному термину Internal Server Error. Перевод этого словосочетания означает внутреннюю ошибку сервера, связанную со статусом протокола HTTP.
По сути, ошибка означает, что программное обеспечение сервера либо не работает, либо работает, но один или несколько его компонентов дают сбои в виде отказа на клиентские запросы, например, поисковой системы или интернет-браузера.
Причины возникновения ошибки
Говоря об ошибке Internal Server Error в самом широком понимании, стоит учитывать, что возникать она может на множестве сайтов или ресурсов, написанных с помощью совершенно разных CMS. Тут, кстати, нужно разграничить причины ее возникновения.
Очень часто такая ситуация может наблюдаться на сайтах типа WordPress, OpenCart, Joomla и др. Если же структуры управления, подобные WordPress, при построении сайта не используются, возможно, причина кроется в том, что на самом хостинге возникают сбои при подключении неправильных PHP-расширений, или сайт после запроса возвращает некорректные HTTP-заголовки, которые не могут быть распознаны вашим сервером.
Не менее распространенной причиной возникновения ошибки Internal Server Error можно назвать отсутствие корректных прав доступа. Так, например, если на PHP файлы скриптов, которые размещены на хостинге, имеют права доступа 777, очень может быть, что их исполнение попросту блокируется сервером, вследствие чего и выдается сообщение об ошибке.
Также одной из причин может быть достаточно долгая работа скриптов. Дело в том, что PHP-ограничения по времени исполнения действуют не только в отношении хостинга, подобные лимиты могут выставляться и со стороны сервера. Иными словами, это несколько напоминает тайм-аут операции. Когда сервер в течение определенного времени не получает ответа на запрос, он попросту блокирует исполнение скрипта.
В некоторых случаях ошибка Internal Server Error может появляться, когда на хостинге наблюдается превышение лимита используемой памяти. Попросту говоря, скрипт для исполнения требует больше положенного, а ведь такой лимит устанавливается не только на PHP, зачастую действуют ограничения по потреблению ресурсов всеми исполняемыми скриптами.
Ошибка Internal Server Error: как исправить простейшими способами
Для начала посмотрим, что можно сделать при обнаружении неправильных прав доступа. В данном случае права доступа 777 позволяют редактировать содержимое абсолютно всем, что, несомненно, сказывается на безопасности. В такой ситуации необходимо их изменить, применив к папкам значение 755, к файлам скриптов – 600, а ко всем стальным файлам данных – 644.
При слишком долгой работе исполняемого скрипта можно попробовать увеличить время ожидания, правда, тут есть одна загвоздка. Такое решение может сработать на выделенном сервере или VPS (Virtual Private Server), а в случае виртуального хостинга никакого эффекта не будет.
Что касается завышенного потребления памяти в сравнении с ограничениями, действующими на хостинге, тут можно посоветовать только обратиться в службу поддержки или же попросту сменить самого хостинг-провайдера, у которого ограничения будут не такими жесткими.
Проблемы с движком WordPress
Самым простым способом исправления такой ситуации является отключение темы WordPress и использование вместо нее любой другой. Если ошибка исчезла, дело именно в самой теме, если нет – нужно поэтапно отключать плагины WordPress и проверять, какой из них влияет на работоспособность.
Недостатком такого метода является только то, что в данном случае отключается обновление WordPress. При подключении плагинов они работать, естественно, не будут.
Заключение
В принципе, это, так сказать, наиболее распространенные причины появления ошибки и методы ее устранения. На самом деле, что причин, что способов борьбы с такими ситуациями может быть очень много, так что, придется анализировать ситуацию в каждом конкретном случае, а только потом выбирать, какую именно методику для исправления ошибки использовать.
Источники:
https://www. unisender. com/ru/support/about/glossary/chto-oznachaet-oshibka-404-na-sajte-i-chto-s-nej-delat/
https://fb. ru/article/196656/oshibka-internal-server-error-chto-eto-i-kak-s-ney-borotsya
Здравствуйте. При добавлении файлов записей нерабочего времени в папку /offload/asterisk/sounds/other/ через WinSCP выдаёт ошибку:
«Общая ошибка (сервер должен предоставить описание ошибки).
Код ошибки: 4
Сообщение ошибки от сервер: Failure
Обычные причины для ошибки с кодом 4:
— Смена имени файла на уже существующее.
— Создание каталога, который уже существует.
— Перемещение файла на сервере на другую файловую систему (HDD).
— Отправка файла в заполненную файловую систему (HDD).
— Превышение лимита выделенного дискового пространства.
«
Askozia 7.3.13.160
Есть решение этой проблемы? Спасибо.