Wireless Access

how long controllers will maintain logs in the internal storage ?

how often historical data (such logs) are removed?

That's right!

then it is correct to say that the limit is the size of the storage?

as shown in the "show storage" command?

or there is some other limiting factor?

yes it is limited in size.  I don't know what that is though, but pretty sure it is not dependant on free space in flash.

Basically if you have lots of logging enabled, they can get flushed out fairly quickly.

If you untar a "tar logs tech-support" this will give you an idea of which logs are kept and for

how many Kbytes the buffer keeps them.  Different things, corresponding roughly

to the different "show log" subcommands are kept with different sized buffers.

Thank you bjulin!

I'm going to check "the tar logs tech-support" file  to have a better idea about how many Kbytes the buffer keeps.

Regards,

---

everton.cacau@nct.com.br wrote:

 

how long controllers will maintain logs in the internal storage ?

 

how often historical data (such logs) are removed?

---

everton.cacau,

There is a log kept for every process.  For each process where a log is generated by "tar logs tech-support", 96k of each log is kept before it is rolled over to a second and a third log for each process.  If you download the logs.tar, under var>Log>oslog, you will see a list of those logs.  Each time a log rolls, you will see a  log.1 or a log.2 annotation to see that it has rolled and each segment will be no more than 96k.  There will only be a maximum of 3 of these segments (e.g. user.log, user.log.1, user.log.2).  Below is a picture of part of the Var>Log>oslog directory from a busy controller.

I hope that answers your question;