The Sysinternals tools are awesome! This is the first time I've worked with Windows servers and just a few days ago went looking for Windows equivalents to familiar unix tools. Process Explorer, Process Monitor, TCPView, and Autoruns are a few of them that I've explored so far. Process Monitor (similar to truss) just helped me yesterday in figuring out that I hadn't updated my PATH the way I should have. The email engine service wasn't starting, and there wasn't any indication why. None of the logs that were supposed to have been created were there. Following the process as it started up using process monitor showed the file that was missing. It was probably overkill to find a pathing issue, but BMC wasn't able to figure it out either.
These tools have quickly found a place in my quiver. Thad On Thu, Oct 25, 2012 at 9:54 AM, Cecil, Ken <kce...@hubbell.com> wrote: > Thanks, I'll load process explorer on there and watch it. > > > Ken. > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Longwing, LJ CTR MDA/IC > Sent: Thursday, October 25, 2012 8:57 AM > To: arslist@ARSLIST.ORG > Subject: Re: ARERR 300 Malloc failed on server > > Ken, > I would agree that 1.2 on a 64Bit OS is a bit hard to explain the malloc > error. How did the overall system resources look at the time? > > I have found at times that the memory size is a bit hard to determine. I > use a SysInternals tool 'Process Explorer' to look at things. One thing > that I have found is that the memory on my server (32 Bit) tends to crap > out when the 'Virtual Size' hits 2 GB, not necessarily when the 'Private > Bytes' hits 2 GB...and I have sometimes seen a great disparity between the > two values. I additionally try to look at the 'Max Memory Usage' column > (that you can add) to see if at any point it actually spiked higher. > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken > Sent: Wednesday, October 24, 2012 3:04 PM > To: arslist@ARSLIST.ORG > Subject: Re: ARERR 300 Malloc failed on server > > Simon, The servers are Windows Server 2003 Enterprise 64 bit with 10 GB > RAM. > > David, New changes transported to production over since the beginning of > September. > > LJ, That is what I thought. When everything hit the fan yesterday the > arserver.exe process was only using ~1.2 GB of RAM. It is a 64 bit OS so I > think that seems pretty low to cause an out of memory issue? > > Lisa, We get the error in both the Mid Tier and WUT. > > Thanks guys, > > Ken. > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Simon Ellis > Sent: Wednesday, October 24, 2012 4:52 PM > To: arslist@ARSLIST.ORG > Subject: Re: ARERR 300 Malloc failed on server > > What O/S are you running on? > > > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of David M. Clark > Sent: Thursday, 25 October 2012 9:43 a.m. > To: arslist@ARSLIST.ORG > Subject: Re: ARERR 300 Malloc failed on server > > "We are getting this error intermittently over the past couple of weeks" > > Have you recently customized anything in that area? I've seen this happen > when access rights to a newly-created field are not properly defined. > > -D > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Longwing, LJ CTR MDA/IC > Sent: Wednesday, October 24, 2012 3:31 PM > To: arslist@ARSLIST.ORG > Subject: Re: ARERR 300 Malloc failed on server > > Ken, > It sounds like your arserver was bouncing up against a upper memory limit. > This can happen sometimes with memory leaks that don't properly release > memory once used. A restart of the service brings the system back down to > initial minimums of startup. You may want to make sure that you are on the > most recent patch of 7.5 to ensure that any known issues are taken care of > properly. > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken > Sent: Wednesday, October 24, 2012 1:42 PM > To: arslist@ARSLIST.ORG > Subject: ARERR 300 Malloc failed on server > > ** > > We are getting this error intermittently over the past couple of weeks. > The most consistent time it is occurring is when trying to attach a largish > attachment (around 4MB). Some have also received it when trying to open an > attachment. Yesterday for awhile we were getting the error anytime the > SDA's were trying to attach any attachment to an Incident. I ended up > restarting the ar server service. > > > > Has anybody run across something similar? (Arerr 300 when working with > attachments) > > > > I have a support request in with BMC and waiting for a reply. The KB > articles I found did not seem to apply. > > > > > > Thanks > > > > > > Ken Cecil > > 574-283-4248 > > kce...@hubbell.com > > > > > > AR 7.5 > > ITSM 7.6 > > Windows 2003 Enterprise 64bit > > SQL 2008 > > > > > ________________________________ > > This email and any files transmitted with it are confidential and intended > solely for the addressee. If you have received this email in error please > notify the system manager. Subject to local law, communications (including > traffic data) with Hubbell may be monitored by our systems [or a third > party's systems on our behalf] for the purposes of security and the > assessment of internal compliance with Hubbell policies. This footnote also > confirms that this email message has been swept for the presence of > computer viruses. > www.hubbell.com <http://www.hubbell.com/> - Hubbell Incorporated > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 > www.wwrug12.com ARSList: "Where the Answers Are" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 > www.wwrug12.com ARSList: "Where the Answers Are" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 > www.wwrug12.com ARSList: "Where the Answers Are" > > > > ****************************************************************************** > This email and any files transmitted with it are confidential and intended > solely for the addressee. If you have received this email in error please > notify the system manager. Subject to local law, communications (including > traffic data) with Hubbell may be monitored by our systems [or a third > party's systems on our behalf] for the purposes of security and the > assessment of internal compliance with Hubbell policies. This footnote also > confirms that this email message has been swept for the presence of > computer viruses. > www.Hubbell.com <http://www.hubbell.com/> - Hubbell Incorporated > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 > www.wwrug12.com ARSList: "Where the Answers Are" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 > www.wwrug12.com ARSList: "Where the Answers Are" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
