Warn messages about log_device_status_push after upgrade to 5.13.30.8

Warn messages about log_device_status_push after upgrade to 5.13.30.8

Warn messages about log_device_status_push after upgrade to 5.13.30.8
Warn messages about log_device_status_push after upgrade to 5.13.30.8
2024-03-01 19:17:37
Hardware Version:
Firmware Version: 4.13.30.8

Since upgrading to 5.13.30.8, it looks like there is a warning message in the logs that is either just extra verbose or there is some sort of config issue.

 

Someone started a discussion on the container image repo: https://github.com/mbentley/docker-omada-controller/discussions/413

 

Warn messages:

 

03-01-2024 11:06:15.157 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist
03-01-2024 11:11:15.157 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist
03-01-2024 11:16:15.157 WARN [quartzScheduler_Worker-1] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist
03-01-2024 11:21:15.157 WARN [quartzScheduler_Worker-1] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist
03-01-2024 11:26:15.160 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist
03-01-2024 11:31:15.157 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist
03-01-2024 11:36:15.157 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist
03-01-2024 11:41:15.157 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (log_device_status_push, null) but did not execute because corresponding handler log_device_status_push doesn't exist

 

 

Doesn't seem to impact functionality though.

  0      
  0      
#1
Options
1 Reply
Re:Warn messages about log_device_status_push after upgrade to 5.13.30.8
2024-08-26 12:52:19

  @mbentley 

I see the same behaviour in 5.14.26.23, while analysing an issue with repeating performance issues on the network.

Any updates on this? Is it normal to have these repeating errors in the logs, every 5 minutes? 

 

 

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 415

Replies: 1

Related Articles