'Critical' error in log ( Prey 1.8.3; Linux)

Help
#1

critical Mon, 15 Apr 2019 13:59:57 GMT UNCAUGHT EXCEPTION: Unexpected token <

Prey 1.8.3 on Linux Mint 19.1 x64 Cinnamon. Kernel 5.0.7-050007-generic.

Everything seems to work, though (except that there are some other errors in the log too).

#2

Hi @rtrtEerUt,

That happens sometimes when the client has issues parsing some data, after that error the client should restart and keep going normally.
Please let me know if the problem persists.

Regards,
Javo

#3

Dear Javo

Thank you. I will do that.

You might want to put something to the effect of what you said into the log message itself (e.g. ‘Prey should restart; please report the problem on the forum if the problem persists’).

1 Like
#4

Javo,

I still have the problem. I note that the problem is marked ‘critical’ in the log. I note also that my system is set to create an alert when the logs contain a report of a critical error. And this is not, you say, actually a critical error. So at the least Prey should downgrade the severity of what is, in truth, a mere warning.

#5

Hi @rtrtEerUt, can i see your log file please?

Javo

#6

Certainly. Here (on PasteBin) is a relevant (and redacted) snippet.

By the way: just now, trying to reach this site, I got a ‘bad gateway’ error.