SOS 4.1.2 CPU Utilisation ~ 100%

[pigroup]

We have upgraded from SOS 3.5 to 4.1.2 recently, and have noticed once a week that users cannot connect to any databases.

Looking at the windows task manager, the SOS server process is utilising the CPU very heavily, 90-95% in fact. A restart of the service seems to fix this.

This also happened with 3.5 server.

Any information gratefull received.

[lbauer]

Are any SOS clients using the SOS Server at the time the CPU usage is up? If so what type of operations are they doing?

What version of the VSS automation component is on the SOS Server machine? See this KB article on how to find out:
http://support.sourcegear.com/viewtopic.php?t=1510

Is there anything unusual in the SOS Server log during this time? It's log.txt and is in the SOS Server directory.

[pigroup]

There seemed to be a maximum of 6-7 users active at this time. They said it took a long time to open the tree structure for some Databases, which isn't normal behaviour.

The VSS component is version 6.0.81.69.

There doesn't seem anything untoward in the log.txt file.

Thank you.

[lbauer]

You might want to review this KB article about optimizing SOS peformance. Some of the tips may help:
http://support.sourcegear.com/viewtopic.php?t=2575

[Softeq]

I have the exact same problem with 4.1. We only have a few users accessing it. Every so often SOS service will consume 95% of the CPU, and when we notice it no one is logged in or doing anything with SOS.

Stopping and restarting the service will fix the problem, but it is annoying.

[lbauer]

We've had a few reports of this, but haven't been able to reproduce it reliably here. I'd add this info to task we have logged to review overall performance of SOS.

[Jahntassa]

I've seen this as well, though usually only with one user logged in. For some reason SoS just decides to use 95% CPU time and essentially 'locks up'

[lbauer]

For those of you with the high CPU usage:

We'd like to determine if this is related to the version of the VSS automation component SOS is using to communicate with the VSS database.

See this KB article to find out what version you have on the SOS Server machine.

http://support.sourcegear.com/viewtopic.php?t=1510

Then post the following info:

1)SOS Client version
2)SOS Server version
3) Ssapi.dll version

Perhaps we can see a pattern and reproduce the problem so we can fix it.

[sbalki]

1) SOS Client version - 4.1.2
2) SOS Server version - 4.1.2
3) Ssapi.dll version - 6.0.96.4

Windows 2000 Adv. Server

[pigroup]

We are using Windows 2003 Standard, with the same versions as above.

[pigroup]

Hi,

We seem to be getting this problem occurring more regularly. We have scheduled to restart the service twice daily, which obviously logs off any currently logged in users, and isn't the most preferred work-a-round methods. Even so, I still get complaints that SOS becomes unusable.

Do you have any updates on why this is happening?

Thank you

Lee

[lbauer]

We don't have an update, as we have not yet determined the cause -- we have not been able to reproduce this behavior.

But this is a top priority for us.

We'd like you -- and any other users experiencing disconnects or excess CPU utilization to enable both Verbose and Method logging. Details here:

http://support.sourcegear.com/viewtopic.php?t=463

Note: these logs can get large -- be sure to turn off at least Method logging after you've sent your log to SourceGear.

Email your log to linda at SourceGear.com