Page 1 of 1

Warning in line 8131

PostPosted: Thu Jun 03, 2021 8:46 am
by MarcoGT
Hi Karl,

I see every minute this warning plus the log message you see below
Code: Select all
3. Jun 2021 at 16:36:43
   uniFiAP Warning                 in Line 8131 has error=No JSON object could be decoded
   uniFiAP                         checkAndPrepDict JSON len:77; mca-dump | sed -e 's/^ *//' UAP-Sala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1...
...  ala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1
   uniFiAP                         .... in receiving DICTs for APdict-192.168.2.128;  for details check unifi logfile  at: /Library/Application Support/Perceptive Automation/Indigo 7.5/Logs/com.karlwachs.uniFiAP/plugin.log

3. Jun 2021 at 16:37:31
   uniFiAP Warning                 in Line 8131 has error=No JSON object could be decoded
   uniFiAP                         checkAndPrepDict JSON len:77; mca-dump | sed -e 's/^ *//' UAP-Sala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1...
...  ala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1
   uniFiAP                         .... in receiving DICTs for APdict-192.168.2.128;  for details check unifi logfile  at: /Library/Application Support/Perceptive Automation/Indigo 7.5/Logs/com.karlwachs.uniFiAP/plugin.log

3. Jun 2021 at 16:38:15
   uniFiAP Warning                 in Line 8131 has error=No JSON object could be decoded
   uniFiAP                         checkAndPrepDict JSON len:77; mca-dump | sed -e 's/^ *//' UAP-Sala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1...
...  ala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1
   uniFiAP                         .... in receiving DICTs for APdict-192.168.2.128;  for details check unifi logfile  at: /Library/Application Support/Perceptive Automation/Indigo 7.5/Logs/com.karlwachs.uniFiAP/plugin.log

3. Jun 2021 at 16:38:59
   uniFiAP Warning                 in Line 8131 has error=No JSON object could be decoded
   uniFiAP                         checkAndPrepDict JSON len:77; mca-dump | sed -e 's/^ *//' UAP-Sala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1...
...  ala-BZ.v4.3.28# xxxThisIsTheEndTokenxxx1
   uniFiAP                         .... in receiving DICTs for APdict-192.168.2.128;  for details check unifi logfile  at: /Library/Application Support/Perceptive Automation/Indigo 7.5/Logs/com.karlwachs.uniFiAP/plugin.log

3. Jun 2021 at 16:39:44
   uniFiAP Warning                 in Line 8131 has error=No JSON object could be decoded
   uniFiAP                         checkAndPrepDict JSON len:77; mca-dump | sed

Re: Warning in line 8131

PostPosted: Thu Jun 17, 2021 10:43 am
by Different Computers
I'm getting these too, now. Sometimes every ten minutes, other times, several times a minute.

Re: Warning in line 8131

PostPosted: Thu Jun 17, 2021 2:12 pm
by kw123
Restarting the unifi-ap fixes it.

I have that in one of my unifi-ap but only once a month or so.

As I can’t replicate it’s difficult to fix in the plugin.


Sent from my iPhone using Tapatalk

Re: Warning in line 8131

PostPosted: Fri Jul 02, 2021 8:56 am
by Different Computers
Finally got a chance to reboot my UDM this morning.

This showed back up immediately:
Code: Select all
uniFiAP Warning                 in Line 8131 has error=No JSON object could be decoded
   uniFiAP                         checkAndPrepDict JSON len:56; mca-dump | sed -e 's/^ *//' xxxThisIsTheEndTokenxxx1...
...  ed -e 's/^ *//' xxxThisIsTheEndTokenxxx1
   uniFiAP                         .... in receiving DICTs for APdict-192.168.0.123;  for details check unifi logfile  at: /Library/Application Support/Perceptive Automation/Indigo 2021.1/Preferences/Plugins/com.karlwachs.uniFiAP/plugin.log


that mention of 192.168.0.123 makes me wonder though: is this a problem at the UDM, or with the AP? 192.168.0.123 is my AP.

Warning in line 8131

PostPosted: Fri Jul 02, 2021 9:49 am
by kw123
I guess that's your AP.

a restart of the AP should fix this .. you can do that from the plugin or the unifi controller or the iPhone app

Karl

ps i am still waiting for one of my 4 APs to get into that state to diagnose it in detail and how to auto fix it

Re: Warning in line 8131

PostPosted: Mon Jul 05, 2021 9:01 am
by Different Computers
Does look like the AP restart fixed it.