Search failedSyntaxError: Unexpected token < in JSON at position 0
-
@wanderson Is that when the issue occurred? This is an abnormal error, I’m just trying to understand the trigger.
Any other insight you can provide will help the developers come to an answer quicker.
-
Apache is not able to answer all requests, would it?
-
@wanderson Those “last insert ID” errors are almost always fixed because:
https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy
That said, when updating, you probably need to refresh the page (after ensuring the DB is usable).
-
Mind you all,
the suggestions I give are based on experiences, this is not by any means a cureall for every situation. The lastInsertID might be present from the period of time you were updating the server to begin with, so unlikely to be the problem you’re experiencing.
-
Remember, errors and “solutions” are very subjective. One fix will not fix every scenario especially when dealing with different OS’s.
I gave information based on what i saw in the error, but this does not mean the “suggestion” I gave is going to fix the problem you were having.
In regards to things, did your server update?
-
update fog sucess fog 1.40
-
@wanderson And the task page is still giving the json token error?
-
@Tom-Elliott When I restart the server, it works again, but then the error happens again
-
@Tom-Elliott Would not the httpd be down?
-
What? Why would httpd be down?
This sounds like a max_connections issue to me though.
-
@Tom-Elliott Yes, after a few minutes, give the error http 500
-
I will try to apply this rule in apache
<IfModule mpm_prefork_module> StartServers 4 MinSpareServers 20 MaxSpareServers 40 MaxClients 200 MaxRequestsPerChild 4500 </IfModule>```
-
@wanderson Is it giving 500, or is it getting “connection” errors? 500 means apache is responding.
-
@Tom-Elliott, yes, Was giving HTTP 500 connection errors while doing the image upload task
-
Problems began to appear after I started adding more than 20 nodes, I’m currently using 34 fog nodes
-
@wanderson Maybe too many clients hitting the apache with requests? Please check your apache access and maybe error log to see what’s going on and how many requests from which hosts are coming in.
-
solved: update mysql.user set plugin=‘mysql_native_password’;