Hi
On my hostmon server I see many eventlog errors (about every second) like this:
"Thread creation error: Not enough storage is available to process this command"
Using HostMon 6.82, Windows 2003 Standard Edition.
Where to start troubleshooting?
Gabrie
Errors: Not enough storage is available to process
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Could you provide more information, please?
- Do you use ODBC logging or ODBC Query test method? If yes, what ODBC driver do you use?
- Do you have installed antivirus monitor? Personal firewall? Content monitoring software? Non-standard winsock components? Network packet analyzer?
- Do you have SP1 or SP2 installed on your Windows 2003 system?
Looks like resource allocation error. What is the total resource usage on your system (Memory, Handles, etc)? How many Handles, GDI and USER objects are used by hostmon.exe process? What exact process does use the most of resources? You may use standard Windows Task Manager to check Handles, GDI and USER objects.
To workaround this problem I would suggest you slightly modify registry in a following way: you should change
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows registry key.
There are present SharedSection parameter. By default, it is set as SharedSection=1024,3072,512. We recommend you to increase second and third values. You should set SharedSection=1024,6144,1024
Please read following articles to understand the meaning of changes:
http://support.microsoft.com/default.as ... -us;126962
Please note: foregoing articles contain information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.
Regards,
Max
- Do you use ODBC logging or ODBC Query test method? If yes, what ODBC driver do you use?
- Do you have installed antivirus monitor? Personal firewall? Content monitoring software? Non-standard winsock components? Network packet analyzer?
- Do you have SP1 or SP2 installed on your Windows 2003 system?
Looks like resource allocation error. What is the total resource usage on your system (Memory, Handles, etc)? How many Handles, GDI and USER objects are used by hostmon.exe process? What exact process does use the most of resources? You may use standard Windows Task Manager to check Handles, GDI and USER objects.
To workaround this problem I would suggest you slightly modify registry in a following way: you should change
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows registry key.
There are present SharedSection parameter. By default, it is set as SharedSection=1024,3072,512. We recommend you to increase second and third values. You should set SharedSection=1024,6144,1024
Please read following articles to understand the meaning of changes:
http://support.microsoft.com/default.as ... -us;126962
Please note: foregoing articles contain information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.
Regards,
Max
Not sure what I'm using.... OPTIONS -> PRIMARY LOG is log to FILE.KS-Soft Europe wrote:Could you provide more information, please?
- Do you use ODBC logging or ODBC Query test method? If yes, what ODBC driver do you use?
McAfee Virusscan enterprise 8.0.0- Do you have installed antivirus monitor? Personal firewall? Content monitoring software? Non-standard winsock components? Network packet analyzer?
No other monitoring software.
- Do you have SP1 or SP2 installed on your Windows 2003 system?
Not SP1 and not SP2.
Have applied this now. No change yet.Looks like resource allocation error. What is the total resource usage on your system (Memory, Handles, etc)? How many Handles, GDI and USER objects are used by hostmon.exe process? What exact process does use the most of resources? You may use standard Windows Task Manager to check Handles, GDI and USER objects.
To workaround this problem I would suggest you slightly modify registry in a following way: you should change
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows registry key.
There are present SharedSection parameter. By default, it is set as SharedSection=1024,3072,512. We recommend you to increase second and third values. You should set SharedSection=1024,6144,1024
Please read following articles to understand the meaning of changes:
http://support.microsoft.com/default.as ... -us;126962
Please note: foregoing articles contain information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.
Regards,
Max
We have 1994 tests running. Strange this is that when I right click one of those test that report "The wait operation timed out" and selected that this test should be re run, I get the correct reply.
We do the follwing tests:
- Available MBytes
- CPU usage
- Disk space C:\ and D:\
- Disk Queue length C:\ and D:\
Strange thing is that these time outs only occur on "Available MBytes" and "Disk Queue length", never on other counters.
Gabrie
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
In fact, we recommend to use HostMonitor on clean system, without antiviruses. Most of antiviruses, like Symantec, McAfee, TrendMicro often leads to problems, especially related to SMTP protocol, it even can crash HostMonitor. At the same time antivirus scanners work fine (scanner - module that checks files and processes from time to time, scanners does not modify system DLLs and registry, does not intercept TCP traffic and so on). If you are unable to disable antivirus, we recommend at least to disable real-time protection module or add HostMonitor to exclusions list.Gabrie wrote:McAfee Virusscan enterprise 8.0.0
We strongly recommend to install SP1 or/and SP2 on your system. A lot of network related problems were fixed in these service packs.Gabrie wrote:Not SP1 and not SP2.
As I understand, you are using "Performance Counter" test method to retrieve foregoing counters, right? In fact, Microsoft's implementation of Performance counters is not much reliable, so we recommend to use "WMI" test method instead: http://www.ks-soft.net/hostmon.eng/mfra ... ts.htm#wmiGabrie wrote:- Available MBytes
- Disk Queue length C:\ and D:\
You just should setup "WMI" test method with following query to retrieve AvailableMByte counter:
Code: Select all
select AvailableMBytes from Win32_PerfFormattedData_PerfOS_Memory
Code: Select all
select CurrentDiskQueueLength from Win32_PerfFormattedData_PerfDisk_LogicalDisk WHERE Name = 'C:'
Max
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Did it help? Have you still experienced "The wait operation timed out" error?Gabrie wrote:I just upgraded to SP2.
Also, there are additional options available for the "Performance Counter" test method on "Options" -> "Miscellaneous" tab -> "Performance Counter tests" area. Could you try to select another "Test Mode", for instance "External mode" or "OneByOne"? Please, read the following article for details: http://www.ks-soft.net/hostmon.eng/mfra ... m#MiscPerf
Hm. I think, you may export all "Performance counter" tests into text file using "File" -> "Export to text file" menu item and use any text editor with "Find/Replace" function to change test method and appropriate data within this file. After that, you may import modified text file using menu "File" -> "Import from text file".Gabrie wrote:Is there an easy way I can change the performance counters to WMI counters? Or do I have to edit all tests one by one?
Regards,
Max