(Migrated) Help needed | Cluster --> Servers --> Server ---> Edit --> ConnectionError

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

Hi Team,
I am using Zato for my project and successfully setup the environment on my
machine. The zato web-admin UI is running perfectly and I have added
servers to load balancer
Now I am trying to change server name I am getting Connection
Error(Connection aborted error(111, ‘Connection refused’)).

Also when I am listing the plain http channels the same error is occurred.

I have attached the screen shots for your reference.

Please let me know if any additional information needed and hoping for help.

On 31/12/15 09:36, Nilesh Sutar wrote:

Now I am trying to change server name I am getting Connection
Error(Connection aborted error(111, ‘Connection refused’)).

Also when I am listing the plain http channels the same error is occurred.

I have attached the screen shots for your reference.

Hello Nilesh,

there are a few remarks here:

  • In your screenshot both of your servers appear to have been introduced
    to the LB to listen on 127.0.0.1:17010 - this looks like a mistake and
    one of them probably is on 17011 instead?

  • The ‘Connection refused’ error means that one of the components is not
    running or is not running on a TCP port another component is configured
    to use.

Can you please post the output from these commands executed right after
that error message?

$ zato info /path/to/load/balancer
$ zato info /path/to/server1
$ zato info /path/to/server2

thanks,

On 31/12/15 14:17, Nilesh Sutar wrote:

I have executed following commands after the error message

Please find the attachments of it.

Hi Nilesh,

in the output from ‘zato info /path/to/load-balancer’ you will note that
it only listens on port 20151, which is the LB’s agent used to submit
configuration commands to the LB itself.

https://zato.io/docs/architecture/load-balancer.html

The LB should also listen on a separate TCP port, one which is actually
used for distributing HTTP traffic across servers. By default, this is
port 11223.

Question is in that case if the core LB is started at all, i.e. its
agent is but the main process looks to be down.

The process is started in background using HAProxy, the default command
to start it is ‘haproxy’.

Thus, can you send the output from this command?

$ haproxy -v

thanks,

On 31/12/15 14:33, Nilesh Sutar wrote:

Actually I started loadbalancer and haproxy manually with commands
"zato start load-balancer" and " haproxy -Vd -f
/opt/zato/Cluster1/load-balancer/config/repo/zato.config &"

Ok, what does the below return?

$ sudo netstat -tulpn

Hi Dariusz,

Thank you for your quick response and pointing out the mistake of port no.
of second server.

I have corrected the port of second server with 17011.

I have executed following commands after the error message

Please find the attachments of it.

Thank you in Advance!

On Thu, Dec 31, 2015 at 4:12 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 31/12/15 09:36, Nilesh Sutar wrote:

Now I am trying to change server name I am getting Connection
Error(Connection aborted error(111, ‘Connection refused’)).

Also when I am listing the plain http channels the same error is
occurred.

I have attached the screen shots for your reference.

Hello Nilesh,

there are a few remarks here:

  • In your screenshot both of your servers appear to have been introduced
    to the LB to listen on 127.0.0.1:17010 - this looks like a mistake and
    one of them probably is on 17011 instead?

  • The ‘Connection refused’ error means that one of the components is not
    running or is not running on a TCP port another component is configured
    to use.

Can you please post the output from these commands executed right after
that error message?

$ zato info /path/to/load/balancer
$ zato info /path/to/server1
$ zato info /path/to/server2

thanks,


Dariusz Suchojad

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

Hi Dariusz,

Ok, The output of command is :
zato@ULTP-413:~/current$ haproxy -v
HA-Proxy version 1.4.24 2013/06/17
Copyright 2000-2013 Willy Tarreau w@1wt.eu

Actually I started loadbalancer and haproxy manually with commands “zato
start load-balancer” and " haproxy -Vd -f
/opt/zato/Cluster1/load-balancer/config/repo/zato.config &"

Please let me know for additional information.
Thank you again for responding me very quickly.

On Thu, Dec 31, 2015 at 6:52 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 31/12/15 14:17, Nilesh Sutar wrote:

I have executed following commands after the error message

Please find the attachments of it.

Hi Nilesh,

in the output from ‘zato info /path/to/load-balancer’ you will note that
it only listens on port 20151, which is the LB’s agent used to submit
configuration commands to the LB itself.

https://zato.io/docs/architecture/load-balancer.html

The LB should also listen on a separate TCP port, one which is actually
used for distributing HTTP traffic across servers. By default, this is
port 11223.

Question is in that case if the core LB is started at all, i.e. its
agent is but the main process looks to be down.

The process is started in background using HAProxy, the default command
to start it is ‘haproxy’.

Thus, can you send the output from this command?

$ haproxy -v

thanks,


Dariusz Suchojad

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

Hi Dariusz,

Please find the attachment

On Thu, Dec 31, 2015 at 7:09 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 31/12/15 14:33, Nilesh Sutar wrote:

Actually I started loadbalancer and haproxy manually with commands
"zato start load-balancer" and " haproxy -Vd -f
/opt/zato/Cluster1/load-balancer/config/repo/zato.config &"

Ok, what does the below return?

$ sudo netstat -tulpn


Dariusz Suchojad

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

On 31/12/15 14:50, Nilesh Sutar wrote:

Please find the attachment

[…]

Ok, the LB is bound to 127.0.0.1 - can you reconfigure it to listen on
0.0.0.0 and see if it helps?

thanks,

Hi Team,
Thank you for your valuable support. I have resolved all the issues.

My zato platform is running smoothly. :slight_smile:

On Wed, Jan 6, 2016 at 4:37 PM, Nilesh Sutar nilesh.sutar@synerzip.com
wrote:

Hi Dariusz,

I have binded LB to 0.0.0.0
Please find the attachment.

Thanks in advance for your help!

On Tue, Jan 5, 2016 at 10:22 PM, Nilesh Sutar nilesh.sutar@synerzip.com
wrote:

Hi Dariusz,
Ok, Will configure it and will let you know.

On Tue, Jan 5, 2016 at 6:05 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 31/12/15 14:50, Nilesh Sutar wrote:

Please find the attachment

[…]

Ok, the LB is bound to 127.0.0.1 - can you reconfigure it to listen on
0.0.0.0 and see if it helps?

thanks,


Dariusz Suchojad

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


Thanks & Regards,
Nilesh Sutar.


Thanks & Regards,
Nilesh Sutar.