(Migrated) zato json paser error

Community support
#1

(This message has been automatically imported from the retired mailing list)

i am is baocaixiong. and i had given you a picture not long ago. i am sorry
for my poor spoken english.

from https://twitter.com/baocaixiong/status/402373226832986112/photo/1.

#2

On 11/18/2013 03:25 PM, 张明 wrote:

i had given you a picture not long ago.

from https://twitter.com/baocaixiong/status/402373226832986112/photo/1.

Hi 明,

most likely, the reason for this message is that at that time no server
was running in your environment.

Here are the details

  • web admin is the admin GUI console
  • web admin communicates with servers through their load balancer
  • the communication uses JSON

So what happened was

  • you visited a page in the admin
  • this resulted in a JSON message being sent to one of the servers
  • but no server was running so there was no JSON response
  • the missing response could not be parsed hence the parsing error

Next time it happens, if at all, please issue these commands

$ zato info /path/to/web-admin
$ zato info /path/to/load-balancer
$ zato info /path/to/server1
$ zato info /path/to/server2

and then we will know whether all the components are running properly.

#3

On 11/18/2013 03:25 PM, 张明 wrote:

i had given you a picture not long ago.

from https://twitter.com/baocaixiong/status/402373226832986112/photo/1.

Hi 明,

most likely, the reason for this message is that at that time no server
was running in your environment.

Here are the details

  • web admin is the admin GUI console
  • web admin communicates with servers through their load balancer
  • the communication uses JSON

So what happened was

  • you visited a page in the admin
  • this resulted in a JSON message being sent to one of the servers
  • but no server was running so there was no JSON response
  • the missing response could not be parsed hence the parsing error

Next time it happens, if at all, please issue these commands

$ zato info /path/to/web-admin
$ zato info /path/to/load-balancer
$ zato info /path/to/server1
$ zato info /path/to/server2

and then we will know whether all the components are running properly.