Re: console log appears to wrap at the most inopportune time

Rob,

The NOTES.INI parameter LOG= sets parameters only for the LOG.NSF and has
no relation to the console.log. The fifth parameter sets the maximum size
of the body field for the log document in bytes, but does not limit the
size of the log.nsf.

The size of the console log is controlled through the
CONSOLE_LOG_MAX_KBYTES Notes.ini parameter. You can increase this value
or implement console log mirroring to address your current issue. Here is
some information on this feature (new in Domino 8):

------------------------------------------------------------------------------------------
Console log mirroring works like a file splitter for the console log file
on the server so you can specify how large each file is allowed to grow
and also keep previous data. When console log mirroring is not enabled and
a maximum size is set for the console log the oldest data is overwritten
when that limit is hit.

Related Notes.ini variables
CONSOLE_LOG_ENABLED=1: Enables the console logging feature
CONSOLE_LOG_MIRROR=1: Enables the mirroring feature
RETAIN_MIRROR_LOGS=1: Prevents deletion of previous mirrors when Domino
starts
CONSOLE_LOG_MAX_KBYTES: Sets the maximum size of the Console Log/mirror
files

There are no changes to existing behavior if Mirroring is not enabled.

Enabling Mirroring
If Mirroring is enabled, then the new Server thread is created, titled
"Console Log Mirror Task". The task begins by deleting previous mirror
files if RETAIN_MIRROR_LOGS is not specified. Then a new file is created.
This file is the name of the console log (console.log by default) with a
number appended to it, 999 maximum. The first available number is used,
meaning that the file does not exist. Holes will be filled so, if
console10.log exists then console9.log and then console11.log will be
created. As the Console Log changes the data is read from the console log
and copied to the new mirror log file.

Mirroring makes use of the circular log mechanism. The variable
CONSOLE_LOG_MAX_KBYTES needs to be set to the value to which the Console
Log can grow, and then wrap around; when the Console Log wraps, the new
mirror file is created. If mirroring is enabled, then the Maximum value
for CONSOLE_LOG_MAX_KBYTES is 1,000,000 (1 GB).

If mirroring fails for any reason then a message is printed to the Console
Log - "Console Log Mirror Task has been disabled". The server can
tolerate up to a 3 second delay by the mirror task. If the mirror fails
to catch up in 3 seconds then mirroring is automatically disabled. A
failed read or write will also disable the feature. The feature will
remain disabled until the server is restarted.

When mirroring is enabled then all keystrokes are copied to the console
log and mirrored, so backspaces may appear in the console logs.

Note that Console Log Mirroring and Console Logging must be enabled, and
CONSOLE_LOG_MAX_KBYTES must be set to some value when Domino starts, in
order for the mirroring to work. Enabling Console Logging after Domino
starts will not enable Console Log Mirroring.

Example
Notes.ini contains CONSOLE_LOG_MIRROR=1, CONSOLE_LOG_ENABLED=1,
CONSOLE_LOG_MAX_KBYTES=102400, and Domino is started. The file
console.log will be created in the IBM_TECHNICAL_SUPPORT directory under
the data directory. The file console1.log will also be created. The
console.log file will capture console output, grow to 102400 KB, and the
data will also be written to console1.log. When 102400 KB is reached,
then console1.log will be closed and console2.log will be created. The
position in console.log will be reset to the beginning and overwrite the
previous data. New data will be copied to console2.log. The cycle will
repeat until Domino terminates, or until console999.log reaches 102400 KB.
When Domino is restarted, then console1.log thru console999.log will be
deleted, since RETAIN_MIRROR_LOGS=1 was not specified in the Notes.ini
file.








Darla Black
Advisory Software Engineer
Domino on IBM i
IBM Collaboration Solutions

















From:
rob@xxxxxxxxx
To:
domino400@xxxxxxxxxxxx,
Date:
07/03/2013 02:27 PM
Subject:
console log appears to wrap at the most inopportune time
Sent by:
domino400-bounces@xxxxxxxxxxxx



I have an incident which occurs regularly around noon thirty the last
couple of Tuesdays. Trying to look at the console.logs. It looks like
they are wrapping. Funny thing is only around this incident. Strange
error (pmr open) trying to archive the boss' email.

....+....1....+....2....+....3....+....4....+....5..
************Beginning of data**************
console_NOTES02_2013_06_25@00_32_40.log

[696503:15822:00004-000000D1] 06/25/2013 14:34:13.88
...

and

....+....1....+....2....+....3....+....4....+....5..
************Beginning of data**************
console_NOTES02_2013_07_02@00_40_06.log
[702287:20890:00004-0000013E] 07/02/2013 14:06:16.98

It's only the Tuesday ones. Size on those Tuesday ones is rather
significant, 39MB vs usual 2-9MB size. Let me guess:
the server gets bounced nightly, which would cause a new console.log.
secondary server in the cluster (no one's home server),
Tuesday's archive is the only busy day,
Therefore this experience is expected since it's the only day that garners

significant log activity.
notes.ini line
Log=log.nsf, 1, 0, 7, 40000
I'm guessing the 39MB size and that 40000 in the notes.ini are somewhat
related.
Is there a way to say, don't wrap, generate a new successive console.log?


Rob Berendt