I've never seen the services.exe process itself consume memory on that scale. Is that WS Private?
On Mon, Jan 31, 2011 at 8:53 AM, Al Rose <arose...@gmail.com> wrote: > Process Explorer shows that services.exe utilizes around 2GB of RAM however > the dependend processes are the same as the ones on the passive node that > doesnt have a memory leak. > I cannot see any process using unusual amount of RAM. > > boot.ini is as follows: > [boot loader] > timeout=30 > default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS > [operating systems] > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, > Enterprise" /noexecute=optout /fastdetect /BASEVIDEO /3GB /USERVA=3030 > > On Mon, Jan 31, 2011 at 2:41 PM, Richard Stovall <rich...@gmail.com>wrote: > >> Process Explorer didn't show you which service(s) was(were) consuming all >> that memory? You should be able to add columns for Working Set, WS Private, >> and WS Shareable. >> >> Out of curiosity, what are the contents of your boot.ini file on that >> server? >> >> >> On Mon, Jan 31, 2011 at 5:18 AM, Al Rose <arose...@gmail.com> wrote: >> >>> Hi all, >>> >>> I am working on a cluster that shows some memory leaks. >>> >>> Servers participating in the cluster have both 4GB of Ram and are running >>> windows server 2003 R2. >>> I started noticing that the services.exe process was using 2GB of RAM on >>> the active node, i tried to find out what was happening using procxp from >>> live sysinternals but could not find anything relevant. After some googling >>> i found out that some people were experiencing the same issue and referred >>> to logs size. There was a standard policy on our domain for server that >>> allowed log files to grow to 120MB, i changed that policy for the cluster to >>> 40Mb and cleaned out the log but still the services.exe is eating up almost >>> 2GB. The server was the active node in the cluster so we did a failover to >>> see if it would change the memory consumption but now that the node is >>> passive services.exe is still using the same amount of memory. >>> >>> Nothing differs from the 2 nodes. >>> I did a netdiag on the node in question and received a browsing error: >>> DC list test . . . . . . . . . . . : Failed >>> Failed to enumerate DCs by using the browser. >>> [ERROR_NO_BROWSER_SERVERS_FOUND] >>> >>> I can say that netbios is not enabled on the cluster and no wins servers >>> are configured. >>> >>> I stumbled upon this article from Microsoft stating that netbios is still >>> needed for exchange 2003 to function properly especially for Clusters >>> http://support.microsoft.com/kb/837391/en-us >>> >>> Any ideas, does it looks to you that it cpould be a netbios related >>> issue? >>> >>> --- >>> To manage subscriptions click here: >>> http://lyris.sunbelt-software.com/read/my_forums/ >>> or send an email to listmana...@lyris.sunbeltsoftware.com >>> with the body: unsubscribe exchangelist >>> >> >> --- >> To manage subscriptions click here: >> http://lyris.sunbelt-software.com/read/my_forums/ >> or send an email to listmana...@lyris.sunbeltsoftware.com >> with the body: unsubscribe exchangelist >> > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
