Problem with command line download, but not in the GUI

[rayres@claritas.com]

Using source offsite 3.5.3 on a Win2K SP4 system.

When getting latest on a full project from the command line, the download hangs with no error, (read - needs to be killed after hours) on the same file each time we do a command line get latest. If we run the same get from the GUI, the file and directory download without a problem.

The file we are getting hung on is binary. I'm thinking it isn't of a particular size that is a problem since we are doing other files in the same project without problem either command line or GUI.

I'm not sure how to proceed with debugging the command line calls or what I should do next. I'd appreciate any help I could get.

thanks,
russ

[lbauer]

Can you do a get of just that one file from the command line? What about the parent directory of that file? Is it just in the long recursive get that it hangs?

The log file might have some clues. First, set logging to debug:

http://support.sourcegear.com/viewtopic.php?t=463

Do the Get with the GUI client. Then do the Get with the CLC and compare the gets in the log.

If you want to email the log to me, I can take a look, too.

[rayres@claritas.com]

The info appears to be the reset by peer from the log below, but we don't seem to get that same message from the GUI, just the command line. Any other ideas?

---- cut from the log (and I changed the machine and ip addresses)
Thu Mar 18 14:42:36 PST 2004 - machine (100.196.110.120) - Begin Get File Operation: jre.zip
Thu Mar 18 14:42:37 PST 2004 - machine(100.196.110.120) - Getting version information
Thu Mar 18 14:42:37 PST 2004 - machine(100.196.110.120) - Version information obtained
Thu Mar 18 14:43:45 PST 2004 - machine(100.196.110.120) - Connection reset by peer
Thu Mar 18 14:43:45 PST 2004 - machine(100.196.110.120 - Connection reset by peer
Thu Mar 18 14:43:46 PST 2004 - machine(100.196.110.120) - User "hborda" disconnected

[lbauer]

I was able to get a 50 MB zip file with the SOS GUI client, but not with the CLC. The operation just stopped after a while, taking 99% CPU. So there may be a limitation in the CLC -- it is not as efficient in getting such a large file.

You may be getting the connection reset messages because the connection is being reset by a third party because nothing's happening.

I tried this with SOS 4.0 and the results were the same.