wir erhalten ständig folgende Fehlermeldung im Log:
Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
Domino 7.0.4 FP1 im Cluster
diese Lösung wurde schon ausprobiert:
http://www-01.ibm.com/support/docview.wss?uid=swg21099641
hat leider nicht geholfen
Hat vielleicht jemand ne Idee?
Hast du denn schon rausgefunden, was dir das Log zu zumüllt? Hast du die Event Pool Size hochgedreht?
wurde auf 5 MB hochgesetzt, aber außer der fehlermeldung ist fast nix im log zu sehen
Und was ist im Log zu sehen direkt bevor die Fehlermeldung das erste mal auftritt ?
Gibt es da eventuell eine Häufung von Agentenausgaben oder ähnlichem ?
Zitat
comet schrieb:
wurde auf 5 MB hochgesetzt, aber außer der fehlermeldung ist fast nix im log zu sehen
Wie "auf 5 MB hochgesetzt"? Das Minimum sind 5 MB, default sind 10. Wie kann man etwas auf das absolute Minimum hochdrehen?
11.11.2009 12:58:34 Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery)
11.11.2009 12:58:37 Event Monitor started
11.11.2009 12:58:37 Warning: All Domino Domain Monitoring probes are disabled resulting in the loss of valuable diagnostic information. Please configure DDM probes in events4.nsf. Access DDM reports in ddm.nsf.
11.11.2009 12:58:38 Searching Server document for security lists
11.11.2009 12:58:39 Searching Server Configuration document(s) for parameters...
11.11.2009 12:58:39 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
11.11.2009 12:58:40 Event: Could not locate view 'svrcollhier'.
11.11.2009 12:58:41 Lotus Domino (r) Server started, running Release 7.0.4FP1
11.11.2009 12:58:41 Server started on physical node ....
11.11.2009 12:58:45 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
11.11.2009 12:58:48 The Console file is d:\Lotus\Domino\data\IBM_TECHNICAL_SUPPORT\console.log
11.11.2009 12:58:48 Console Logging is ENABLED
11.11.2009 12:58:48 Adding server to cluster BB_PIM_CL01
11.11.2009 12:58:49 Database Replicator started
11.11.2009 12:58:49 Replicator is set to Ignore Database Quotas
11.11.2009 12:58:49 Searching Server document for security lists
11.11.2009 12:58:49 Database Replicator started
11.11.2009 12:58:49 Replicator is set to Ignore Database Quotas
11.11.2009 12:58:49 Index update process started
11.11.2009 12:58:49 Index update process started
11.11.2009 12:58:49 Calendar Connector started
11.11.2009 12:58:49 Schedule Manager started
11.11.2009 12:58:49 Rooms and Resources Manager started
11.11.2009 12:58:49 Admin Process: ... is the Administration Server of the Domino Directory.
11.11.2009 12:58:49 Database Server started
11.11.2009 12:58:49 Administration Process started
11.11.2009 12:58:49 Unable to redirect failover from
11.11.2009 12:58:50 Router: notes.ini setting for Log_Mailrouting being used (note - this option may now be configured in a Server Configuration document)
11.11.2009 12:58:50 Agent Manager started
11.11.2009 12:58:50 Mail Router started for domain GA
11.11.2009 12:58:50 Router: Internet SMTP host ... in domain notes....
11.11.2009 12:58:50 RnRMgr: Informational: Schedule Manager is responsible for the busytime database on this server.
11.11.2009 12:58:50 AMgr: Executive '1' started. Process id '3264'
11.11.2009 12:58:50 SchedMgr: Informational: Schedule Manager is responsible for the busytime database on this server.
11.11.2009 12:58:50 Unable to redirect failover from ....
11.11.2009 12:58:50 SchedMgr: Validating schedule database
11.11.2009 12:58:50 RnRMgr: Validating schedule database
11.11.2009 12:58:54 RnRMgr: Done validating schedule database
11.11.2009 12:58:54 Router: notes.ini setting for Log_Mailrouting being used (note - this option may now be configured in a Server Configuration document)
11.11.2009 12:58:54 Unable to redirect failover from ....
11.11.2009 12:58:55 SchedMgr: Done validating schedule database
11.11.2009 12:58:55 Unable to redirect failover from ....
11.11.2009 12:58:55 Unable to redirect failover from ....
11.11.2009 12:58:55 Unable to redirect failover from ....
11.11.2009 12:58:56 Unable to redirect failover from ....
11.11.2009 12:58:56 Unable to redirect failover from ....
11.11.2009 12:58:56 Unable to redirect failover from ....
11.11.2009 12:58:59 Router: notes.ini setting for Log_Mailrouting being used (note - this option may now be configured in a Server Configuration document)
11.11.2009 12:59:22 Unable to redirect failover from ....
11.11.2009 12:59:22 Unable to redirect failover from ....
11.11.2009 12:59:28 Cluster Database Directory started
11.11.2009 12:59:30 Finished initialization of Cluster Database Directory
11.11.2009 12:59:30 Replicating Cluster Database Directory with ....
11.11.2009 12:59:38 Cluster Replicator started
11.11.2009 12:59:39 Cluster Replicator is set to Ignore Database Quotas
11.11.2009 12:59:45 Event: Probe configurations changes will not be recognized because the '($DDMConfig)' view cannot be found: Entry not found in index
11.11.2009 12:59:45 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
11.11.2009 12:59:49 This server is currently a member of a cluster
11.11.2009 12:59:54 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 12:59:54 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 12:59:54 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 12:59:54 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 12:59:55 Unable to redirect failover from ....
11.11.2009 13:00:45 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:00:59 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
console log nach hochsetzen auf 10mb:
Lotus Domino (r) Server, Release 7.0.4FP1, July 20, 2009
Copyright (c) IBM Corporation 1987, 2009. All Rights Reserved.
Restart Analysis (0 MB): 100%
11.11.2009 13:09:04 Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery)
11.11.2009 13:09:06 Event Monitor started
11.11.2009 13:09:06 Warning: All Domino Domain Monitoring probes are disabled resulting in the loss of valuable diagnostic information. Please configure DDM probes in events4.nsf. Access DDM reports in ddm.nsf.
11.11.2009 13:09:07 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
11.11.2009 13:09:07 Event: Could not locate view 'svrcollhier'.
11.11.2009 13:09:07 Searching Server document for security lists
11.11.2009 13:09:08 Searching Server Configuration document(s) for parameters...
11.11.2009 13:09:08 Server started on physical node ...
11.11.2009 13:09:12 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
11.11.2009 13:09:14 The Console file is d:\Lotus\Domino\data\IBM_TECHNICAL_SUPPORT\console.log
11.11.2009 13:09:14 Console Logging is ENABLED
11.11.2009 13:09:14 Adding server to cluster BB_PIM_CL01
11.11.2009 13:09:14 Database Replicator started
11.11.2009 13:09:14 Replicator is set to Ignore Database Quotas
11.11.2009 13:09:14 Rooms and Resources Manager started
11.11.2009 13:09:14 Admin Process: ... is the Administration Server of the Domino Directory.
11.11.2009 13:09:14 Database Replicator started
11.11.2009 13:09:14 Replicator is set to Ignore Database Quotas
11.11.2009 13:09:14 Index update process started
11.11.2009 13:09:14 Schedule Manager started
11.11.2009 13:09:14 Administration Process started
11.11.2009 13:09:14 Calendar Connector started
11.11.2009 13:09:14 Index update process started
> 11.11.2009 13:09:15 Agent Manager started
11.11.2009 13:09:15 RnRMgr: Informational: Schedule Manager is responsible for the busytime database on this server.
11.11.2009 13:09:15 AMgr: Executive '1' started. Process id '3856'
11.11.2009 13:09:15 SchedMgr: Informational: Schedule Manager is responsible for the busytime database on this server.
11.11.2009 13:09:15 Database Server started
> 11.11.2009 13:09:15 Searching Server document for security lists
> 11.11.2009 13:09:15 SchedMgr: Validating schedule database
11.11.2009 13:09:15 Router: notes.ini setting for Log_Mailrouting being used (note - this option may now be configured in a Server Configuration document)
> 11.11.2009 13:09:16 Mail Router started for domain GA
11.11.2009 13:09:16 Router: Internet SMTP host ... in domain notes...
> 11.11.2009 13:09:19 RnRMgr: Validating schedule database
> 11.11.2009 13:09:19 Router: notes.ini setting for Log_Mailrouting being used (note - this option may now be configured in a Server Configuration document)
> 11.11.2009 13:09:20 SchedMgr: Done validating schedule database
> 11.11.2009 13:09:20 RnRMgr: Done validating schedule database
> 11.11.2009 13:09:24 Cluster Database Directory started
> 11.11.2009 13:09:25 Router: notes.ini setting for Log_Mailrouting being used (note - this option may now be configured in a Server Configuration document)
> 11.11.2009 13:09:25 Finished initialization of Cluster Database Directory
> 11.11.2009 13:09:25 Replicating Cluster Database Directory with ...
> 11.11.2009 13:09:34 Cluster Replicator started
> 11.11.2009 13:09:35 Cluster Replicator is set to Ignore Database Quotas
> 11.11.2009 13:09:45 This server is currently a member of a cluster
> 11.11.2009 13:10:12 Event: Probe configurations changes will not be recognized because the '($DDMConfig)' view cannot be found: Entry not found in index
11.11.2009 13:10:12 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
>
11.11.2009 13:10:17 4107 Transactions/Minute, 654 Notes Users
> 11.11.2009 13:11:12 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
>
11.11.2009 13:11:18 2762 Transactions/Minute, 566 Notes Users
> 11.11.2009 13:11:25 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
> 11.11.2009 13:12:12 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
>
11.11.2009 13:12:19 2696 Transactions/Minute, 546 Notes Users
> 11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
Vielleicht solltest du erst mal die angezeigten fehler, wie z.B. die des Events Tasks beheben
die gabs auch schon, als die fehlermeldungen nicht existierten
Ja und ?
Trotzdem können diese ja mit daran Schuld sein
Sag mal, bist du sicher, dass du auch wirklich das vollständige Log gepostet hast? Mir kommen die Zeiträume zwischen den von dir geposteten Outputs doch ein wenig komisch vor:
> 11.11.2009 13:10:12 Event: Probe configurations changes will not be recognized because the '($DDMConfig)' view cannot be found: Entry not found in index
11.11.2009 13:10:12 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
Dann, ganze 5 Sekunden später erst:
> 11.11.2009 13:10:17 4107 Transactions/Minute, 654 Notes Users
Dann vergeht eine knappe Minute:
> 11.11.2009 13:11:12 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
Jetzt vergehen wieder 6 Sekunden:
> 11.11.2009 13:11:18 2762 Transactions/Minute, 566 Notes Users
Jetzt sind es 7 Sekunden:
> 11.11.2009 13:11:25 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
47 Sekunden:
> 11.11.200913:12:12 Event: Error loading domain monitoring configuration view '($DDMFilters)': Entry not found in index
wieder 7 Sekunden:
> 11.11.2009 13:12:19 2696 Transactions/Minute, 546 Notes Users
11 Sekunden und erst jetzt loggt er mehrere Entries in der selben Sekunde
> 11.11.2009 13:12:30 Maximum number of in-memory log entries exceeded; cannot create another until some are flushed to the log database
Dass der Server -gemäß deiner Angaben- eigentlich gar nichts tut und urplötzlich Fehler spuckt, kann ich kaum glauben.
Hast du mit OS-Bordmittel denn schon geprüft, wie die CPU-Last aussieht und vor allem die Schreib-/Lesequeues und -durchsätze der Platten?
habe nix weggelassen und nix dazugeschrieben
wir werden jetzt nen call bei IBM aufmachen
Sag mal, bist du sicher, dass du auch wirklich das vollständige Log gepostet hast? Mir kommen die Zeiträume zwischen den von dir geposteten Outputs doch ein wenig komisch vor:
Das liegt an Log_Sessions=0, sonst sieht man nämlich nix mehr.
Inzwischen ist das Problem aber gelöst. Nachdem der Wert auf 1 gesetzt wurde und der Parameter LOG_DISABLE_SESSION_INFO=1 hinzugefügt wurde. Seitdem sind die Transaction Logs auch wieder auf Normalniveau.
