Cruise Control and Draconet and Vault Version 3.0.7.2863
Moderator: SourceGear
-
- Posts: 14
- Joined: Mon Nov 28, 2005 6:25 pm
Cruise Control and Draconet and Vault Version 3.0.7.2863
When we have multiple projects accessing vault we almost always get periodic errors (i am assuming from multiple connections timing out).
I am not the Vault admin, but can you tell me if there are connection throttles on the server that would prevent an ip from making multple simultaneous connections to vault?
Error is always the same (unless it builds alone):
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: . Process command: c:\program files\sourcegear\vault client\vault.exe history $/DesktopModules/Gallery -excludeactions label -rowlimit 0 -begindate 2005-11-28T18:58:25 -enddate 2005-11-28T19:28:26 -host source.modified.com -user modified -password modified -repository Mod_Gallery at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute(ProcessInfo processInfo) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.GetModifications(ProcessInfo info, DateTime from, DateTime to) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vault.GetModifications(IIntegrationResult from, IIntegrationResult to) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications(ISourceControl sourceControl, IIntegrationResult lastBuild, IIntegrationResult thisBuild) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.RunIntegration(BuildCondition buildCondition)
Thanks!
I am not the Vault admin, but can you tell me if there are connection throttles on the server that would prevent an ip from making multple simultaneous connections to vault?
Error is always the same (unless it builds alone):
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: . Process command: c:\program files\sourcegear\vault client\vault.exe history $/DesktopModules/Gallery -excludeactions label -rowlimit 0 -begindate 2005-11-28T18:58:25 -enddate 2005-11-28T19:28:26 -host source.modified.com -user modified -password modified -repository Mod_Gallery at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute(ProcessInfo processInfo) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.GetModifications(ProcessInfo info, DateTime from, DateTime to) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vault.GetModifications(IIntegrationResult from, IIntegrationResult to) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications(ISourceControl sourceControl, IIntegrationResult lastBuild, IIntegrationResult thisBuild) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.RunIntegration(BuildCondition buildCondition)
Thanks!
-
- Posts: 14
- Joined: Mon Nov 28, 2005 6:25 pm
Sorry, I don't think I've seen anything related to this, unless your ISA server configuration limits the number of connection.
If you create a batch file with the Vault command line / start.cmd to start about 5-10 CLC's to do something, do you still see the same blocked behavior? What if you run this batch file / CLC launcher on the Vault server itself?
In case this is a Cruise Control issue, I'm going to ask someone more familiar w/ CC.Net to take a look as well.
If you create a batch file with the Vault command line / start.cmd to start about 5-10 CLC's to do something, do you still see the same blocked behavior? What if you run this batch file / CLC launcher on the Vault server itself?
In case this is a Cruise Control issue, I'm going to ask someone more familiar w/ CC.Net to take a look as well.
Jeff Clausius
SourceGear
SourceGear
Bryan,
If you set Cruise Control's logging to debug, we can get a better idea what's failing here. This can be accomplished by un-commenting this line:
from ccservice.exe.config if you're running Cruise Control as a service or ccnet.exe.config if you're running the console server. If you can post the error and a few lines before and after it, we'll have a better idea.
If you set Cruise Control's logging to debug, we can get a better idea what's failing here. This can be accomplished by un-commenting this line:
Code: Select all
<!-- <add name="CruiseControlSwitch" value="4" /> --> <!-- Debug: All messages -->
Ian Olsen
SourceGear
SourceGear
-
- Posts: 14
- Joined: Mon Nov 28, 2005 6:25 pm
log entries - from one of the 6 vault processes that run
11/29/2005 9:53:14 AM: [DotNetNuke.Forum:Info]: Checking for modifications in Vault from 11/29/2005 9:51:53 AM to 11/29/2005 9:53:14 AM
11/29/2005 9:53:14 AM: [DotNetNuke.Forum:Debug]: Vault History command: FileName: [c:\program files\sourcegear\vault client\vault.exe] -- Arguments: [history $/DesktopModules/Forum -excludeactions label -rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host MODIFIED -user MODIFIEDUSER -password MODIFIED -repository Mod_Forums] -- WorkingDirectory: [C:\Program Files\CruiseControl.NET\server\DotNetNuke.Forum\WorkingDirectory] -- StandardInputContent: [] -- Timeout: [120000]
11/29/2005 9:53:14 AM: [DotNetNuke.Forum:Debug]: Executing process c:\program files\sourcegear\vault client\vault.exe history $/DesktopModules/Forum -excludeactions label -rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host MODIFIED -user MODIFIEDUSER -password MODIFIED -repository Mod_Forums in C:\Program Files\CruiseControl.NET\server\DotNetNuke.Forum\WorkingDirectory
11/29/2005 9:53:14 AM: [DotNetNuke.Forum:Debug]: Attempting to start process [c:\program files\sourcegear\vault client\vault.exe] in working directory [C:\Program Files\CruiseControl.NET\server\DotNetNuke.Forum\WorkingDirectory] with arguments [history $/DesktopModules/Forum -excludeactions label -rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host MODIFIED -user MODIFIEDUSER -password MODIFIED -repository Mod_Forums]
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: <vault>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: <error>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. 1109 : FailDBUpdate
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: </error>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: <exception>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: System.Exception: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. 1109 : FailDBUpdate
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.Login(Boolean bAllowAuto, Boolean bSaveSession)
11/29/2005 9:53:53 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandHistory(String strReposPath)
11/29/2005 9:53:53 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: </exception>
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: <result success="no" />
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: </vault>
11/29/2005 9:53:14 AM: [DotNetNuke.Forum:Debug]: Vault History command: FileName: [c:\program files\sourcegear\vault client\vault.exe] -- Arguments: [history $/DesktopModules/Forum -excludeactions label -rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host MODIFIED -user MODIFIEDUSER -password MODIFIED -repository Mod_Forums] -- WorkingDirectory: [C:\Program Files\CruiseControl.NET\server\DotNetNuke.Forum\WorkingDirectory] -- StandardInputContent: [] -- Timeout: [120000]
11/29/2005 9:53:14 AM: [DotNetNuke.Forum:Debug]: Executing process c:\program files\sourcegear\vault client\vault.exe history $/DesktopModules/Forum -excludeactions label -rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host MODIFIED -user MODIFIEDUSER -password MODIFIED -repository Mod_Forums in C:\Program Files\CruiseControl.NET\server\DotNetNuke.Forum\WorkingDirectory
11/29/2005 9:53:14 AM: [DotNetNuke.Forum:Debug]: Attempting to start process [c:\program files\sourcegear\vault client\vault.exe] in working directory [C:\Program Files\CruiseControl.NET\server\DotNetNuke.Forum\WorkingDirectory] with arguments [history $/DesktopModules/Forum -excludeactions label -rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host MODIFIED -user MODIFIEDUSER -password MODIFIED -repository Mod_Forums]
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: <vault>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: <error>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. 1109 : FailDBUpdate
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: </error>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: <exception>
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: System.Exception: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. 1109 : FailDBUpdate
11/29/2005 9:53:52 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.Login(Boolean bAllowAuto, Boolean bSaveSession)
11/29/2005 9:53:53 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandHistory(String strReposPath)
11/29/2005 9:53:53 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: </exception>
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: <result success="no" />
11/29/2005 9:53:54 AM: [CruiseControl Server:Debug]: </vault>
Okay it looks to me like Jeff's original diagnosis was correct: something other than Vault is imposing a concurrent connection limit. The ISA server sounds like a good first thing to investigate. I'd also double-check the IIS configuration, as it is possible to impose a limit even on a server OS.
Ian Olsen
SourceGear
SourceGear
You may also want to look at your Vault server log file to see if you can see the login attempt from the server's point of view.
Jeff Clausius
SourceGear
SourceGear
-
- Posts: 14
- Joined: Mon Nov 28, 2005 6:25 pm
Well Cruise Control logs a message when it kills a process due to timeout, which we're not seeing, so that's one less possibility.
When you tried the 5 simultaneous command-line clients, were they running roughly the same commands that CC.NET runs? Did the last one take longer than the 38 seconds we got from CC.NET?
When you tried the 5 simultaneous command-line clients, were they running roughly the same commands that CC.NET runs? Did the last one take longer than the 38 seconds we got from CC.NET?
Ian Olsen
SourceGear
SourceGear
-
- Posts: 14
- Joined: Mon Nov 28, 2005 6:25 pm
-
- Posts: 14
- Joined: Mon Nov 28, 2005 6:25 pm
I am not the greatest at batch files so.... i created one for each and just execute them as quickly as i can. If you know a way that will allow me to execute them simultaneously i can try that. Yes they are the closest i could get to being the same (tell me if i am missing something):
"c:\program files\sourcegear\vault client\vault.exe" history $/DesktopModules/Gallery -excludeactions label
-rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host source.MODIFIED.com -username
MODIFIED -password MODIFIED -repository "Mod_Gallery" -DESTPATH
C:\CCBuilds\DotNetNuke\DotNetNuke_3.2.0-Release\DesktopModules\Gallery
I have tried executing 5 of these with the HISTORY and GET commands.
"c:\program files\sourcegear\vault client\vault.exe" history $/DesktopModules/Gallery -excludeactions label
-rowlimit 0 -begindate 2005-11-29T09:51:53 -enddate 2005-11-29T09:53:14 -host source.MODIFIED.com -username
MODIFIED -password MODIFIED -repository "Mod_Gallery" -DESTPATH
C:\CCBuilds\DotNetNuke\DotNetNuke_3.2.0-Release\DesktopModules\Gallery
I have tried executing 5 of these with the HISTORY and GET commands.
-
- Posts: 14
- Joined: Mon Nov 28, 2005 6:25 pm
From the logs:
11/29/2005 4:41:00 PM MODIFIED--MODIFIED.org(xxx.xxx.xxx.xxx)--SSL Disabled Transaction (Process ID 82) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
11/29/2005 4:41:00 PM MODIFIED--MODIFIED.org(xxx.xxx.xxx.xxx)--SSL Disabled Login failed: FailDBUpdate
11/29/2005 4:41:00 PM MODIFIED--MODIFIED.org(xxx.xxx.xxx.xxx)--SSL Disabled Transaction (Process ID 82) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
11/29/2005 4:41:00 PM MODIFIED--MODIFIED.org(xxx.xxx.xxx.xxx)--SSL Disabled Login failed: FailDBUpdate