(Migrated) Re: Re: Fw: Re: Quickstart guide doesn't work! (for me!)

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

I have this problem every time I start the Environment=2E
If I use your command (and not the start script like the tutorial say) I h=
ave no error=2E Anyway, if I start the service in this way, the test comman=
d with curl for ping service refuse to respond=2E

-----Original message-----
Sent: marted=C3=AC, 24 marzo 2015 at 12:43:23
From: “Dariusz Suchojad” <dsuch@zato=2Eio>
To: “Robert asda” <robert_1@priest=2Ecom>
Subject: Re: [Zato-discuss] Fw: Re: Quickstart guide doesn’t work! (for m=
e!)

/proc/cpuinfo
/proc/meminfo

Ok, cool, the hardware is aplenty=2E

Is that OperationalError something intermittent or can you reproduce it
each time you start the environment?

Can issue the command below:

$ zato start /opt/zato/Tests/prova2/server1 --fg

?

This will run this one server in foreground so it can be stopped with
Ctrl-C=2E

When you start/stop it a few times, does that error pop up each time?

–=20
Dariusz Suchojad

https://zato=2Eio
ESB, SOA, REST, APIs and Cloud Integrations in Python

Hello,

I’ll add my two cents. Whenever I start Zato., I make sure to delete the
pid files and also I do a check config!!! You could try that too.
I delete the Pid Files from the following folders

  1. Server1
  2. Server2
  3. Load Balancer
  4. Web-admin

Regards,
Sharad

On Tue, Mar 24, 2015 at 9:47 AM, Dariusz Suchojad dsuch@zato.io wrote:

On 24/03/15 15:45, robert_1@priest.com wrote:

I have this problem every time I start the Environment.
If I use your command (and not the start script like the tutorial say) I
have no error.
Anyway, if I start the service in this way, the test command with curl
for ping service refuse to respond.

The curl will fail because it connects to the load-balancer which is on
port 11223.

To start each component individually you can issue:

$ zato start /path/to/load-balancer
$ zato start /path/to/server1
$ zato start /path/to/web-admin

This will work as well.

Thanks for the email - I’ll try to reproduce the situation.


Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and Cloud Integrations in Python

On 24/03/15 15:45, robert_1@priest.com wrote:

I have this problem every time I start the Environment.
If I use your command (and not the start script like the tutorial say) I have no error.
Anyway, if I start the service in this way, the test command with curl for ping service refuse to respond.

The curl will fail because it connects to the load-balancer which is on
port 11223.

To start each component individually you can issue:

$ zato start /path/to/load-balancer
$ zato start /path/to/server1
$ zato start /path/to/web-admin

This will work as well.

Thanks for the email - I’ll try to reproduce the situation.