Logging on persistent file current.log issue of a Stackable B5 Switch

  • 0
  • 1
  • Problem
  • Updated 3 years ago
  • Solved
Hi all,

on switch B5G124-24 fw. 06.81.06.0002 I report the following issue:

I have to save on current.log file all syslog messages by applying the following configuration:
set logging local console enable file enable
set logging default facility local4 severity 8

set logging application all level 8

The problem reported is that any log messages are not saved on current.log file but by "show logging buffer" I can clearly see all log messages that I expected also on current.log file.

Can anybody clarify such behaviour and explain how I could save all log messages on current.log file?

Thank you in advance to all for helping me
Claudio
Photo of Claudio Minnetti

Claudio Minnetti

  • 164 Points 100 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Paul Poyant

Paul Poyant, Employee

  • 3,536 Points 3k badge 2x thumb
The commands you've listed here are outlined in Hub KB 10869:
https://community.extremenetworks.com/extreme/topics/capturing_securestack_error_messages_in_the_log...

They are intended to affect what is written to the logging buffer (from master unit only, saved until system reset) and the syslog server.
This logged data has some overlap with what is written to the current.log (aggregated from all stack units, saved to non-volatile memory), but it is in general not a record of the same events.

I don't know of any detailed explanation of the differences, however I believe that the rationale is that keeping long-term track of the additional debug messaging has the potential to quickly fill the current.log's available 256,000-byte storage and place it into auto-wrap/overwrite mode - for little resulting diagnostic value.