vault trying unpin on an unpinned file??
Moderator: SourceGear
vault trying unpin on an unpinned file??
soon after we branched out one of our project vault started to periodically crash in the middle of our builds
It seems vault is trying to unpin files that aren't pinned at all... funny things is that we never used pinning so no clue why this unpin command is launched...
I attached the vault log, here is the interesting part:
----6/11/2007 11:48:01 PM buildmachine--vaultserver-dev.domain.com(127.0.0.1)--SSL Disabled (b5163699-bd25-4770-9a84-8ac093e91bdc) BeginTx returned: Failure
----6/11/2007 11:48:01 PM buildmachine--vaultserver-dev.domain.com(127.0.0.1)--SSL Disabled (b5163699-bd25-4770-9a84-8ac093e91bdc) Unpin: $/Project 1.0.0/BuildConfig.xml returned: FailItemNotPinned
----6/11/2007 11:48:01 PM buildmachine--vaultserver-dev.domain.com(127.0.0.1)--SSL Disabled (b5163699-bd25-4770-9a84-8ac093e91bdc) CheckIn: $/Project 1.0.0/BuildConfig.xml returned: Failure
our build system basically sends this command:
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot checkin "$/Project 1.0.0/BuildConfig.xml" -merge overwrite -unchanged undocheckout -comment "Updated Build_Num to 14"
and then returns...
<!-- Preparing data to begin transaction -->
<!-- Beginning transaction -->
<!-- Item $/Project 1.0.0/BuildConfig.xml caused the transaction to fail: The object is not pinned. -->
<!-- Transaction failed -->
As an FYI the commands sent just before were in order from the first one to the last...
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot get "$/Project 1.0.0/BuildConfig.xml" -verbose -setfiletime modification -merge overwrite -destpath E:\Temp\builds\wd.rad67EE7
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot setworkingfolder "$/Project 1.0.0" E:\Temp\builds\wd.rad67EE7 -commit
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot get "$/Project 1.0.0/BuildConfig.xml" -verbose -setfiletime modification -merge overwrite
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot checkout "$/Project 1.0.0/BuildConfig.xml" -setfiletime modification -merge overwrite -exclusive
after the command I mentionned above gets run and crashes...
I tried an IIS restart, server reboot, and a vault cache reset... no luck
interesting thing to mention is that the project we branched this one from still builds perfectly fine. another thing is last week we ran into the exact same problem and after one day and a half of trying different things, reset cache, reboot, patch the server, rollback some files... etc... finally the problem went away... but now it's back
let me know if you need more details on this
many thanks in advance
It seems vault is trying to unpin files that aren't pinned at all... funny things is that we never used pinning so no clue why this unpin command is launched...
I attached the vault log, here is the interesting part:
----6/11/2007 11:48:01 PM buildmachine--vaultserver-dev.domain.com(127.0.0.1)--SSL Disabled (b5163699-bd25-4770-9a84-8ac093e91bdc) BeginTx returned: Failure
----6/11/2007 11:48:01 PM buildmachine--vaultserver-dev.domain.com(127.0.0.1)--SSL Disabled (b5163699-bd25-4770-9a84-8ac093e91bdc) Unpin: $/Project 1.0.0/BuildConfig.xml returned: FailItemNotPinned
----6/11/2007 11:48:01 PM buildmachine--vaultserver-dev.domain.com(127.0.0.1)--SSL Disabled (b5163699-bd25-4770-9a84-8ac093e91bdc) CheckIn: $/Project 1.0.0/BuildConfig.xml returned: Failure
our build system basically sends this command:
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot checkin "$/Project 1.0.0/BuildConfig.xml" -merge overwrite -unchanged undocheckout -comment "Updated Build_Num to 14"
and then returns...
<!-- Preparing data to begin transaction -->
<!-- Beginning transaction -->
<!-- Item $/Project 1.0.0/BuildConfig.xml caused the transaction to fail: The object is not pinned. -->
<!-- Transaction failed -->
As an FYI the commands sent just before were in order from the first one to the last...
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot get "$/Project 1.0.0/BuildConfig.xml" -verbose -setfiletime modification -merge overwrite -destpath E:\Temp\builds\wd.rad67EE7
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot setworkingfolder "$/Project 1.0.0" E:\Temp\builds\wd.rad67EE7 -commit
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot get "$/Project 1.0.0/BuildConfig.xml" -verbose -setfiletime modification -merge overwrite
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host localhost -user Buildmachine -password HereIsMyPassword! -repository VaultDepot checkout "$/Project 1.0.0/BuildConfig.xml" -setfiletime modification -merge overwrite -exclusive
after the command I mentionned above gets run and crashes...
I tried an IIS restart, server reboot, and a vault cache reset... no luck
interesting thing to mention is that the project we branched this one from still builds perfectly fine. another thing is last week we ran into the exact same problem and after one day and a half of trying different things, reset cache, reboot, patch the server, rollback some files... etc... finally the problem went away... but now it's back
let me know if you need more details on this
many thanks in advance
Last edited by riptown on Tue Jun 12, 2007 12:47 pm, edited 1 time in total.
we acquired an application, including the buildmachine that is running vault server and vault database for that application, from a third party company so I can't guarantee all the details about the history behind,
however I recall them saying that they migrated their repository from source safe so I am assuming it's true
as for the version, until about 1 month ago we had 3.5.1 but then we upgraded to 3.5.2
however I recall them saying that they migrated their repository from source safe so I am assuming it's true
as for the version, until about 1 month ago we had 3.5.1 but then we upgraded to 3.5.2
here is a more detailed log
in my other log the logging was on "quiet"...
here is a more detailed version
here is a more detailed version
- Attachments
-
- detailed_log.txt
- (111.67 KiB) Downloaded 192 times
There may be an unpin operation "stuck" in the buildmachine's pending change set.
On the machine where you're running the command line client, log in to a Vault GUI Client with the buildmachine account and look in the pending change set for an unpin transaction.
Or there even could be a failed pin operation along with the unpin.
On the machine where you're running the command line client, log in to a Vault GUI Client with the buildmachine account and look in the pending change set for an unpin transaction.
Or there even could be a failed pin operation along with the unpin.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I logged in the VaultGUI on the buildmachine using the same u/p that is used for our buildprocess and I can confirm there is no pending pin or unpin operations there,
on that note nobody in the team ever use pinning... also whats funny is that we can build noproblem the project from the original branch... its only the stuff in our new branch that doesnt work
on that note nobody in the team ever use pinning... also whats funny is that we can build noproblem the project from the original branch... its only the stuff in our new branch that doesnt work
finally... we can breath a little bit now...
rebooting the server resolved the problem this time... however its the second time in 8 days we experience this 'unpin' thing and we only end up resolving the problem by doing random things till it works again... reboot, restart IIS, rollback some files, ...
anything you guys can think that can lead us to a more permanent resolution would be much appreciated
rebooting the server resolved the problem this time... however its the second time in 8 days we experience this 'unpin' thing and we only end up resolving the problem by doing random things till it works again... reboot, restart IIS, rollback some files, ...
anything you guys can think that can lead us to a more permanent resolution would be much appreciated