(Migrated) A few issues with fresh install with postgresql

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

Hi

I have been working through a clean install of 2.0.0 with postgresql as the
ODB.

I created the instance using

zato quickstart create --odb_host localhost --odb_port 5432 --odb_user
zato1 --odb_password zato1 --odb_db_name zato1 --store-config --store-log
–verbose --cluster_name insphire01 /opt/zato/instances/insphire postgresql
localhost 6379

Options saved in file /opt/zato/zato.2015_02_04_00_07_18_403887.config

Key/value database password (will not be echoed):

Enter the kvdb_password again (will not be echoed):

[1/8] Certificate authority created

[2/8] ODB schema already exists

[3/8] ODB initial data created

[4/8] server1 created

[5/8] server2 created

[6/8] Load-balancer created

Superuser created successfully.

[7/8] Web admin created

[8/8] Management scripts created

Quickstart cluster insphire01 created

Web admin user:[admin], password:[onom-agad-enot-orto]

Start the cluster by issuing the
/opt/zato/instances/insphire/zato-qs-start.sh command

Visit https://zato.io/support for more information and support options

Error in atexit._run_exitfuncs:

Traceback (most recent call last):

File “/usr/lib/python2.7/atexit.py”, line 24, in _run_exitfuncs

func(*targs, **kargs)

File “/usr/lib/python2.7/logging/init.py”, line 1654, in shutdown

h.close()

File “/usr/lib/python2.7/logging/init.py”, line 918, in close

StreamHandler.close(self)

TypeError: unbound method close() must be called with StreamHandler
instance as first argument (got FileHandler instance instead)

Error in sys.exitfunc:

Traceback (most recent call last):

File “/usr/lib/python2.7/atexit.py”, line 24, in _run_exitfuncs

func(*targs, **kargs)

File “/usr/lib/python2.7/logging/init.py”, line 1654, in shutdown

h.close()

File “/usr/lib/python2.7/logging/init.py”, line 918, in close

StreamHandler.close(self)
TypeError: unbound method close() must be called with StreamHandler
instance as first argument (got FileHandler instance instead)

The service still runs however in the web admin interface in clusters it
does mention -

insphire01

Created by zato@peresb01 on 2015-02-04T00:07:37.366300 (UTC)

Could not fetch the load balancer’s configuration

And lastly if I try to run zato check-config I get

zato@peresb01:~$ zato check-config /opt/zato/instances/insphire/
Directory /opt/zato/instances/insphire doesn’t seem to belong to a Zato
component. Expected one of the following files to exist [’.zato-info’]

My guess is the .zato-info creation is the last step and it failed with the
error above.

Any thoughts

Cheers
Tim

On 04/02/15 01:27, Tim Hoffmn wrote:

I have been working through a clean install of 2.0.0 with postgresql as
the ODB.

Hi Tim,

what operating system/architecture is it on?

Here it is on Ubuntu 14.04 64-bit. Would like to reproduce it - does the
atexit error manifest each time? This looks like something coming from
Python itself hence I’d like to reproduce it locally.

$ rm -rf ~/env/qs-1 && mkdir ~/env/qs-1 && cd ~/env/qs-1 &&
zato quickstart create ~/env/qs-1 postgresql localhost 6379
–odb_password zato1
–verbose --odb_host localhost --odb_port 5432 --odb_user zato1
–odb_db_name zato1 --odb_password zato1 --kvdb_password ‘’
[1/8] Certificate authority created
[2/8] ODB schema created
[3/8] ODB initial data created
[4/8] server1 created
[5/8] server2 created
[6/8] Load-balancer created
Superuser created successfully.
[7/8] Web admin created
[8/8] Management scripts created
Quickstart cluster quickstart-200709 created
Web admin user:[admin], password:[omom-okam-ehco-yeto]
Start the cluster by issuing the /home/dsuch/env/qs-1/zato-qs-start.sh
command
Visit https://zato.io/support for more information and support options
$

~/env/qs-1$ zato check-config server1
SQL ODB connection OK
Redis connection OK
~/env/qs-1$

thanks,

Hi Dariusz

Yes it’s Ubuntu 14.04 64-bit.

I had performed an upgrade earlier which was problematic, so then I apt-get
remove zato
and then installed apt-get install zato.

I wonder if anything was left lying around that could have caused the
problem.

Is there any way of recreating the .zato-info

Everything is working fine except for running things like check config and
running the server in fg becuase there is no .zato-info

T

On 4 February 2015 at 15:41, Dariusz Suchojad dsuch@zato.io wrote:

On 04/02/15 01:27, Tim Hoffmn wrote:

I have been working through a clean install of 2.0.0 with postgresql as
the ODB.

Hi Tim,

what operating system/architecture is it on?

Here it is on Ubuntu 14.04 64-bit. Would like to reproduce it - does the
atexit error manifest each time? This looks like something coming from
Python itself hence I’d like to reproduce it locally.

$ rm -rf ~/env/qs-1 && mkdir ~/env/qs-1 && cd ~/env/qs-1 &&
zato quickstart create ~/env/qs-1 postgresql localhost 6379
–odb_password zato1
–verbose --odb_host localhost --odb_port 5432 --odb_user zato1
–odb_db_name zato1 --odb_password zato1 --kvdb_password ‘’
[1/8] Certificate authority created
[2/8] ODB schema created
[3/8] ODB initial data created
[4/8] server1 created
[5/8] server2 created
[6/8] Load-balancer created
Superuser created successfully.
[7/8] Web admin created
[8/8] Management scripts created
Quickstart cluster quickstart-200709 created
Web admin user:[admin], password:[omom-okam-ehco-yeto]
Start the cluster by issuing the /home/dsuch/env/qs-1/zato-qs-start.sh
command
Visit https://zato.io/support for more information and support options
$

~/env/qs-1$ zato check-config server1
SQL ODB connection OK
Redis connection OK
~/env/qs-1$

thanks,


Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and cloud integrations in Python

Thanks for that.

I had tried the upgrade, but had a few problems

So I apt removed zato, then deleted everything in /opt/zato and then did an
install zato so I assumed that was clean enough :wink:

Cheers

Tim

On 4 February 2015 at 19:19, Dariusz Suchojad dsuch@zato.io wrote:

On 04/02/15 12:02, Tim Hoffman wrote:

Is there any way of recreating the .zato-info

Please place the JSON below in each server’s top-level directory so
there is, for instance:

$ cat /opt/zato/instances/insphire/server1/.zato-info

{“created_user_host”: “user@hostname”, “version”: “Zato
2.0.0.rev-55e0ec28”, “component”: “SERVER”, “created_ts”:
“2015-02-04T08:36:40.891344”}

Obviously - created_user_host and created_ts need to be updated.

The fact that you were upgrading from pre1 to stable most likely is the
reason - only stable releases get proper migration testing from our end
and are guaranteed to work according to the documentation:

https://zato.io/docs/admin/guide/migrate/overview.html

The good news is that from now on Zato releases won’t be that far off in
time and all the accumulated features will be available more frequently.

thanks again,


Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and cloud integrations in Python