We’ve been having problems for a few days now. We have Zato deployed on a Ubuntu 18.04.2 LTS server, and it has almost always worked without problems. However, recently we had to restart the server, and by doing so Zato has stopped working. When starting it, it runs until step 6/7 without problem, that is, the scheduler, but after that, we get the following message:
Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/opt/zato/3.0/code/zato-scheduler/src/zato/scheduler/main.py", line 77, in <module> main() File "/opt/zato/3.0/code/zato-scheduler/src/zato/scheduler/main.py", line 47, in main dictConfig(yaml.load(f)) File "/usr/lib/python2.7/logging/config.py", line 794, in dictConfig dictConfigClass(config).configure() File "/usr/lib/python2.7/logging/config.py", line 576, in configure '%r: %s' % (name, e)) ValueError: Unable to configure handler 'default': [Errno 13] Permission denied: '/opt/zato/env/SP2-0/scheduler/logs/server.log
We believe this is because, although it seems to start servers 1 and 2, these are not active (they appear as DOWN on the web-admin) and therefore we cannot use the services or access the list of services.
We have tried to start the servers individually with zato start /opt/zato/env/SP2-0/server1, and although it appears OK it does not seem to be running, because if we use zato stop /opt/zato/env/SP2-0/server2, the following message appears: OSError: (3, ‘No such process’) (Hint: re-run with --verbose for full traceback).
Sometimes when starting Zato it does not complete the 7 steps, but it appears an error in step 4, appearing the following message:
[4/7] server1 started
No handlers could be found for logger “zato.common.util.proc”
If you knew why it could be happening we would appreciate it, we are a little desperate