(Migrated) No server is available error

Community support
#1

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

Hello All,

I was allowing the Zato tutorial and created the cluster and started the
cluster. But it keeps giving me either Server TimeOut or No Server is
available to handle the request.

PFB the server log. Much Thanks for any help.

Regards,
Sharad

2015-05-11 14:58:55,328 - ^[[1;37mINFO^[[0m - 8510:MainThread -
zato.common.repo:22 - Location [/opt/zato/dev_dir/server1/config/repo] is
not a Bazaar branch. Will turn it into one.
2015-05-11 14:58:55,986 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Starting gunicorn 18.0
2015-05-11 14:58:55,998 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Listening at: http://127.0.0.1:17010 (8510)
2015-05-11 14:58:55,998 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Using worker: gevent
2015-05-11 14:58:56,014 - ^[[1;37mINFO^[[0m - 8526:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8526
2015-05-11 14:58:56,095 - ^[[1;37mINFO^[[0m - 8527:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8527
2015-05-11 15:02:56,304 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8526)
2015-05-11 15:02:56,306 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8527)
2015-05-11 15:02:56,325 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8526)
2015-05-11 15:02:56,326 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8527)
2015-05-11 15:02:56,327 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8526)
2015-05-11 15:02:56,331 - ^[[1;37mINFO^[[0m - 8681:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8681
2015-05-11 15:02:57,438 - ^[[1;37mINFO^[[0m - 8682:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8682
2015-05-11 15:04:35,736 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Handling signal: term
2015-05-11 15:05:05,911 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Shutting down: Master
2015-05-11 15:06:22,168 - ^[[1;37mINFO^[[0m - 8727:Dummy-1 -
gunicorn.main:22 - Starting gunicorn 18.0
2015-05-11 15:06:22,176 - ^[[1;37mINFO^[[0m - 8727:Dummy-1 -
gunicorn.main:22 - Listening at: http://127.0.0.1:17010 (8727)
2015-05-11 15:06:22,177 - ^[[1;37mINFO^[[0m - 8727:Dummy-1 -
gunicorn.main:22 - Using worker: gevent
2015-05-11 15:06:22,191 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8749
2015-05-11 15:06:22,235 - ^[[1;37mINFO^[[0m - 8750:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8750
2015-05-11 15:10:14,157 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.odb:22 - Server id:[1], name:[server1] is now a connector
server for cluster id:[1], name:[quickstart-489278]
2015-05-11 15:10:14,159 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - Initializing connectors
2015-05-11 15:10:14,171 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No AMQP channels to start
2015-05-11 15:10:14,182 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No AMQP outgoing connections to start
2015-05-11 15:10:14,381 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No JMS WebSphere MQ channels to start
2015-05-11 15:10:14,388 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No JMS WebSphere MQ outgoing connections to
start
2015-05-11 15:10:14,395 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No Zero MQ channels to start
2015-05-11 15:10:14,412 - ^[[1;37mINFO^[[0m - 8749:Dummy-3 -
zato.broker.client:22 - Starting broker client, host:[localhost],
port:[6379], name:[parallel-K07JYTFXT5P3N3A2MMK5PXHQQE3F],
topics:[[’/zato/to-parallel/all’, ‘/zato/to-parallel/any’,
’/zato/to-singleton’]]
2015-05-11 15:10:18,178 - ^[[1;37mINFO^[[0m - 8749:Dummy-9 -
zato.helpers.input-logger:784 - {u’impl_name’:
u’zato.server.service.internal.helpers.InputLogger’, u’name’:
u’zato.helpers.input-logger’, u’cid’: u’K067CTMD5W6XD76GPNHRW4MBZAHZ’,
u’invocation_time’: datetime.datetime(2015, 5, 11, 20, 10, 18, 176240),
u’job_type’: None, u’data_format’: None, u’slow_threshold’: 99999,
u’request.payload’: u’Sample payload for a startup service (first worker)’,
u’wsgi_environ’: {u’zato.request_ctx.async_msg’: Bunch(action=u’101802’,
channel=u’startup-service’, cid=u’K067CTMD5W6XD76GPNHRW4MBZAHZ’,
msg_type=u’0001’, payload=u’Sample payload for a startup service (first
worker)’, service=u’zato.helpers.input-logger’),
u’zato.request_ctx.fanout_cid’: None, u’zato.request_ctx.in_reply_to’:
None, u’zato.request_ctx.parallel_exec_cid’: None}, u’environ’: {},
u’usage’: 1, u’channel’: u’startup-service’}
2015-05-11 15:10:22,353 - ^[[1;33mCRITICAL^[[0m - 8727:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8750)
2015-05-11 15:10:22,401 - ^[[1;33mCRITICAL^[[0m - 8727:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8750)
2015-05-11 15:10:23,407 - ^[[1;37mINFO^[[0m - 8911:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8911
2015-05-11 15:13:25,661 - ^[[1;31mERROR^[[0m - 8911:Dummy-1 -
gunicorn.main:22 - Exception in worker process:
Traceback (most recent call last):
File “/opt/zato/2.0.3/eggs/gunicorn-18.0-py2.7.egg/gunicorn/arbiter.py”,
line 494, in spawn_worker

#2

On 11/05/15 22:45, Sharad Tanwar wrote:

I was allowing the Zato tutorial and created the cluster and started the
cluster. But it keeps giving me either Server TimeOut or No Server is
available to handle the request.

Hi Sharad,

if it’s a VirtualBox VM can you give it 1 GB RAM and try again?

thanks,

#3

Hello Dariusz,

Thank you for the suggestion. My zato installation on VirtualBox VM is
working fine. I have another VM outside of VirtualBox which has 4GB of RAM.
It gave me ZATO_OK once, but keeps giving me No Server available to handle
request error now. Is there any check to confirm if Zato is working or is
in idle state or something??

Thanks.

Regards,
Sharad Tanwar

On Mon, May 11, 2015 at 4:10 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 11/05/15 22:45, Sharad Tanwar wrote:

I was allowing the Zato tutorial and created the cluster and started the
cluster. But it keeps giving me either Server TimeOut or No Server is
available to handle the request.

Hi Sharad,

if it’s a VirtualBox VM can you give it 1 GB RAM and try again?

thanks,

–
Dariusz Suchojad

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

#4

Hello,
I had a similar problem when using sqlite as ODB, it was just too slow,
the workers took about 2 minutes to get up,
I solved the problem by using MySQL, now it takes 10 seconds, have you
tried that?

Andrea.

On 05/11/15 22:45, Sharad Tanwar wrote:

Hello All,

I was allowing the Zato tutorial and created the cluster and started
the cluster. But it keeps giving me either Server TimeOut or No Server
is available to handle the request.

PFB the server log. Much Thanks for any help.

Regards,
Sharad

2015-05-11 14:58:55,328 - ^[[1;37mINFO^[[0m - 8510:MainThread -
zato.common.repo:22 - Location [/opt/zato/dev_dir/server1/config/repo]
is not a Bazaar branch. Will turn it into one.
2015-05-11 14:58:55,986 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Starting gunicorn 18.0
2015-05-11 14:58:55,998 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Listening at: http://127.0.0.1:17010 (8510)
2015-05-11 14:58:55,998 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Using worker: gevent
2015-05-11 14:58:56,014 - ^[[1;37mINFO^[[0m - 8526:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8526
2015-05-11 14:58:56,095 - ^[[1;37mINFO^[[0m - 8527:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8527
2015-05-11 15:02:56,304 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8526)
2015-05-11 15:02:56,306 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8527)
2015-05-11 15:02:56,325 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8526)
2015-05-11 15:02:56,326 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8527)
2015-05-11 15:02:56,327 - ^[[1;33mCRITICAL^[[0m - 8510:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8526)
2015-05-11 15:02:56,331 - ^[[1;37mINFO^[[0m - 8681:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8681
2015-05-11 15:02:57,438 - ^[[1;37mINFO^[[0m - 8682:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8682
2015-05-11 15:04:35,736 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Handling signal: term
2015-05-11 15:05:05,911 - ^[[1;37mINFO^[[0m - 8510:Dummy-1 -
gunicorn.main:22 - Shutting down: Master
2015-05-11 15:06:22,168 - ^[[1;37mINFO^[[0m - 8727:Dummy-1 -
gunicorn.main:22 - Starting gunicorn 18.0
2015-05-11 15:06:22,176 - ^[[1;37mINFO^[[0m - 8727:Dummy-1 -
gunicorn.main:22 - Listening at: http://127.0.0.1:17010 (8727)
2015-05-11 15:06:22,177 - ^[[1;37mINFO^[[0m - 8727:Dummy-1 -
gunicorn.main:22 - Using worker: gevent
2015-05-11 15:06:22,191 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8749
2015-05-11 15:06:22,235 - ^[[1;37mINFO^[[0m - 8750:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8750
2015-05-11 15:10:14,157 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.odb:22 - Server id:[1], name:[server1] is now a connector
server for cluster id:[1], name:[quickstart-489278]
2015-05-11 15:10:14,159 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - Initializing connectors
2015-05-11 15:10:14,171 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No AMQP channels to start
2015-05-11 15:10:14,182 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No AMQP outgoing connections to start
2015-05-11 15:10:14,381 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No JMS WebSphere MQ channels to start
2015-05-11 15:10:14,388 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No JMS WebSphere MQ outgoing
connections to start
2015-05-11 15:10:14,395 - ^[[1;37mINFO^[[0m - 8749:Dummy-1 -
zato.server.base.parallel:22 - No Zero MQ channels to start
2015-05-11 15:10:14,412 - ^[[1;37mINFO^[[0m - 8749:Dummy-3 -
zato.broker.client:22 - Starting broker client, host:[localhost],
port:[6379], name:[parallel-K07JYTFXT5P3N3A2MMK5PXHQQE3F],
topics:[[’/zato/to-parallel/all’, ‘/zato/to-parallel/any’,
’/zato/to-singleton’]]
2015-05-11 15:10:18,178 - ^[[1;37mINFO^[[0m - 8749:Dummy-9 -
zato.helpers.input-logger:784 - {u’impl_name’:
u’zato.server.service.internal.helpers.InputLogger’, u’name’:
u’zato.helpers.input-logger’, u’cid’: u’K067CTMD5W6XD76GPNHRW4MBZAHZ’,
u’invocation_time’: datetime.datetime(2015, 5, 11, 20, 10, 18,
176240), u’job_type’: None, u’data_format’: None, u’slow_threshold’:
99999, u’request.payload’: u’Sample payload for a startup service
(first worker)’, u’wsgi_environ’: {u’zato.request_ctx.async_msg’:
Bunch(action=u’101802’, channel=u’startup-service’,
cid=u’K067CTMD5W6XD76GPNHRW4MBZAHZ’, msg_type=u’0001’,
payload=u’Sample payload for a startup service (first worker)’,
service=u’zato.helpers.input-logger’), u’zato.request_ctx.fanout_cid’:
None, u’zato.request_ctx.in_reply_to’: None,
u’zato.request_ctx.parallel_exec_cid’: None}, u’environ’: {},
u’usage’: 1, u’channel’: u’startup-service’}
2015-05-11 15:10:22,353 - ^[[1;33mCRITICAL^[[0m - 8727:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8750)
2015-05-11 15:10:22,401 - ^[[1;33mCRITICAL^[[0m - 8727:Dummy-1 -
gunicorn.main:204 - WORKER TIMEOUT (pid:8750)
2015-05-11 15:10:23,407 - ^[[1;37mINFO^[[0m - 8911:Dummy-1 -
gunicorn.main:22 - Booting worker with pid: 8911
2015-05-11 15:13:25,661 - ^[[1;31mERROR^[[0m - 8911:Dummy-1 -
gunicorn.main:22 - Exception in worker process:
Traceback (most recent call last):
File
"/opt/zato/2.0.3/eggs/gunicorn-18.0-py2.7.egg/gunicorn/arbiter.py",
line 494, in spawn_worker