Posted this in the Skylark 4.4 release topic but wanted to make it’s own.
The messages log in /var/logs on my installation is getting hammered with messages like:
Mar 6 03:48:39 outernet user.notice root: 2017-03-06T03:48:39.894Z httpCall exception SyntaxError: Unexpected token % in JSON at position 1 SyntaxError: Unexpected token % in JSON at position 1
Mar 6 03:48:39 outernet user.notice root: at Object.parse (native)
Mar 6 03:48:39 outernet user.notice root: at IncomingMessage. (/usr/lib/node_modules/ui2/server/http.js:324:27)
I added a bit of logging to see what was being sent to function httpCall and most of the messages that are causing the exceptions are trying to be parsed as JSON with var args = JSON.parse(Buffer.concat(body)); but the body does not appear to be JSON. Most contents being sent through that are causing the messages are like the following:
%
^_SelfTuningClient-834553913-1565^P^B^X^A,
or
%2Fnew=150&%2Flatest=2057&%2Funread%2F1978=169&%2Fdelete=1&%2Frecover=0&%2Fglobal%2Fasset-version=2&%2Fsite%2Fbanner=2&%2Ffile-change=24&%2Flogout=134&%2Fsite%2Fread-only=0&%2Fnotification%2F19
or
^O
834553913^P ^X^A
^O
834553913^P^D^X^A
^O
834553913^P^E^X^A
^O
834553913^P^C^X^A
^O
834553913^P^B^X^A
^V
^Ppsn-XKKCXMF3FVVC^P^L^X^A
^Z
^Ttid-sSqf6AAAVXDX4bnw^P^F^X^B,
These are causing the bulk of the exceptions. Other, normal messages that are JSON do work of course, like:
{“path”:“home:///”},
when opening file manager in the GUI. Or the username and password when logging into the GUI.
Do any of the non-json messages look familiar at all?
I know it’s just a logging issue, but for whatever reason, it is nagging at me.
Maybe just take out the logging of the errors for now if they don’t impact functionality?