Wireless Controller WM3700 CGI and SSH Connection Fault Foot

  • 0
  • 1
  • Problem
  • Updated 1 year ago
  • Solved

MODEL : WM3700

VERSION : 5.5.5.0-018R


nice to meet you. A failure has occurred. Extreme wireless controller suddenly
CGI and SSH do not connect.
You have saved the log at the time of the failure. If you see this log, what problems
I would like to ask you if it occurred and how to fix it.


-----------------LOG--------------------------------------------------------------------------------------------------------

Jun 19 14:19:11 2017: ap4600-67ECA0 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67ECA0:R2'. New channel: 60 freq 5300 MHz. Scan time: 70 secs
Jun 19 14:19:11 2017: ap4600-67ECA0 : %RADIO-4-RADAR_DETECTED: Radar found on channel 52 freq 5260 MHz
Jun 19 14:19:10 2017: ap4600-67E98C : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67E98C:R2'. New channel: 149 freq 5745 MHz. Scan time: 0 secs
Jun 19 14:19:10 2017: ap4600-67E98C : %RADIO-4-RADAR_DETECTED: Radar found on channel 60 freq 5300 MHz
Jun 19 14:19:09 2017: ap4600-67FB34 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67FB34:R2'. New channel: 100 freq 5500 MHz. Scan time: 70 secs
Jun 19 14:19:09 2017: ap4600-67FB34 : %RADIO-4-RADAR_DETECTED: Radar found on channel 60 freq 5300 MHz
Jun 19 14:19:07 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:19:00 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:18:52 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:18:37 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot server parse2 failed
Jun 19 14:18:33 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:18:32 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:18:22 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:18:16 2017: ap4600-67EEA8 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67EEA8:R2'. New channel: 40 freq 5200 MHz. Scan time: 0 secs
Jun 19 14:18:16 2017: ap4600-67EEA8 : %RADIO-4-RADAR_DETECTED: Radar found on channel 52 freq 5260 MHz
Jun 19 14:18:10 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot server parse2 failed
Jun 19 14:18:07 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot server parse2 failed
Jun 19 14:18:02 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:18:01 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:59 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:57 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:54 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:48 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:47 2017: ap4600-67EB80 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67EB80:R2'. New channel: 48 freq 5240 MHz. Scan time: 0 secs
Jun 19 14:17:47 2017: ap4600-67EB80 : %RADIO-4-RADAR_DETECTED: Radar found on channel 60 freq 5300 MHz
Jun 19 14:17:36 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:30 2017: ap4600-67EDF0 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67EDF0:R2'. New channel: 52 freq 5260 MHz. Scan time: 70 secs
Jun 19 14:17:30 2017: ap4600-67EE70 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67EE70:R2'. New channel: 104 freq 5520 MHz. Scan time: 70 secs
Jun 19 14:17:30 2017: ap4600-67EDF0 : %RADIO-4-RADAR_DETECTED: Radar found on channel 60 freq 5300 MHz
Jun 19 14:17:30 2017: ap4600-67EE70 : %RADIO-4-RADAR_DETECTED: Radar found on channel 60 freq 5300 MHz
Jun 19 14:17:29 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:25 2017: ap4600-67F8E8 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: 'ap4600-67F8E8:R2'. New channel: 44 freq 5220 MHz. Scan time: 0 secs
Jun 19 14:17:25 2017: ap4600-67F8E8 : %RADIO-4-RADAR_DETECTED: Radar found on channel 52 freq 5260 MHz
Jun 19 14:17:12 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:09 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 14:17:07 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot policy parse failed
Jun 19 13:17:02 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 13:17:02 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 13:17:02 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 13:17:02 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.5F.31.D0:timed out
Jun 19 13:17:02 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.FB.8C:timed out
Jun 19 13:17:02 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.5F.29.FC:timed out
Jun 19 13:17:02 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.FB.34:timed out
Jun 19 13:17:01 2017: %KERN-3-ERR: Out of memory: Killed process 11846 (dpd2)..
Jun 19 13:17:01 2017: %KERN-3-ERR: Out of Memory: Kill process 11846 (dpd2) score 440 and children..
Jun 19 12:25:02 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.F9.94:timed out
Jun 19 12:24:47 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EA.84:timed out
Jun 19 12:24:26 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E8.F0:timed out
Jun 19 12:24:14 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EB.54:timed out
Jun 19 12:23:51 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EF.5C:timed out
Jun 19 12:23:24 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot server parse2 failed
Jun 19 12:20:02 2017: wm3700-59275E : %DEVICE-4-OFFLINE: Device 00-04-96-67-ED-48(1F_8_67ED48) is offline, last seen:10 minutes ago on switchport -
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.ED.1C:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.ED.C8:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.FB.04:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.ED.88:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.F9.C4:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EB.7C:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EB.B0:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E9.84:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EA.90:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E8.14:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E7.88:timed out
Jun 19 12:20:01 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.FA.AC:timed out
Jun 19 12:20:00 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E8.DC:timed out
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E8.F8:timed out
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.F9.6C:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E8.24:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.ED.54:timed out
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EB.50:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E9.E0:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.ED.D0:timed out
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E7.3C:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EB.C8:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.ED.68:timed out
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EE.50:timed out
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E8.B4:timed out
Jun 19 12:19:29 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.5F.2F.A8:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:27 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EC.7C:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:19:11 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EE.A8:[Errno 145] Connection timed out
Jun 19 12:17:23 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.EE.5C:[Errno 32] nbsocket.recvall(16): EOF with insufficent 0 bytes of data
Jun 19 12:17:02 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E9.34:timed out
Jun 19 12:13:52 2017: wm3700-59275E : %DIAG-4-CPU_LOAD: 1 minute average load limit exceeded, value is 100.0% limit is 99.9% (top processes: cfgd using 34.0)
Jun 19 12:13:51 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jun 19 12:13:51 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jun 19 12:13:51 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jun 19 12:13:51 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jun 19 12:13:50 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: [Errno 145] Connection timed out
Jun 19 12:12:59 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 12:12:41 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 12:12:39 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 12:12:32 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 12:12:05 2017: %USER-3-ERR: hslogin.c: CP Login : Invalid/Missing auth response from RIM (type 16)
Jun 19 12:10:56 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT:  Conflict in destination ip-gateway mac between packet and snoop table data : Vlan = 206, Pkt Src Mac: AC-EE-9E-FF-B2-EB, Pkt Dst Mac: FF-FF-FF-FF-FF-FF, Pkt Dst IP : 192.168.200.3, Snoop Table  Mac: 00-04-96-51-AC-F3, Snoop Table IP: 192.168.206.1 .
Jun 19 12:10:46 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 1 minute average load limit exceeded, value is 100.0% limit is 99.9% (top processes: hsd using 89.6)
Jun 19 12:10:31 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: [Errno 131] Connection reset by peer
Jun 19 12:10:31 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: [Errno 131] Connection reset by peer
Jun 19 12:10:31 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: [Errno 131] Connection reset by peer
Jun 19 12:10:31 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: [Errno 131] Connection reset by peer
Jun 19 12:10:31 2017: %USER-3-ERR: main.pyo: * * ERROR: receive update error: [Errno 131] Connection reset by peer
Jun 19 12:10:30 2017: %USER-3-ERR: main.pyo: * * ERROR: error communicating with 46.67.E8.BC:[Errno 131] Connection reset by peer
Jun 19 12:10:13 2017: %DAEMON-3-ERR: dhcpd: Abandoning IP address 192.168.217.15: pinged before offer
Jun 19 12:09:59 2017: %DAEMON-3-ERR: dhcpd: Abandoning IP address 192.168.204.222: pinged before offer
Jun 19 12:09:37 2017: 9F_10_67ED18 : %RADIO-4-RADAR_DET_INFO: Radar info: Radio: '9F_10_67ED18:R2'. New channel: 40 freq 5200 MHz. Scan time: 0 secs
Jun 19 12:09:37 2017: 9F_10_67ED18 : %RADIO-4-RADAR_DETECTED: Radar found on channel 100 freq 5500 MHz
Jun 19 12:07:34 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT:  Conflict in destination ip-gateway mac between packet and snoop table data : Vlan = 218, Pkt Src Mac: 18-83-31-9D-6A-81, Pkt Dst Mac: FF-FF-FF-FF-FF-FF, Pkt Dst IP : 192.168.200.3, Snoop Table  Mac: 00-04-96-51-AC-F3, Snoop Table IP: 192.168.218.1 .
Jun 19 12:07:11 2017: %USER-3-ERR: hslogin.c: CP Login: hotspot server parse2 failed
Jun 19 12:07:06 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT:  Conflict in destination ip-gateway mac between packet and snoop table data : Vlan = 218, Pkt Src Mac: 18-83-31-9D-6A-81, Pkt Dst Mac: FF-FF-FF-FF-FF-FF, Pkt Dst IP : 192.168.200.3, Snoop Table  Mac: 00-04-96-51-AC-F3, Snoop Table IP: 192.168.218.1 .
Jun 19 12:04:53 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT - NO PACKET DROP:  Conflict in ip-mac binding between packet and snoop table data : Vlan = 217, Pkt Src Mac: 00-04-96-51-AC-F3, Pkt Dst Mac: 5C-70-A3-7D-16-A4, Pkt Dst IP : 192.168.217.214, Snoop Table  Mac: 94-76-B7-17-33-21, Snoop Table IP: 192.168.217.214 .
Jun 19 12:04:38 2017: %USER-2-CRIT: Monitoring Subsystem: Free memory 20420 kB, running low
Jun 19 12:04:16 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT - NO PACKET DROP:  Conflict in ip-mac binding between packet and snoop table data : Vlan = 218, Pkt Src Mac: 00-04-96-51-AC-F3, Pkt Dst Mac: F8-A9-D0-00-81-C6, Pkt Dst IP : 192.168.218.218, Snoop Table  Mac: E4-FA-ED-81-99-06, Snoop Table IP: 192.168.218.218 .
Jun 19 12:03:57 2017: %DAEMON-3-ERR: dhcpd: Abandoning IP address 192.168.210.247: pinged before offer
Jun 19 12:03:55 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT:  Conflict in destination ip-gateway mac between packet and snoop table data : Vlan = 208, Pkt Src Mac: 08-EE-8B-11-ED-E5, Pkt Dst Mac: FF-FF-FF-FF-FF-FF, Pkt Dst IP : 192.168.200.3, Snoop Table  Mac: 00-04-96-51-AC-F3, Snoop Table IP: 192.168.208.1 .
Jun 19 12:03:50 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT - NO PACKET DROP:  Conflict in ip-mac binding between packet and snoop table data : Vlan = 217, Pkt Src Mac: 00-04-96-51-AC-F3, Pkt Dst Mac: 5C-70-A3-7D-16-A4, Pkt Dst IP : 192.168.217.214, Snoop Table  Mac: 94-76-B7-17-33-21, Snoop Table IP: 192.168.217.214 .
Jun 19 12:03:35 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 1 minute average load limit exceeded, value is 100.0% limit is 99.9% (top processes: hsd using 96.8)
Jun 19 12:03:34 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 5 minute average load limit exceeded, value is 100.0% limit is 98.0% (top processes: hsd using 96.5)
Jun 19 12:03:34 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 15 minute average load limit exceeded, value is 100.0% limit is 95.0% (top processes: hsd using 96.4)
Jun 19 12:03:12 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT - NO PACKET DROP:  Conflict in ip-mac binding between packet and snoop table data : Vlan = 218, Pkt Src Mac: 34-FC-EF-EF-1A-09, Pkt Dst Mac: 00-04-96-51-AC-F3, Pkt Src IP : 192.168.218.218, Snoop Table  Mac: E4-FA-ED-81-99-06, Snoop Table IP: 192.168.218.218 .
Jun 19 12:03:12 2017: %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING:  Conflicting snoop entry found :Ethernet Src Mac: 34-FC-EF-EF-1A-09, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 34-FC-EF-EF-1A-09, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 192.168.218.218, ARP Target IP: 192.168.218.1, Snoop Table MAC = E4-FA-ED-81-99-06, Snoop Table IP = 192.168.218.218.
Jun 19 12:03:03 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 1 minute average load limit exceeded, value is 100.0% limit is 99.9% (top processes: hsd using 96.6)
Jun 19 12:03:03 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 5 minute average load limit exceeded, value is 100.0% limit is 98.0% (top processes: hsd using 96.5)
Jun 19 12:03:03 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 15 minute average load limit exceeded, value is 100.0% limit is 95.0% (top processes: hsd using 96.4)
Jun 19 12:03:02 2017: %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT - NO PACKET DROP:  Conflict in ip-mac binding between packet and snoop table data : Vlan = 217, Pkt Src Mac: 5C-70-A3-7D-16-A4, Pkt Dst Mac: 01-00-5E-7F-FF-FA, Pkt Src IP : 192.168.217.214, Snoop Table  Mac: 94-76-B7-17-33-21, Snoop Table IP: 192.168.217.214 .
Jun 19 12:03:02 2017: %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING:  Conflicting snoop entry found :Ethernet Src Mac: 5C-70-A3-7D-16-A4, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 5C-70-A3-7D-16-A4, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 192.168.217.214, ARP Target IP: 192.168.217.1, Snoop Table MAC = 94-76-B7-17-33-21, Snoop Table IP = 192.168.217.214.
Jun 19 12:02:32 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 1 minute average load limit exceeded, value is 100.0% limit is 99.9% (top processes: hsd using 96.5)
Jun 19 12:02:32 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 5 minute average load limit exceeded, value is 100.0% limit is 98.0% (top processes: hsd using 96.4)
Jun 19 12:02:31 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 15 minute average load limit exceeded, value is 100.0% limit is 95.0% (top processes: hsd using 96.4)
Jun 19 12:02:01 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 1 minute average load limit exceeded, value is 100.0% limit is 99.9% (top processes: hsd using 96.5)
Jun 19 12:02:01 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 5 minute average load limit exceeded, value is 100.0% limit is 98.0% (top processes: hsd using 96.2)
Jun 19 12:02:01 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 15 minute average load limit exceeded, value is 100.0% limit is 95.0% (top processes: hsd using 96.4)
Jun 19 12:01:30 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 1 minute average load limit exceeded, value is 100.0% limit is 99.9% (top processes: hsd using 96.5)
Jun 19 12:01:29 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 5 minute average load limit exceeded, value is 100.0% limit is 98.0% (top processes: hsd using 96.2)
Jun 19 12:01:29 2017: 9F_2_67EC6C : %DIAG-4-CPU_LOAD: 15 minute average load limit exceeded, value is 100.0% limit is 95.0% (top processes: hsd using 96.4)

Photo of jeon min

jeon min

  • 340 Points 250 badge 2x thumb

Posted 1 year ago

  • 0
  • 1
Photo of Taykin Izzet

Taykin Izzet , Employee

  • 2,924 Points 2k badge 2x thumb
Jeon, there is a concern of the 1, 5, and 15 minute load limits being exceeded by the hsd process. Can you check to see if is still being consumed and try to restart the process?

service show top
service signal abort hsd

If the process is still high, let us know and we will investigate further. A reboot of the controller may also be helpful (if not performed so far).
(Edited)
Photo of jeon min

jeon min

  • 340 Points 250 badge 2x thumb
Let's see if it looks the same through log and process monitoring.
After checking, I will reply in case of abnormal log or abnormal symptom, but what is hsd process?
(Edited)