"The number of logs is up to the limit" alert messages
"The number of logs is up to the limit" alert messages
I got tons of these alert messages when upgrading the Omada controller from 4.4.6 to 5.0.29. I acknowledge them all, and now I got another one, but I don't understand what do they mean. Any idea?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @pcsurgeon, @Unraider,
Here is a article you can refer to learn more details:
What to do if you get an alert of “The number of logs is up to the limit”?
And you can try the troubleshooting step as below:
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.
Best Regards!
- Copy Link
- Report Inappropriate Content
Unraider wrote
I got tons of these alert messages when upgrading the Omada controller from 4.4.6 to 5.0.29. I acknowledge them all, and now I got another one, but I don't understand what do they mean. Any idea?
The Omada Controller v5 has changed the upper limit of the Alert log entries.
When you are notified with such alert log, that means the alert log entries has reached the upper limit and the exceeded alert log entries will be cleared automatically.
May I know how many Omada devices do you have?
How do you set about the log notification?
Best Regards!
- Copy Link
- Report Inappropriate Content
The literal meaning? Sounds like it's up to the limit and you gotta clear them up to get storage for other alerts?
- Copy Link
- Report Inappropriate Content
Good day
I'm having the same issue of getting the " The number of logs is up to the limit. " message after upgrading to the 5.0.29 firmware.
what is the usual cause of these logs?
- Copy Link
- Report Inappropriate Content
@Hank21 I have 4 devices in total (see signature for details), and I haven't changed the log notifications from the default.
So, from what I understand, I should not worry about this alert, it just means that the notifications reached a limit. It probably shouldn't be at the Warning level, then, just at the Info level.
- Copy Link
- Report Inappropriate Content
@Unraider I got the same error even after deleting all logs... my concern is that system has gone down today without any log. Could it have something to do?
- Copy Link
- Report Inappropriate Content
@Unraider There gotta be a way to delete the log... Getting these messages non-stop
- Copy Link
- Report Inappropriate Content
@pcsurgeon There is a paintbrush-like icon on the top-right to delete all logs. I don't think that's the issue, I think the issue is that they changed something between 4.4.x and 5.0.x and they don't explain what this new "alert" message means or how to configure Omada.
- Copy Link
- Report Inappropriate Content
Dear @pcsurgeon, @Unraider,
Here is a article you can refer to learn more details:
What to do if you get an alert of “The number of logs is up to the limit”?
And you can try the troubleshooting step as below:
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.
Best Regards!
- Copy Link
- Report Inappropriate Content
Hi,
I'm getting same messages everyday. Already tried to lower the log/events entries... and also deleted all logs/archived/events... But after a few hours the message is coming back.
What can I do? Maybe manually delete all the logs via terminal/ssh?
Controller: v.5.1.7 (Software Controller via Ubuntu - with enough space, CPU, RAM).
2 x TL-SG2008P v3.0
2 x EAP660 HD(EU) v1.0
- Copy Link
- Report Inappropriate Content
*imagine that this OC200 could have an option for more disk space* ?
/me looks sadly to the USB remaining disk space of the USB drive which is attached to the OC200 , not everybody wants to run a syslog
Why can't we reserved a preconfigured amount of space on the USB device ?
and then when OC200 hits its internal limit , it 'batch copies' a big amount of logs to the USB device ? then at least the USB disk is not hammered with write requests the whole time.
I wouldn't care if logs on the USB devices are not easily retrieval via the GUI or maybe later there could be an option in the gui to pull back a batch log and display the logs or events , I don't know ?
Disk
(1.85 GB free of 3.00 GB)
USB Disk1:
(14.89 GB free of 14.92 GB)
its not like the USB will be full anytime soon , might as wel use it as long time log storage
autobackup_5.0.30_365days_(2022-03-01_12-00-00_1646132400266).cfg |
2022-03-01 |
5.42 MB |
|
autobackup_5.0.30_365days_(2022-02-01_12-00-00_1643713200668).cfg |
2022-02-01 |
5.33 MB |
|
autobackup_5.0.29_365days_(2022-01-01_12-00-00_1641034800724).cfg |
2022-01-01 |
5.29 MB |
|
autobackup_365days_1638352800730.cfg |
2021-12-01 |
9.11 MB |
|
autobackup_365days_1635760800256.cfg |
2021-11-01 |
7.06 MB |
|
autobackup_365days_1633082400307.cfg |
2021-10-01 |
3.15 MB |
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 9057
Replies: 18
Voters 0
No one has voted for it yet.