NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WAX630E v12.8.0.6 log messages
I’m hoping someone from Netgear support can pass this along to engineering.
Since updating my multiple WAX630E access points to firmware version V12.8.0.6, all of them are continuously displaying the following messages in the system log files. New messages are generated about every second.
May 3 09:26:44 nddmp[5641]: nddmp total time to execute = 1.000000 seconds
May 3 09:26:43 nddmp[5641]: NDDMP: data received from lighttpd = "[REMOVED]"
May 3 09:26:43 nddmp[5641]: nddmp total time to execute = 0.000000 seconds
May 3 09:26:43 nddmp[5641]: NDDMP: data received from lighttpd = "[REMOVED]"
May 3 09:26:43 nddmp[5641]: nddmp total time to execute = 1.000000 seconds
May 3 09:26:42 nddmp[5641]: NDDMP: data received from lighttpd = "[REMOVED]"
May 3 09:26:30 root: monitor_stuck is running
May 3 09:26:14 root: monitor_stuck is running
May 3 09:25:58 root: monitor_stuck is running
May 3 09:25:42 root: monitor_stuck is running
1 Reply
Typical console level output, most is severity level [Diagnostics] only. It's written to volatile memory in a buffer of ~16 MB - the last lines lines (~17) are shown in the Web UI.
This is an WBE7xx for example:
May 4 14:03:05.232 netifd: vlan250 (29167): rm: can't remove '/tmp/run/br-vlan250_ip': No such file or directory
May 4 14:03:04.492 root: monitor_stuck is running
May 4 14:02:57.075 cloudAgent[32335]: Agent: Get Neighbor API scan response: 0
May 4 14:02:57.063 nddmp[23366]: nddmp total time to execute = 0.000000 seconds
May 4 14:02:57.060 nddmp[23366]: NDDMP: data received from lighttpd = { "system": { "monitor": { "initialApScanStatus": "" } } }
May 4 14:02:49.380 root: monitor_stuck is running
May 4 14:02:47.012 cloudAgent[32335]: Agent: Get Neighbor API scan response: 0
May 4 14:02:47.000 nddmp[23366]: nddmp total time to execute = 1.000000 seconds
May 4 14:02:46.998 nddmp[23366]: NDDMP: data received from lighttpd = { "system": { "monitor": { "initialApScanStatus": "" } } }
May 4 14:02:44.083 nddmp[23366]: nddmp total time to execute = 0.000000 seconds
May 4 14:02:36.948 cloudAgent[32335]: Agent: Get Neighbor API scan response: 0
May 4 14:02:36.937 nddmp[23366]: nddmp total time to execute = 0.000000 seconds
May 4 14:02:36.934 nddmp[23366]: NDDMP: data received from lighttpd = { "system": { "monitor": { "initialApScanStatus": "" } } }
May 4 14:02:35.173 netifd: vlan250 (29167): rm: can't remove '/tmp/run/br-vlan250_ip': No such file or directory
May 4 14:02:34.207 root: monitor_stuck is running
May 4 14:02:26.886 cloudAgent[32335]: Agent: Get Neighbor API scan response: 0
May 4 14:02:26.874 nddmp[23366]: nddmp total time to execute = 0.000000 seconds
Unless there really is something to worry - for these very rare cases - this all ends up on the console eg. for support reasons.
In case you are concerned about missing more potentially essential messages, operate a syslog server. There you can filter to severity levels - and more, depends on the syslog server of course.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
