Very annoying stall on upload bug

When uploading via WinSCP, it very often happens that the status bar indicates that the entire file has been completely uploaded in terms of bytes, but the server seems not to have acknowledged it yet and WinSCP stalls - sometimes forever - trying to wait for that acknowledgement.

Quite often, the file really is already present on the server, although sometimes it isn't yet.

Does anyone know how to avoid this behaviour? Is this a problem with the ssh protocol and is it possible to circumvent this with some clever heuristics? Or perhaps we have configured some settings wrongly? (I set server response timeout to 20-30 secs, execue keep alive via dummy protocol commands every 20 secs)

I have to congratulate prikryl for giving us WinSCP which is such a nice and well designed program that has tremendously boosted our development productivity and removing this little annoyance would seem to be the last step towards development nirvana (we interactively edit files on the server and save every few minutes and this small problem is really killing the workflow speed).

I should also note that this may be happening more often with small files (e.g. <10K in size) (or perhaps just get noticed more often...)


This has happened across all the versions of WinSCP in recent memory, including the latest stable one, I have not yet tried the beta though.

I have not done scientific verification yet, but it also seems to happen on all the different servers we've tried accessing via WinSCP and on all ISP connections (good or bad) that we have used.

Transfer protocol is SFTP, maybe SCP should be default?

no fault of prog think...

there is no com bw client/server
some went async. cause ??

maybe, your antivir prog tries to control...
in this case, transfer fails everytime cause of timeout.
try disable outgoing network scan/control.

btw: never had such problems, be sure your not
infected with some shit...

hth...

Telepath wrote:

maybe, your antivir prog tries to control...
in this case, transfer fails everytime cause of timeout.
try disable outgoing network scan/control.

btw: never had such problems, be sure your not
infected with some shit...

hth...

This happens quite regularly on many different computers and setups.

WinSCP's GUI also seems much more prone to hanging/stalling compared to other FTP clients, e.g. the screen does not want to redraw (waiting for packets?) (with "not responding" coming out on the title bar). I think the two problems are related. It may be the way WinSCP handles the situation on bad connections. Fwiw, it's not the only program that behaves like this, SQLYog is also prone to such GUI hangs.


.

Please post a full log file showing the problem.

Could someone help me with this? I am using WinSCP to transfer data from local directory to remote directory. However, I meet with a problem because I fail to upload my data to the server. I cannot solve this since few days ago.


<?php /// Moodle Configuration File

unset($CFG);

$CFG->dbtype = 'mysql';
$CFG->dbhost = 'localhost';
$CFG->dbname = 'moodle';
$CFG->dbuser = 'xxx';
$CFG->dbpass = 'ti';
$CFG->dbpersist = false;
$CFG->prefix = 'mdl_';

$CFG->wwwroot = 'http://localhost/moodle';
$CFG->dirroot = 'D:\xampp\htdocs\moodle';
$CFG->dataroot = 'D:\xampp\moodledata';
$CFG->admin = 'admin';

$CFG->directorypermissions = ; // try on a server in Safe Mode

$CFG->passwordsaltmain = '&;Zl(~,Ay9#[w[=%';

require_once("$CFG->dirroot/lib/setup.php");
// MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,
// RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.
?>




Warning: main(D:\xampp\htdocs\moodle/lib/setup.php): failed to open stream: No such file or directory in /Users/student/ting/Sites/xampp/moodle/config.php on line 22

Fatal error: main(): Failed opening required 'D:\xampp\htdocs\moodle/lib/setup.php' (include_path='.:/Applications/xampp/xamppfiles/lib/php') in /Users/student/ting/Sites/xampp/moodle/config.php on line 22