Hello,
We are on newest release of vault (version 4) and is experiencing a certain phenomenon. At either 1 PM CST or 2PM CST, vault client is VERY SLOW at getting the files. I have checked the server to see any external processes working (ie Virus Scan). At this time, only two people are logged in (build team) and it takes FOREVER to get a 4kb file.
We do index our database on a weekly basis and the server is defragged along with 4 gb of ram and we have already done optimization through many topics of the forum (thanks beth).
Vault is slow AT certain times of the day
Moderator: SourceGear
How many websites are served up by that same server? Are there other programs on that server being access that may have higher traffic?
How about the SQL server? If it's busy doing other things at that time, it could take longer to respond.
You might want to make user of the Windows monitoring to see what the server does throughout the day. There's also other tools available that can help troubleshoot such as a packet sniffer. It will take someone who knows your network from a bigger picture to see what's happening.
Some things you can check on the Vault side is the Vault Server Log and the Event Viewer logs for errors. That may provide more information.
What about automatic updates?
How about the SQL server? If it's busy doing other things at that time, it could take longer to respond.
You might want to make user of the Windows monitoring to see what the server does throughout the day. There's also other tools available that can help troubleshoot such as a packet sniffer. It will take someone who knows your network from a bigger picture to see what's happening.
Some things you can check on the Vault side is the Vault Server Log and the Event Viewer logs for errors. That may provide more information.
What about automatic updates?
There is only website running on that server which is the vault website (no one is using it).How many websites are served up by that same server?
The server is only used for vault.Are there other programs on that server being access that may have higher traffic?
SQL server is on the same machine.How about the SQL server? If it's busy doing other things at that time, it could take longer to respond.
I have it installed and vault server executable is PEGGED red. I will provide a screenshot.You might want to make user of the Windows monitoring to see what the server does throughout the day. There's also other tools available that can help troubleshoot such as a packet sniffer. It will take someone who knows your network from a bigger picture to see what's happening.
What about automatic updates?Updates are installed on a nightly basis and is approved through the security manager.
Beth,
One of our users tried to login BUT was given a "password is incorrect" screen. His password is stored in the profile. It is the password he logons onto the domain (which our vault client is using domain authentication).
Here is what's in the Client Log. There is a whole slaw of them. I cut out just a few lines to the bottom of the file.
Code: Select all
11/26/2007 11:34:16 AM <generic>: [Main:584] IsModified(): Could not determine files status for D:\Vault\OURREPOSITORY\Source\NETASPSource\TESTSITESECURE\webservices\Extensions\Validation\Prototype\ValidationExtensionReflector.vb
11/26/2007 11:34:16 AM <generic>: [Main:584] Error: Object reference not set to an instance of an object.
11/26/2007 11:34:16 AM <generic>: [Main:584] Returning: False for file modification status
11/26/2007 11:34:16 AM <generic>: [Main:584] IsModified(): Could not determine files status for D:\Vault\OURREPOSITORY\Source\NETASPSource\TESTSITESECURE\webservices\Extensions\Validation\Prototype\ValidationFormatExtension.vb
11/26/2007 11:34:16 AM <generic>: [Main:584] Error: Object reference not set to an instance of an object.
11/26/2007 11:34:16 AM <generic>: [Main:584] Returning: False for file modification status
11/26/2007 11:34:16 AM <generic>: [Main:584] IsModified(): Could not determine files status for D:\Vault\OURREPOSITORY\Source\NETASPSource\TESTSITESECURE\webservices\Extensions\Validation\Prototype\ValidationSchemaAttribute.vb
11/26/2007 11:34:16 AM <generic>: [Main:584] Error: Object reference not set to an instance of an object.
11/26/2007 11:34:16 AM <generic>: [Main:584] Returning: False for file modification status
11/26/2007 11:34:16 AM <generic>: [Main:584] IsModified(): Could not determine files status for D:\Vault\OURREPOSITORY\Source\NETASPSource\TESTSITESECURE\webservices\Extensions\Validation\Prototype\ValidationSchemaCacheAttribute.vb
11/26/2007 11:34:16 AM <generic>: [Main:584] Error: Object reference not set to an instance of an object.
11/26/2007 11:34:16 AM <generic>: [Main:584] Returning: False for file modification status
1/11/2008 1:57:37 PM <generic>: [Main:2476] Emergency logging enabled in Windows Forms client
1/11/2008 1:57:41 PM <generic>: [Main:2476] Emergency logging enabled in Windows Forms client
1/11/2008 2:01:45 PM <statussearch>: [Main:2476] GetSettingTable started
1/11/2008 2:01:46 PM <statussearch>: [Main:2476] GetSettingTable finishedDid the user either change his password for logging onto the Domain recently or use the Change Password feature in Vault? Was it working for this user previously?One of our users tried to login BUT was given a "password is incorrect" screen. His password is stored in the profile. It is the password he logons onto the domain (which our vault client is using domain authentication).
The client log you posted says 11:34 am and you said the slowdown occurs at 1-2 pm. Is there a time different between the client and server?
Can I get the Vault Server Log that corresponds to the slow-down time or just the entire log? You can either post it here or send it to me in an email at support at sourcegear.com (attn: Beth) with a link to this forum thread.
Hey Beth,
Well, here's what I'm thinking with the client log you saw with the 11AM. Since there are threads being run to retrieve items from the database, well I'm thinking that the process has been running since 11:34AM. So you saw for that particular user, that the time started at 11:34 AM. Then at around 1:30 PM, i did the client logging and it was working on that thread. I will gather the server log today and send it your way.
BTW, the user did not change his password that day or recently. I checked in the domain about his status and his password is still valid (days, length,etc). After vault decided to work properly (5pM) he logged into vault with the same credentials and it worked.
Well, here's what I'm thinking with the client log you saw with the 11AM. Since there are threads being run to retrieve items from the database, well I'm thinking that the process has been running since 11:34AM. So you saw for that particular user, that the time started at 11:34 AM. Then at around 1:30 PM, i did the client logging and it was working on that thread. I will gather the server log today and send it your way.
BTW, the user did not change his password that day or recently. I checked in the domain about his status and his password is still valid (days, length,etc). After vault decided to work properly (5pM) he logged into vault with the same credentials and it worked.
With not being able to determine the file status in the client, it makes me wonder if the user doesn't have something occurring on the client-side that is getting in the way instead of on the server side?
If you install a client right onto the server, does it experience the same slowness at the same time of day?
If you install a client right onto the server, does it experience the same slowness at the same time of day?