nhttp 100% CPU. Wer kann helfen.

[Ta Lun]

Hallo,
ich benötige hilfe weil wir nicht wissen woher folgendes Problem kommen könnte.
Wir setzen die "neueste" Version der 5er Reihe auf Basis Windows 2000 ein und betreiben u.a. 4 Server die über Webaccess Mailzugriff gewähren.
Die Systeme laufen seit einigen Jahren und wir haben auch keine Änderungen in den letzten Wochen getätigt.

Gestern und Vorgestern sind unsere Systeme aber extrem in die Knie gegangen und der nhttp task hatte eine 100% Auslastung egal wieviele CPU´s in der Maschine stecken.

Die einzige Veränderung die wir feststellen konnten -wobei dies mehr vermutungen sind- scheinen die Benutzer zu sein. Es sind mehr als vorher und viele davon sind in den letzten Wochen auf DSL umgestiegen.
Dadurch scheint die gleichzeitige aktivität also die "current HTTP user sessions" gestiegen zu sein. Vorher lagen wir so bei 50 - 120 nun kommt es aber vor das wir loker auf 300 gehen. Das Problem daran ist aber das der Task sich nicht mehr resetet, wenn es weniger user sind.
eute nach hatten wir 100% obwohl nur 7 Sessions on waren.

Wer kennt das Problem.
Wer hat ein Tip was man noch prüfen könnte.

wir sind am Überlegen ein Upgrade der Hardware durzuführen (Teilweise bis 6 Jahre alt) und auf Windows 2003  upzugraden. Würde dies das Problem beheben?

Danke.

Ta Lun

[Lossa]

Hallo,

das sagt die Knowledgebase:
 Domino Server NRouter or HTTP Tasks Can Take 80-100% of CPU Under Windows 2000
A customer has a Domino R5.x or Domino 6 server installed on a Windows 2000 server.

Intermittently, one of the following issues occurs:

1. When a large number of messages are sent, NROUTER.EXE spikes and consumes 80 to 100% of the CPU. The messages are initially delivered normally by the router, however the performance of the Domino server begins to decrease rapidly. Issuing a "tell router q" command from the server console and then reloading Router only temporarily resolves the issue.

      In some cases, mail continues to route, even as the Task Manager shows the Router consuming close to 100% of the CPU, but replication and other tasks do not take place at the same time. If the customer quits the Router, replication will then take place.


2. The HTTP process spikes and consumes 80 to 100% of the CPU for a significant amount of time. This issue was observed on a Dual Pentium-III 1.3 ghz PC and Dual Pentium-III Xeon 500Mhz PC. The issue was reproduced by using a Linux script to access a Domino database and performing basic authentication against an LDAP Server via Directory Assistance.

 Solution

This issue has been reported to Lotus Software Quality Engineering and was found to be a problem with Windows 2000. To address this issue, contact Microsoft Product Support Services to obtain the Latest Service Pack (SP3) for Windows 2000 Server.

Reference article #Q282865 at www.microsoft.com for full details.

To work around this issue, move Domino to a Windows NT 4 server (or obtain the aforementioned Service Pack 3 from Microsoft if you remain on Windows 2000).

      Note: This topic is covered in the Release Notes for Domino 6 under Requirements for server monitoring (i.e. the Collect task and Administrator client). In Domino 6, the Collect task outputs a message specifically designed to avoid this problem. In Domino 6, the Collect task is designed to write to the console the following message:

                  "To avoid severe performance degradation, you must update Windows 2000 with 'Service Pack 3'."

      This message appears whenever Collect is started on the Windows 2000 platform and Service Pack 3 is not installed.

Supporting Information:

If a program makes MANY network connections in a very short duration, the Windows kernel code will go into a tight loop eating all of the available CPU. This type of network behavior often happens when the Domino monitoring feature is configured to gather information from multiple servers in a relatively short amount of time. Hence, it is likely that servers will experience the issue using the server monitoring features of the Domino Administrator client or the Collect task on a Domino server. The time interval and number of servers is dependent on the network environment and the systems being monitored.

Microsoft has acknowledged and addressed a network issue in Windows 2000 that can degrade the performance of both the mail router and the statistic collector in Notes/Domino 6, affecting the server, the Domino Administrator, and Tivoli Analyzer. While it should be noted that Service Pack 3 is not a requirement for the Domino server, the Domino 6 Release Notes require Service Pack 3 for all Domino Administrator client machines and server machines running the Collect task. In general, Service Pack 3 is strongly recommended for all Domino servers because of the possibility that server outages may occur for other tasks as stated above.

For a complete list of Microsoft Product Support Services phone numbers, please go to the following address:

            http://support.microsoft.com/directory/overview.asp

Related Documents:

R5 Admin Server Monitor Task Pegs the CPU on Windows 2000 Systems
Document #: 182047

What is the NOTES.INI Parameter Platform_Statistics_Enabled?
Document #: 177652