Chronic SYSTEM WARNING The number of logs is up to the limit.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Chronic SYSTEM WARNING The number of logs is up to the limit.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
21 Reply
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-02-12 02:39:17

  @ChrisDV  I checked the log entries (It's possible to download the log list in the "Export Data" section.)

 

The log is full of DHCP entries.  But as far as I can see, all DHCP logging notifications are turned off.   

 

Where can I find the function to turn off DHCP server logs?

 

I tried managing the router, but it is being controlled by the OC200, so no luck there.

I looked through all the Log Notifications and Gateway DHCP Events is already turned off.

  0  
  0  
#12
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-02-12 02:40:40
...and all the DHCP Log entries are for just one VLAN
  0  
  0  
#13
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-02-12 03:22:10
I Used "Clear" in the logs section to remove "Gateway DHCP Server Module Information" logs. That cleared the massive number of log entries. But the entries were still be added very fast even though there were very few clients on the network. But now I can see that the DHCP system is allocating addresses to 5 clients every few seconds. They are all IOT devices belonging to the electricity management ssystem (Acrel AWT100 Gateway smart-meter connections). I'm guessing, but if the system manager of the gateways has set a fixed IP address then the gateways will continually be unstable. So 2 quick answers:- 1. The logging system actually records log events that are set to "No notification" 2. There is an issue with DHCP and devices that may be incorrectly configured.
  0  
  0  
#14
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-02-12 09:47:06

  @ChrisDV 

 I find that if I leave the logs to accumulate, eventually the whole system will collapse. DHCP will stop working and I will be unable to manage the controller. 

That is probably also the case here. My whole infrastructure is very sluggish for the past few days.  Just received the "log full" email again.

 

It's possible to download the log list in the "Export Data" section.

Thanks for the tip, will have a look.

 

The logging system actually records log events that are set to "No notification" 

Probably yes, but the unchecked setting hides them in the logs? Weird behavior.

  0  
  0  
#15
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-02-12 11:13:29

Update. Downloaded the log ist. Has 4365 entries. It has 1/3 of
"[client:xxx] was disconnected from network "yyy" on [osw:xxx:Switch](connected time:8m connected, traffic: 0Bytes)."

and 2/3 of 
"DHCP Server allocated IP address yyyyy for the client[MAC: zzzzzz]."

 

with recent time and date - last 12 days.

Nothing visible in the controller logs.

 

This is all disabled: 

Gateway DHCP Client Module Information

Gateway DHCP Server Module Information

Client Disconnect (Wireless)
Client Disconnected (Wired)

 

Definitely looks like a bug.

  0  
  0  
#16
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-02-12 14:04:13

  @aly-fly  Yes.  I can easily reproduce two "weird behaviours":

1. When the log list is full, the DHCP system becomes unstable and I lose the ability to use local connection for management. The WAN link works because it does not use DHCP, but the system seems to be in a panic and functions extremely slowly until some log entries have been deleted. Then I can get control. 

2. The undisplayed log entries are just hidden. They are still in the Log List.  They can be deleted as a single action after you can control of the web interface, but until then you have to delete the 3 or 4 at a time using the phone app.

  0  
  0  
#17
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-02-20 04:20:53

I discussed the problem with a Support agent.  I was told that there is an error in that the DHCP entries should not be being logged if the Notifications setting is unchecked.  I was advised to upgrade to the latest version of controller firmware, but actually I'm already running the latest version.  OC200 V2, 5.12.9,  2.11.3 Build 20230906 Rel.36272.

 

Why am I getting the problem but it has not been noticed by other people?  Well, I guess I have several hundreds of DHCP actions to new devices every day.  But also, we have 5 IoT devices misbehaving. They are causing DHCP actions every few seconds so the number of DHCP log entries builds up very rapidly.

 

Why does the system go into a panic when the log is full?  I don't know. Maybe it's trying to tidy the log, but the log gets untidy just as fast as it can be tidied. Certainly I have to clean the log list every day or we get severe performance problems.   

  0  
  0  
#18
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-05-08 14:31:25 - last edited 2024-05-08 14:31:54

 I also have this problem and it's extremely annoying.  

 

Have the latest controller firmware. I have been following the issues for some time.  My logs are filled with DHCP connections(verified by export) and that's disabled. I archive/clean all and it gets filled quickly.  I get notified constantly its over the limit.  Its to the point I ignore the emails - boy who cried wolf scenario.   Please fix this BS!!  We are getting ready to buy more equipment but I'm not so sure about this support anymore!

  0  
  0  
#19
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-05-08 16:35:39

  @Paulait  I don't have issues anymore since the last FW update of my OC200.

  0  
  0  
#20
Options
Re:Chronic SYSTEM WARNING The number of logs is up to the limit.
2024-05-09 02:53:59

  @aly-fly  Agreed. The initial fix just stopped the warning but there was also a memory problem that seems to have been fixed by the update.

There is now an IP address problem and a significant delay in displayed data being updated with correct values.

  0  
  0  
#21
Options