Hi @FreeSamples 

Please refer to this post Controller v5 May Frequently Generate Alerts Of “The number of logs is up to the limit”.

FreeSamples wrote

Hey  @Hank21!

 

Thank you for the post. I get that the message occures when logs are full. I have 90GB of free space on disk for the logs and non of my mounts are near full. If you add all my of logs up that is like 10k logs. Looking at any log file in /var/log that equates to well under meg of storage. I understand what the error means, but either TP link stores these logs as large uncompressed images or may only allocated a small fraction of space? If the Omada controller can handle 100 different devices (and I have only 3) if the device can only store 10k logs, that seems like a major problem, right?

 

If there a way to allocate more storage for logs or something? The error does not make sense given the scenario.

 

 

Hi @FreeSamples 

For Omada Software Controller, the maximum number of logs depends on the number of managed Omada devices.

If the number of managed Omada devices (let's say x) does not exceed 100, the maximum number of logs is 150 * 31 * x. If the number exceeds 100, the maximum number of logs is 150 * 31 * 100 + 30 * 31 * (x-100).

When the number of logs in your controller exceeds the upper limit, you will receive an alert of “The number of logs is up to the limit”.

But if you get such alerts frequently, there are probably a lot of client roaming events, which generate many logs. You can go to Log – Notifications, to adjust the notification settings. For example, you can uncheck “Log full” notification in System, or “Client Roaming (Wireless)” notification in Client, or other frequent log types.