Search failedSyntaxError: Unexpected token < in JSON at position 0

[wanderson]

Server

• FOG Version: 1.40
• OS: CENTOS 7

Client

• Service Version: 1.35
• OS: Windows 7 Professional

Description

I have the 1.40 fog with 35 storages connected to it.

When I start to download an image, the apache server drops and comes back, it flashes, so computers have this error when they start.

It also gives JASON error: Search failedSyntaxError: Unexpected token < in JSON at position 0

[george1421]

@wanderson Can we get a little bigger screen shot of the error.

Also can you explain what 35 storages connected mean?

Did this FOG server ever download or did you change something?

Lastly if you tail /var/log/httpd/error_log is there anything helpful in there?

[wanderson]

1. Storage == FOG NODE

2. FOG 1.35 update to FOG 1.40

3. 

[george1421]

@wanderson Yep, we are going to need the developers to look at these error.

just to be clear you did update from 1.3.5 to 1.4.1?

[wanderson]

@george1421

update fog 1.35 to 1.40

[george1421]

@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.

[wanderson]

@george1421

Apache is not able to answer all requests, would it?

[Tom Elliott]

@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).

[Tom Elliott]

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.

[Tom Elliott]

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?

[wanderson]

@Tom-Elliott

update fog sucess fog 1.40

[Tom Elliott]

@wanderson And the task page is still giving the json token error?

[wanderson]

@Tom-Elliott When I restart the server, it works again, but then the error happens again

[wanderson]

@Tom-Elliott Would not the httpd be down?

[Tom Elliott]

What? Why would httpd be down?

This sounds like a max_connections issue to me though.

[wanderson]

@Tom-Elliott Yes, after a few minutes, give the error http 500

[wanderson]

@Tom-Elliott

I will try to apply this rule in apache

<IfModule mpm_prefork_module>
	StartServers          4
	MinSpareServers       20
	MaxSpareServers      40
	MaxClients           200
	MaxRequestsPerChild  4500
</IfModule>```

[Tom Elliott]

@wanderson Is it giving 500, or is it getting “connection” errors? 500 means apache is responding.

[wanderson]

@Tom-Elliott, yes, Was giving HTTP 500 connection errors while doing the image upload task

[wanderson]

Problems began to appear after I started adding more than 20 nodes, I’m currently using 34 fog nodes