topic Memory leak in cpqteam.sys? in Windows Server 2003

Memory leak in cpqteam.sys?

Rikard Nilsson — Wed, 25 Jul 2007 04:06:47 GMT

Hi all,

We have a IIS that randomly stops serving pages.

1. Found connection_refused errors problems in our intranetservers (Windows Server 2003 SP2) httperr.log file,

2. Googled a little bit and found this http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO_Diagnose_IIS6_failing_to_accept_connections_due_to_Connections_Refused.aspx
article

3. C:\> poolmon -b -n

4. Checked the poolsnap.log file and the topmost driver sorted by memoryusage

Tag Type Allocs Frees Diff Bytes Per Alloc
NTID Nonp 12263728 12170319 93409 168397912 1802

5. C:\> cd c:\windows\system32\drivers

6. C:\> findstr /m /l NTID *.sys
cpqteam.sys

Everytime I check the used allocated memory on this server the NTID has grabbed more memroy.

If I let the server run, for 3-4 days the IIS will stop responding and serving pages.

The hardware is ProLiant BL460c G1 with a cpqteam.sys driver version 8.55.0.0.

Any clues?

Kind rega

Re: Memory leak in cpqteam.sys?

Rikard Nilsson — Wed, 25 Jul 2007 05:59:14 GMT

Update:
1. Upgraded the driver to 8.70.0.0
2. Upgraded HP Network Configuration Utility for Windows Server 2003

I'll see if it helps.

Kind regards,

/Rikard

Re: Memory leak in cpqteam.sys?

Rikard Nilsson — Fri, 27 Jul 2007 01:21:57 GMT

Update:

So far so good...the NTID has not "eaten" as much memory as before...

Kind regards,

/Rikard

Re: Memory leak in cpqteam.sys?

Patrick Buser — Mon, 06 Aug 2007 13:14:37 GMT

Hi Rikard

I have similar behaviour on a DL360 G5 file server. After 1 - 2 days it stops accepting connections, AD crashes and after a while it completely hangs. Poolmon brought up NTID tag as well. I just have updadet cpqteam.sys to 8.70. At the moment it doesn't seem to consume too much pool memory anymore. Let's wait and hope - crashing fileservers are always a pain ;-)

Re: Memory leak in cpqteam.sys?

Rikard Nilsson — Tue, 07 Aug 2007 02:07:52 GMT

Update 2:
NTID still behaves normally, apparently there must have been some fix in v8.70.

Kind regards,

/Rikard

Re: Memory leak in cpqteam.sys?

Robert M Harrison — Tue, 07 Aug 2007 12:01:23 GMT

Hi,
I had the same problem on 2 of 4 Windows Server 2003 Enterprise edition SP2 R2 systems.

Problem started after I installed NCU v8.60 some months ago.

I installed HP NCU v8.70 this morning on all 4 systems.

I'm using 2 NC370T MultiFunction NICs with TOE enabled in a team.

On the 2 systems which were experiencing the memory leak I can no longer launch the HP Network Configuration Utility.

HP NCU 8.70 now reports an error dialog box stating "An error occurred when making a call into the operating system" and after I click OK on the dialog box the NCU disappears from the task bar system tray until I login again.

There are no events in the event log.

Can anyone tell me how to correct this condition?

Regards,

Bob Harrison

Re: Memory leak in cpqteam.sys?

Rikard Nilsson — Wed, 08 Aug 2007 03:43:35 GMT

Is the NIC driver (HP NC-Series Multifunction Driver for Windows Server 2003) up to date as well? I am running v3.4.10.0 in which the memory leak seems to be fixed.

BTW: have you had any problems regarding TOE?

Kind regards,

/Rikard

Re: Memory leak in cpqteam.sys?

Robert M Harrison — Wed, 08 Aug 2007 14:06:03 GMT

I got HP NCU 8.70 to work today after enabling 2 retired disabled HP NC6170 NICs and then disabling these 2 NICs again to get rid of these NIC's RED Xed icons in the system tray.

I upgraded the NIC drivers yesterday for all three of my installed NIC types before upgrading NCU from 8.60 to 8.70.

If you don't upgrade the NIC drivers, the NCU upgrade checks for and complains about NIC drivers which are not up to date with minimum required versions for NCU to operate.

Please note that enabling the disabled NIC and re-disabling the NICs caused NCU managed teams to stop communicating on the LAN and this caused cluster service to hang. I had to reboot both nodes of my cluster a couple of times to get through the enable/disable process. NCU seems to working OK now.

Re: Memory leak in cpqteam.sys?

AlexF — Mon, 13 Aug 2007 12:50:55 GMT

Man...I really wish I had searched for this a bit more. I noticed the pool nonpaged bytes reaching well over 110MB for a couple ofweeks on a new Exchange cluster. After working through a few other things i finally started troubleshooting and found the issue to be with the teaming driver. I could have sworn I was at 8.7 but as I see this morning, I'm at 8.6. Damn it.

I'm updatng now and will see how things go. THanks all.
-alex

Re: Memory leak in cpqteam.sys?

h00kupz — Fri, 24 Aug 2007 09:30:13 GMT

I think I have the same problem which exhibits istelf on later versions than 8.55 and prior versions to 8.55. I'm going to install support pack 7.70 which specifically includes this version of the NCU (and hopefully a working driver) to see if I continue to experience the same issue.

Will post results.

Re: Memory leak in cpqteam.sys?

h00kupz — Fri, 24 Aug 2007 12:50:50 GMT

Support pack 7.70A fixes this issue - this problem exists in 7.60A, 7.80A, and 7.90A(Current - 8/24/2007)

Re: Memory leak in cpqteam.sys?

dospavlos — Thu, 19 Jun 2008 19:46:23 GMT

I can confirm this is still an issue on PSP8.0. Try and open teaming utility and it gives the 'error making call to operating system'. 7.7 is the only version I've found that works.