Vault Command line problem retrieving files with label
Moderator: SourceGear
Vault Command line problem retrieving files with label
On my build machine, I have scripts that use the command line version, Vault.exe. Normally the build works fine, but occasionally the "getlabel" command to retrieve the files will fail for certain folders. Running the comand again usually results in consistent failure once it occurs. Only rebooting the build machine will resolve the problem.
I have collected client and server logs from the event and attached them here.
Please let me know what other information you might need.
Thanks,
Mike Ballou
I have collected client and server logs from the event and attached them here.
Please let me know what other information you might need.
Thanks,
Mike Ballou
- Attachments
-
- VaultLog.zip
- Client and server logs
- (33.68 KiB) Downloaded 770 times
I'm running 3.1.0 (3494) on both the build machine and the source server.
I haven't tried getting an older label when the problem occurs. When it happens again I will try that.
The build process right now applies a label to 3 different folders recursively. Then it performs a Getlabel on the same 3 folders with the same label it just applied. The first two folders are small and don't contain a lot of files. The 3rd folder has many more files and is where the failure occurs.
Normally this works as expected, but occasionally it starts to fail for unknown reasons at this time. I can access the vault server without problem when the issue occurs.
I don't think it would cause any issues, but the communication between the build machine and the server is using IPSec with certificates.
This problem has occured since I started using Vault about 3 releases ago. I just now had time to collect logs and post them here.
Let me know what other information you need.
Thanks for your quick response!
Mike Ballou
I haven't tried getting an older label when the problem occurs. When it happens again I will try that.
The build process right now applies a label to 3 different folders recursively. Then it performs a Getlabel on the same 3 folders with the same label it just applied. The first two folders are small and don't contain a lot of files. The 3rd folder has many more files and is where the failure occurs.
Normally this works as expected, but occasionally it starts to fail for unknown reasons at this time. I can access the vault server without problem when the issue occurs.
I don't think it would cause any issues, but the communication between the build machine and the server is using IPSec with certificates.
This problem has occured since I started using Vault about 3 releases ago. I just now had time to collect logs and post them here.
Let me know what other information you need.
Thanks for your quick response!
Mike Ballou
Not much in the log files, except the failure message in each:
Client:
and this in the sgvault.log:
When this happens again, check the Taskmanager in the client to see if system resources are being used up.
Since it's an intermittent problem, it might be tricky to pin down. Try the command from different machine. Try using the GUI Client for the same Getbylabel. Maybe we can determine the conditions under which this fails or succeeds.
Client:
)8/19/2005 11:49:48 AM <get>: [<No Name>:2284] Exception during BeginDownloadLabelFiles: 2100 : FailExistingDownload
at VaultClientNetLib.VaultConnection.BeginDownloadLabelFiles(Int32, String, Int64, VaultRequestGetFile[]&, String&)
at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(GetFileInfo[], MakeWritableType, SetFileTimeType, MergeType, Boolean, String, Boolean, String, OverwritePrompt, Boolean, String, Int64, Boolean
and this in the sgvault.log:
This sounds like a client-side problem, especially because rebooting the build machine gets the command working again. A re-boot might clear a temp directory, release memory . . .----8/19/2005 11:49:48 AM build--av-builds.corp.int-eeye.com(10.100.25.200)--SSL Disabled Beginning label file download
----8/19/2005 11:49:48 AM build--av-builds.corp.int-eeye.com(10.100.25.200)--SSL Disabled FailExistingDownload
When this happens again, check the Taskmanager in the client to see if system resources are being used up.
Since it's an intermittent problem, it might be tricky to pin down. Try the command from different machine. Try using the GUI Client for the same Getbylabel. Maybe we can determine the conditions under which this fails or succeeds.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I did that to get the files. It didn't give me any errors, but it looks like some files were not updated.
I'm not sure if this is related or not, but along with the previous error, sometimes it gives me this result instead:
<vault>
<!-- An error occurred reading from the download stream ("Unable to read data from the transport connection."), retrying... -->
<!-- An error occurred reading from the download stream ("Unable to read data from the transport connection."), retrying... -->
<!-- An error occurred reading from the download stream ("Unable to read data from the transport connection."), retrying... -->
<!-- Too many errors were encountered downloading files. Some files may not have been updated. -->
<result success="yes" />
</vault>
The scary part about this is that even though it got errors, it still returns success, so teh buidl keeps going without getting all the files.
I'm trying to track down more information for this problem. In the meantime, do you know anything about the "result success="yes"" problem?
Thanks,
Mike Ballou
I'm not sure if this is related or not, but along with the previous error, sometimes it gives me this result instead:
<vault>
<!-- An error occurred reading from the download stream ("Unable to read data from the transport connection."), retrying... -->
<!-- An error occurred reading from the download stream ("Unable to read data from the transport connection."), retrying... -->
<!-- An error occurred reading from the download stream ("Unable to read data from the transport connection."), retrying... -->
<!-- Too many errors were encountered downloading files. Some files may not have been updated. -->
<result success="yes" />
</vault>
The scary part about this is that even though it got errors, it still returns success, so teh buidl keeps going without getting all the files.
I'm trying to track down more information for this problem. In the meantime, do you know anything about the "result success="yes"" problem?
Thanks,
Mike Ballou
I narrowed it down to a single file that is causing problems.
If I do a getlabel of the folder the file is in, then it will get the error. The folder has 4 binary files in it. 1 exe, 2 pdf files, and 1 chm file. The folder is completely empty before doing the getlabel.
If I do a getlabel on the the exe file, it works fine. Then if I do the getlabel on the folder, it works correctly.
So something weird is happening with that one executable. The filename is HelpWizard.exe. Again, this doesn't always happen, but once it starts happening, it keeps going until I reboot the machine.
Any ideas come to mind that might help me with this issue?
Thanks,
Mike Ballou
If I do a getlabel of the folder the file is in, then it will get the error. The folder has 4 binary files in it. 1 exe, 2 pdf files, and 1 chm file. The folder is completely empty before doing the getlabel.
If I do a getlabel on the the exe file, it works fine. Then if I do the getlabel on the folder, it works correctly.
So something weird is happening with that one executable. The filename is HelpWizard.exe. Again, this doesn't always happen, but once it starts happening, it keeps going until I reboot the machine.
Any ideas come to mind that might help me with this issue?
Thanks,
Mike Ballou
Ahh.. Finally figured it out. We have Symantec AntiVirus install on the build machine. I always stop the antivirus service before running a build, so it wasn't a problem with that.
But there is a Symantec Event Manager service that is running that seemed to cause the problem. Once I stopped that service the problem goes away. If I restart the service, the problem comes back.
Thank you to the Source Gear support guys for quick replies in this problem.
Mike Ballou
But there is a Symantec Event Manager service that is running that seemed to cause the problem. Once I stopped that service the problem goes away. If I restart the service, the problem comes back.
Thank you to the Source Gear support guys for quick replies in this problem.
Mike Ballou