During initialization, the log server minimally initializes the memory-buffer, nvram, and console log targets to their default configurations. * (pacman debug) Slot-2 Stack.3 # show log configuration target Log Target : memory-buffer Enabled : yes Filter Name : DefaultFilter Match regex : Any Severity : Debug-Data (through Critical) Format : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition> Slot: Buffer size : 1000 messages Log Target : nvram Enabled : yes Filter Name : DefaultFilter Match regex : Any Severity : Warning (through Critical) Format : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition> Slot: Log Target : console Enabled : yes Filter Name : DefaultFilter Match regex : Any Severity : Info (through Critical) Format : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition> Slot: The log server causes this event if there is not sufficient memory to allocate for these targets, or if some other internal inconsistency occurs which prevents the log server from successfully completing setting their default configuration. The log server will continue to operate despite this condition, although its functionality will be very limited. In particular, there may be no log targets at all, and it may not even be possible for this event message to be logged.
There is no specific work-around if this condition does occur - it is most likely the result of some internal inconsistency or the overallocation of memory either by the log server or some other process. The output from the "show log configuration target" and the "show memory" commands should be obtained to help in trouble-shooting this problem.
Error
The log server was unable to initialize the default target configuration
Print
this page
Email this topic
Feedback
View PDF
Download EPUB