VaultService's application pool maxing out the CPU

[mweaver]

We have been using Vault Server 2.0.0 on Windows Server 2003 (IIS 6.0)for several months now with few problems. Today we were unable to access the server at all. I checked Task Manager and saw that w3wp.exe (the DefaultAppPool) was taking up all of the CPU.

I stopped the DefaultAppPool and decided to put VaultService into its own application pool (VaultAppPool). I restarted DefaultAppPool (without VaultService) and it worked fine - minimal CPU usage. I started VaultAppPool (With only VaultService) and its CPU usage immediately jumped to nearly 100%. This is without any client connections. I checked db activity and there was no process connecting to the sgvault database.

My next attempt was to install Vault Server 2.0.0.6 - and the install/upgrade appeared to be succesful. However, even with the latest version, VaultService is still using up the entire CPU (making VaultService and the rest of the server virtually useless).

In summary, VaultService has its very own application pool, VaultAppPool. As soon as VaultAppPool starts, it immediately jumps to nearly 100% CPU usage. This is without any connections from any Vault clients - and there is also no Sql Server process connected to sgvault db.

What can VaultService be doing that is taking the entire CPU? And more importantly, how can I fix it?

[mweaver]

In addition to the situation described above, VaultService is not even creating an sgvault.log file. I removed all of the existing *.log files (C:\WINDOWS\Temp\sgvault\) and then restarted the VaultAppPool (containing VaultService). Again, the CPU immediately jumped to ~100%. I was hoping to review sgvault.log to see if it contained any useful information - but that file was not even created. So, whatever is maxing out the CPU is happening before the *.log file is even created.

[jclausius]

Is this a new installation? The creation of the log file is one of the first startup tasks. If the service is going haywire before the log is created, an incorrect configuration with the setup is suspect.

If it is a new installation, try a complete uninstall (you can keep the database), and reinstall.

If this is an existing installation, examine web.config. Anything in the connect string or config path look odd?

[mweaver]

This is an existing installation - it has been working just fine for several months.

I have attached the web.config file from the VaultService folder.

[mweaver]

Here is the VaultService\web.config file. It uses integrated security. The VaultAppPool is running as "Network Service" and Network Service is a valid Sql Server login with access to the sgvault database.

I have also include the VaultService\Vault.config file - in case that is useful.

[mweaver]

I just tried starting VaultAppPool again ... just to see what happens.

So far, it is NOT hogging the CPU, and everything seems to be working.

This time it DID create a log file, and this was the first entry:

----9/27/2004 9:46:30 AM sgvaultsystem--()--
A configuration error occurred reading [DelayThreshold] from Vault.Config. ConfigReader reported the following error: The section could not be found within vault.config.

I checked the Vault.config file, adn the <DeleayThreshold> setting is NOT there. Should it be? What should the value be?

[jclausius]

You don't have to add them, but the missing values in Vault.Config are

<DelayThreshold>10</DelayThreshold>
<DelayDurationSeconds>30</DelayDurationSeconds>

As for the CPU usage, let's keep an eye on things, and see what happens.