×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
If I cannot think of an open incident which may require these should I
just remove these parameters mentioned in my log.nsf and console.log?
NOTES.INI contains the following *DEBUG* parameters:
DEBUG_AMGR=*
DEBUG_CAPTURE=1
DEBUG_PANIC_ON_MARK_CORRUPT=1
DEBUG_SHOW_TIMEOUT=1
DEBUG_THREADID=1
DEBUG_TRAP_CORRUPTION=1
Warning: Debug parameters could impact operation or performance.
Contact your appropriate support vendor.
I've already decided to remove
DEBUG_PANIC_ON_MARK_CORRUPT=1
Which basically says "if I find a database marked for corruption then
cause a panic on the server and bounce it. Of course, it will notice the
corruption again when the server restarts and does it's "Begin scan of
databases to be consistency checked" and start another panic. While it
does a fantastic job of causing attention to fixing that database before
corruption passes on to the rest of cluster members it vexes the users
that the server is down, big time.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
