It has also been observed that while not rising to what might be determined as excessive usage, that PoolMon.exe may show increasing memory counts for Vxit Nonp 1663464 0 1663464 1091232384 656 <- 1040MBĭuring heavy I/O read-write locking and file delete operations affect I/O performance. The absurdity of YouTube’s Copyright Claim System 8.Nebula: The Zero Trust Networking Tool You Didn’t Know You Needed 4.COVID-19 Scams Spread Like Their Own Virus 0.Next Post Next Obama is just another politician after all… Links If this post helps you solve a similar issue, I’d love to hear that too. If there is an easier way that I could have diagnosed this issue, I would love to hear it. Since it took me this much effort to track down this problem, and because I’ve read lots and lots of message board posts written by people having an equally difficult time tracking down similar issues, I thought I’d share.
POOLMON.EXE INFORMATION DRIVERS
Sorting by these two columns, I quickly track down the culprit as HPBPRO.EXE which is part of the HP drivers for a Color LaserJet 3500. I open up Task Manager, click the Processes tab, and then go to View…Select Columns… and I turn on Handle Count and Thread Count. Task Manager can be used to display these resources, but it is not configured to do so by default. Now I know I’m not looking for a memory issue, I’m looking for thread or handle usage.
POOLMON.EXE INFORMATION WINDOWS
As you can see, there is obviously a problem and it is quite visible with only a short period of logging:Īccording to the poolmon.txt file that comes with poolmon,exe, the pool label Thre is “nt!ps – Thread objects”, which is the pool name for Windows thread and handle objects. I copy and paste the output into Excel, and I turn it into a line graph.
I let that run for two days, and then I wacked this bit of perl together to analyze the results: poolmon_
POOLMON.EXE INFORMATION CODE
Using ActiveState’s ActivePerl, I set up a scheduled task that ran every fifteen minutes and executed this bit of braindead code that just dumps the output of poolmon.exe to a text file that has the timestamp in the file name: I have no interest in picking up where I left off with Visual C++ ten years ago, so I made do with a little bit of perl and Excel. Poolmon needs an overhaul: the ability to track growth of values over time, log output to a file, and a GUI would be nice since this is a Windows utility. It’s pure ASCII, runs in a DOS-style command window, can’t log its results over time to a log file and I kid you not, the official way to use this utility to track down leaks is to run it and copy and paste the entire screen output to a text file every fifteen minutes so you can diff the results. Poolmon has to be the most primitive wacked-up tool anyone at Microsoft has developed, released, and then blatantly ignored. Quite a bit of Google searching and about the only tool I could find that was recommended for tracking down resource leaks that affect the nonpaged memory pool was a Microsoft Utility called poolmon.exe. Process Explorer didn’t yield any immediately useful clues. Task Manager doesn’t display any unusual memory usage. During the melt-down phase the following error is plentiful in the event logs: “The server was unable to allocate from the system nonpaged pool because the pool was empty.” Of the server traits Munin monitors, there doesn’t appear to be anything unusual. Nagios gives a couple of hours advance warning that the server is going to go south, which gives us plenty of time to reboot it. The server is monitored by Nagios, and Munin. Problem: A Windows 2003 Server that starts refusing connections after approximately 14 days of uptime, and if left alone will completely lock up and stop displaying a local console login window.
0 kommentar(er)
