./zato-qs-start.sh error

Community support
#1

I have installed zato(3.0) on debian 6.0.6,when I run ./zato-qs-start.sh,I get error messages as below:

[2/6] SQL ODB connection OK
No handlers could be found for logger "zato.common.haproxy"
Traceback (most recent call last):
File “/home/debian/install/zato/code/bin/zato”, line 183, in
sys.exit(zato.cli.zato_command.main())
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/zato_command.py”, line 261, in main
return run_command(get_parser().parse_args())
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 265, in run_command
command_classargs.command.run(args)
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 485, in run
return_code = self.execute(args)
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 717, in execute
return self._get_dispatch()json_data[‘component’]
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/start.py”, line 121, in _on_lb
self.run_check_config()
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/start.py”, line 64, in run_check_config
cc.execute(Bunch(path=’.’, ensure_no_pidfile=True, check_server_port_available=True))
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 717, in execute
return self._get_dispatch()json_data[‘component’]
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/check_config.py”, line 163, in _on_lb
validate_haproxy_config(lb_conf_string, lba_conf[‘haproxy_command’])
File “/home/debian/install/zato/code/zato-common/src/zato/common/haproxy.py”, line 160, in validate_haproxy_config
raise Exception(msg)
Exception: Caught an exception, e:`Traceback (most recent call last):
File “/home/debian/install/zato/code/zato-common/src/zato/common/haproxy.py”, line 155, in validate_haproxy_config
timeouting_popen(command, HAPROXY_VALIDATE_TIMEOUT, timeout_msg, rc_non_zero_msg, common_msg)
File “/home/debian/install/zato/code/zato-common/src/zato/common/util.py”, line 1522, in timeouting_popen
p = Popen(command, stdout=PIPE, stderr=PIPE)
File “/usr/local/lib/python2.7/subprocess.py”, line 710, in init
errread, errwrite)
File “/usr/local/lib/python2.7/subprocess.py”, line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

what’s the matter?

#2

Can you run the ‘tree’ command in the directory that all the components were installed to and show the output?

$ tree /path/to/quickstart/components

#3

root@debian:/home/debian/install/zato/zatodemo1# tree
.
├── ca
│ ├── ca-material
│ │ ├── ca-certindex
│ │ ├── ca-certindex.attr
│ │ ├── ca-certindex.attr.old
│ │ ├── ca-certindex.old
│ │ ├── ca-cert.pem
│ │ ├── ca-key.pem
│ │ ├── ca-password
│ │ ├── ca-serial
│ │ ├── ca-serial.old
│ │ └── openssl-template.conf
│ ├── out-cert
│ │ ├── lb-agent-cert-2016-10-26_04-29-45.pem
│ │ ├── quickstart-862108-scheduler1-cert-2016-10-26_04-30-02.pem
│ │ ├── quickstart-862108-server1-cert-2016-10-26_04-30-06.pem
│ │ ├── quickstart-862108-server2-cert-2016-10-26_04-30-13.pem
│ │ └── web-admin-cert-2016-10-26_04-29-53.pem
│ ├── out-csr
│ │ ├── lb-agent-csr-2016-10-26_04-29-45.pem
│ │ ├── quickstart-862108-scheduler1-csr-2016-10-26_04-30-02.pem
│ │ ├── quickstart-862108-server1-csr-2016-10-26_04-30-06.pem
│ │ ├── quickstart-862108-server2-csr-2016-10-26_04-30-13.pem
│ │ └── web-admin-csr-2016-10-26_04-29-53.pem
│ ├── out-priv
│ │ ├── lb-agent-priv-2016-10-26_04-29-45.pem
│ │ ├── quickstart-862108-scheduler1-priv-2016-10-26_04-30-02.pem
│ │ ├── quickstart-862108-server1-priv-2016-10-26_04-30-06.pem
│ │ ├── quickstart-862108-server2-priv-2016-10-26_04-30-13.pem
│ │ └── web-admin-priv-2016-10-26_04-29-53.pem
│ └── out-pub
│ ├── lb-agent-pub-2016-10-26_04-29-45.pem
│ ├── quickstart-862108-scheduler1-pub-2016-10-26_04-30-02.pem
│ ├── quickstart-862108-server1-pub-2016-10-26_04-30-06.pem
│ ├── quickstart-862108-server2-pub-2016-10-26_04-30-13.pem
│ └── web-admin-pub-2016-10-26_04-29-53.pem
├── load-balancer
│ ├── config
│ │ └── repo
│ │ ├── 503.http
│ │ ├── lb-agent.conf
│ │ ├── logging.conf
│ │ ├── zato.config
│ │ ├── zato-lba-ca-certs.pem
│ │ ├── zato-lba-cert.pem
│ │ ├── zato-lba-priv-key.pem
│ │ └── zato-lba-pub-key.pem
│ └── logs
│ ├── admin.lock
│ ├── admin.log
│ ├── connector.lock
│ ├── connector.log
│ ├── http_access.lock
│ ├── http_access.log
│ ├── kvdb.lock
│ ├── kvdb.log
│ ├── lb-agent.lock
│ ├── lb-agent.log
│ ├── pubsub.lock
│ ├── pubsub.log
│ ├── pubsub-overflown.lock
│ ├── pubsub-overflown.log
│ ├── rbac.lock
│ ├── rbac.log
│ ├── scheduler.lock
│ ├── scheduler.log
│ ├── web_socket.lock
│ └── web_socket.log
├── scheduler
│ ├── config
│ │ └── repo
│ │ ├── logging.conf
│ │ ├── scheduler.conf
│ │ ├── startup_jobs.conf
│ │ ├── zato-scheduler-ca-certs.pem
│ │ ├── zato-scheduler-cert.pem
│ │ ├── zato-scheduler-priv-key.pem
│ │ └── zato-scheduler-pub-key.pem
│ └── logs
│ ├── admin.lock
│ ├── admin.log
│ ├── connector.lock
│ ├── connector.log
│ ├── http_access.lock
│ ├── http_access.log
│ ├── kvdb.lock
│ ├── kvdb.log
│ ├── pubsub.lock
│ ├── pubsub.log
│ ├── pubsub-overflown.lock
│ ├── pubsub-overflown.log
│ ├── rbac.lock
│ ├── rbac.log
│ ├── scheduler.lock
│ ├── scheduler.log
│ ├── web_socket.lock
│ └── web_socket.log
├── server1
│ ├── config
│ │ └── repo
│ │ ├── logging.conf
│ │ ├── lua
│ │ │ ├── internal
│ │ │ │ └── zato.rename_if_exists.lua
│ │ │ └── user
│ │ ├── pickup.conf
│ │ ├── server.conf
│ │ ├── service-sources.txt
│ │ ├── static
│ │ ├── tls
│ │ │ ├── ca-certs
│ │ │ └── keys-certs
│ │ ├── user-conf
│ │ ├── user.conf
│ │ ├── zato-server-ca-certs.pem
│ │ ├── zato-server-cert.pem
│ │ ├── zato-server-priv-key.pem
│ │ └── zato-server-pub-key.pem
│ ├── logs
│ │ ├── admin.lock
│ │ ├── admin.log
│ │ ├── connector.lock
│ │ ├── connector.log
│ │ ├── http_access.lock
│ │ ├── http_access.log
│ │ ├── kvdb.lock
│ │ ├── kvdb.log
│ │ ├── pubsub.lock
│ │ ├── pubsub.log
│ │ ├── pubsub-overflown.lock
│ │ ├── pubsub-overflown.log
│ │ ├── rbac.lock
│ │ ├── rbac.log
│ │ ├── scheduler.lock
│ │ ├── scheduler.log
│ │ ├── server.lock
│ │ ├── server.log
│ │ ├── web_socket.lock
│ │ └── web_socket.log
│ ├── pickup
│ │ ├── incoming
│ │ │ ├── csv
│ │ │ ├── json
│ │ │ ├── services
│ │ │ ├── static
│ │ │ └── xml
│ │ └── processed
│ │ ├── csv
│ │ ├── json
│ │ ├── static
│ │ └── xml
│ ├── profiler
│ └── work
│ └── hot-deploy
│ ├── backup
│ │ └── last
│ └── current
├── server2
│ ├── config
│ │ └── repo
│ │ ├── logging.conf
│ │ ├── lua
│ │ │ ├── internal
│ │ │ │ └── zato.rename_if_exists.lua
│ │ │ └── user
│ │ ├── pickup.conf
│ │ ├── server.conf
│ │ ├── service-sources.txt
│ │ ├── static
│ │ ├── tls
│ │ │ ├── ca-certs
│ │ │ └── keys-certs
│ │ ├── user-conf
│ │ ├── user.conf
│ │ ├── zato-server-ca-certs.pem
│ │ ├── zato-server-cert.pem
│ │ ├── zato-server-priv-key.pem
│ │ └── zato-server-pub-key.pem
│ ├── logs
│ │ ├── admin.lock
│ │ ├── admin.log
│ │ ├── connector.lock
│ │ ├── connector.log
│ │ ├── http_access.lock
│ │ ├── http_access.log
│ │ ├── kvdb.lock
│ │ ├── kvdb.log
│ │ ├── pubsub.lock
│ │ ├── pubsub.log
│ │ ├── pubsub-overflown.lock
│ │ ├── pubsub-overflown.log
│ │ ├── rbac.lock
│ │ ├── rbac.log
│ │ ├── scheduler.lock
│ │ ├── scheduler.log
│ │ ├── server.lock
│ │ ├── server.log
│ │ ├── web_socket.lock
│ │ └── web_socket.log
│ ├── pickup
│ │ ├── incoming
│ │ │ ├── csv
│ │ │ ├── json
│ │ │ ├── services
│ │ │ ├── static
│ │ │ └── xml
│ │ └── processed
│ │ ├── csv
│ │ ├── json
│ │ ├── static
│ │ └── xml
│ ├── profiler
│ └── work
│ └── hot-deploy
│ ├── backup
│ │ └── last
│ └── current
├── web-admin
│ ├── config
│ │ └── repo
│ │ ├── initial-data.json
│ │ ├── logging.conf
│ │ ├── web-admin-ca-certs.pem
│ │ ├── web-admin-cert.pem
│ │ ├── web-admin.conf
│ │ ├── web-admin-priv-key.pem
│ │ └── web-admin-pub-key.pem
│ └── logs
├── zato-qs-restart.sh
├── zato-qs-start.sh
└── zato-qs-stop.sh

#5

root@debian:/home/debian/install/zato/zatodemo1# …/code/bin/zato --version
Zato 3.0.0pre1.rev-

root@debian:/home/debian/install/zato/zatodemo1# …/code/bin/zato start load-balancer
No handlers could be found for logger "zato.common.haproxy"
Traceback (most recent call last):
File “…/code/bin/zato”, line 183, in
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/zato_command.py”, line 261, in main
return run_command(get_parser().parse_args())
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 265, in run_command
command_classargs.command.run(args)
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 485, in run
return_code = self.execute(args)
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 717, in execute
return self._get_dispatch()json_data[‘component’]
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/start.py”, line 121, in _on_lb
self.run_check_config()
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/start.py”, line 64, in run_check_config
cc.execute(Bunch(path=’.’, ensure_no_pidfile=True, check_server_port_available=True))
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/init.py”, line 717, in execute
return self._get_dispatch()json_data[‘component’]
File “/home/debian/install/zato/code/zato-cli/src/zato/cli/check_config.py”, line 163, in _on_lb
validate_haproxy_config(lb_conf_string, lba_conf[‘haproxy_command’])
File “/home/debian/install/zato/code/zato-common/src/zato/common/haproxy.py”, line 160, in validate_haproxy_config
raise Exception(msg)
Exception: Caught an exception, e:`Traceback (most recent call last):
File “/home/debian/install/zato/code/zato-common/src/zato/common/haproxy.py”, line 155, in validate_haproxy_config
timeouting_popen(command, HAPROXY_VALIDATE_TIMEOUT, timeout_msg, rc_non_zero_msg, common_msg)
File “/home/debian/install/zato/code/zato-common/src/zato/common/util.py”, line 1522, in timeouting_popen
p = Popen(command, stdout=PIPE, stderr=PIPE)
File “/usr/local/lib/python2.7/subprocess.py”, line 710, in init
errread, errwrite)
File “/usr/local/lib/python2.7/subprocess.py”, line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

#6

if I skip load-balancer in the start shell,other is OK.web admin can login(need modify password in database).

If I should try 2.0.7?

#7

1.modify code ,zato/common/haproxy.py
#timeouting_popen(command, HAPROXY_VALIDATE_TIMEOUT, timeout_msg, rc_non_zero_msg, common_msg)

root@debian:/home/debian/install/zato/zatodemo1# ./zato-qs-start.sh
Starting Zato cluster quickstart-862108
Running sanity checks
[1/6] Redis connection OK
[2/6] SQL ODB connection OK
No handlers could be found for logger “zato.common.haproxy”
[3/6] Load-balancer started
[4/6] server1 started
[5/6] server2 started
[5/6] Scheduler started
[6/6] Web admin started
Zato cluster quickstart-862108 started
Visit https://zato.io/support for more information and support options

  1. curl localhost:11223/zato/ping ; echo
    curl: (7) couldn’t connect to host

4.http://localhost:8183/zato/ can login,but

Traceback (most recent call last): File “/home/debian/install/zato/code/zato-web-admin/src/zato/admin/web/views/init.py”, line 338, in call response = self.invoke_admin_service() File “/home/debian/install/zato/code/zato-web-admin/src/zato/admin/web/views/init.py”, line 299, in invoke_admin_service return func(self.service_name, self.input) File “/home/debian/install/zato/code/zato-web-admin/src/zato/admin/middleware.py”, line 75, in invoke response = super(Client, self).invoke(*args, headers={‘X-Zato-Forwarded-For’: self.forwarded_for}, **kwargs) File “/home/debian/install/zato/code/zato-client/src/zato/client/init.py”, line 405, in invoke return self._invoke(async=False, *args, **kwargs) File “/home/debian/install/zato/code/zato-client/src/zato/client/init.py”, line 402, in _invoke return super(AnyServiceInvoker, self).invoke(dumps(request), ServiceInvokeResponse, async, headers, output_repeated) File “/home/debian/install/zato/code/zato-client/src/zato/client/init.py”, line 339, in invoke return self.inner_invoke(request, response_class, async, headers) File “/home/debian/install/zato/code/zato-client/src/zato/client/init.py”, line 324, in inner_invoke raw_response = self.session.post(self.service_address, request, headers=headers, verify=self.tls_verify) File “/home/debian/install/zato/code/eggs/requests-2.7.0-py2.7.egg/requests/sessions.py”, line 508, in post return self.request(‘POST’, url, data=data, json=json, **kwargs) File “/home/debian/install/zato/code/eggs/requests-2.7.0-py2.7.egg/requests/sessions.py”, line 465, in request resp = self.send(prep, **send_kwargs) File “/home/debian/install/zato/code/eggs/requests-2.7.0-py2.7.egg/requests/sessions.py”, line 576, in send r = adapter.send(request, **kwargs) File “/home/debian/install/zato/code/eggs/requests-2.7.0-py2.7.egg/requests/adapters.py”, line 415, in send raise ConnectionError(err, request=request) ConnectionError: (‘Connection aborted.’, error(111, ‘Connection refused’))

5.netstat -a|grep 11223

#8

It is done.
nead install haproxy:
apt-get install haproxy

curl localhost:11223/zato/ping ; echo
{“zato_env”:
{“details”: “No server is available to handle the request”,
“result”: “ZATO_ERROR”,
“cid”: “K012345678901234567890123456”}
}

thanks

#9

new issue.

when run in web-admin,get the errors as below:

Traceback (most recent call last): File “/home/debian/install/zato/code/zato-web-admin/src/zato/admin/web/views/init.py”, line 338, in call response = self.invoke_admin_service() File “/home/debian/install/zato/code/zato-web-admin/src/zato/admin/web/views/init.py”, line 299, in invoke_admin_service return func(self.service_name, self.input) File “/home/debian/install/zato/code/zato-web-admin/src/zato/admin/middleware.py”, line 78, in invoke raise Exception(‘CID: {}\nDetails: {}’.format(zato_env.get(‘cid’), zato_env.get(‘details’))) Exception: CID: K012345678901234567890123456 Details: No server is available to handle the request

#10

It’s OK.

root@debian:/home/debian/install/zato/zatodemo1/server2# curl localhost:11223/zato/ping ; echo
{“zato_env”: {“details”: “”, “result”: “ZATO_OK”, “cid”: “4d4c5cf8bd1811cc18fc699b”}, “zato_ping_response”: {“pong”: “zato”}}

the reason is the server error,I don’t install scipy in my Python virtualenv.

#11

I write a service follow the https://zato.io/docs/tutorial/01.html and upload the service file,in the server log can see the information:
2016-10-27 17:39:31,186 - ^[[1;37mINFO^[[0m - 24799:DummyThread-143 - zato.hot-deploy.create:376 - Creating tar archive
2016-10-27 17:39:31,513 - ^[[1;37mINFO^[[0m - 24799:DummyThread-143 - zato.hot-deploy.create:161 - Uploaded package id:[757], payload_name:[my_service.py]

but,I can’t search the service in the web-admin’s ClustersServices->List Service page.

what’s the matter?

#12

Hello,

if you are installing Zato from source code, please follow instructions from this page and do not install or run Zato as root - there is no need to and it is discouraged to run Zato as root:

https://zato.io/docs/admin/guide/install/source.html

Otherwise, if you don’t use these instructions you may hit upon issues that we will not be able to reproduce and help you out with.

Please use the instructions above first, install Zato as a user with sudo powers going through the steps above.

#13

dsuch

Hello,

I reinstalled Zato from source code using not root user,Zato is runing normally Now.
thank you very much！