NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Nick-Ashfab's avatar
Nick-Ashfab
Aspirant
Mar 20, 2025

Netgear GS752TPv3 Logs Flooded with Restarted ConfigAgent - No Health response

Hello,

We have a Netgear GS752TPv3 that we have configured to write logs to our Syslog server and we've found that it is flooding the log with the same 2 lines every 10 or 15 minutes. 


2025-03-17 00:01:47 Kernel.Debug [IP] 1 2025-03-16T13:01:48.184Z: %[IP]-1 discAgent-7 nal_logging.c(39): Restarted ConfigAgent - No Health response.
2025-03-17 00:02:02 Kernel.Debug [IP] 1 2025-03-16T13:02:03.338Z: %[IP]-1 discAgent-7 nal_logging.c(39): cloud operation mode:0

 

We've disabled Insight on the switch but the same lines keep appearing. 
It is running the latest firmware available (6.2.0.36)

 

We are trying to track why the switch will randomly drop half the ports in the switch if its left on for more than 30 days and with the logging being flooded, its very difficult to read what is going on. 

Thanks,

Nick

 

4 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    Have a config file saved for the switch? Save one off then you might do a factory reset on the switch and setup default settings at first and then check for logging entries, if you don't find anything happening, load up the save config file then check again for changes in logging. 

    • Nick-Ashfab's avatar
      Nick-Ashfab
      Aspirant

      We've factory restored the switch, all we have configured is the static IP on the device and it was throwing a different error flooding the logs after the restore (GET /api/v1/test (null), then I disabled insight on the device and the original log entry is appearing every few minutes. 
      Attached is a screenshot of the logging showing the system restore to default, the logging before disabling insight and logs afterwards. 

      Thanks,
      Nick. 

      • Nick-Ashfab's avatar
        Nick-Ashfab
        Aspirant

        Just adding that this issue only appears when the severity filter is set to DEBUG, if its set to anything else (informational, notice, warning etc) the issue doesnt appear BUT we want debug level logging to find the cause of the switch locking up. 

        Thanks

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More