(Migrated) Zato on an Amazon Linux AMI-based EC2

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

Hi,

Has anyone managed to successfully install zato on this type of EC2?

I followed the instructions at
https://zato.io/docs/admin/guide/install-rhel.html, but the install fails
because of some odd pkg =8Ctix=B9. Googling zato and tix shows nothing.

Following is the output of a yum install zato. I tried '–skip-broken=B9 and
’rpm -Va --nofiles =8Bno digest=B9 ; but the failure persists

Any help would be very much appreciated.

Thanks!

Loaded plugins: priorities, update-motd, upgrade-helper

Resolving Dependencies

–> Running transaction check

—> Package zato.x86_64 0:1.1-1.el6 will be installed

–> Processing Dependency: uuid for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: tix for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: suitesparse for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: scipy for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: postgresql-libs for package:
zato-1.1-1.el6.x86_64

–> Processing Dependency: numpy for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: m2crypto for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: libevent for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: lapack for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: haproxy for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: bzr for package: zato-1.1-1.el6.x86_64

–> Processing Dependency: atlas for package: zato-1.1-1.el6.x86_64

–> Running transaction check

—> Package atlas.x86_64 0:3.8.4-2.6.amzn1 will be installed

—> Package bzr.x86_64 0:2.1.2-2.9.amzn1 will be installed

—> Package haproxy.x86_64 0:1.4.22-5.3.amzn1 will be installed

—> Package lapack.x86_64 0:3.5.0-8.6.amzn1 will be installed

–> Processing Dependency: libblas.so.3()(64bit) for package:
lapack-3.5.0-8.6.amzn1.x86_64

—> Package libevent.x86_64 0:2.0.18-1.10.amzn1 will be installed

—> Package m2crypto.x86_64 0:0.20.2-9.10.amzn1 will be installed

—> Package numpy.x86_64 1:1.7.2-8.10.amzn1 will be installed

–> Processing Dependency: python-nose for package:
1:numpy-1.7.2-8.10.amzn1.x86_64

—> Package postgresql92-libs.x86_64 0:9.2.9-1.46.amzn1 will be installed

—> Package scipy.x86_64 0:0.12.1-1.7.amzn1 will be installed

–> Processing Dependency: f2py for package: scipy-0.12.1-1.7.amzn1.x86_64

—> Package suitesparse.x86_64 0:3.6.1-4.1.amzn1 will be installed

–> Processing Dependency: libtbb.so.2()(64bit) for package:
suitesparse-3.6.1-4.1.amzn1.x86_64

–> Processing Dependency: libtbbmalloc.so.2()(64bit) for package:
suitesparse-3.6.1-4.1.amzn1.x86_64

—> Package uuid.x86_64 0:1.6.2-27.22.amzn1 will be installed

—> Package zato.x86_64 0:1.1-1.el6 will be installed

–> Processing Dependency: tix for package: zato-1.1-1.el6.x86_64

–> Running transaction check

—> Package blas.x86_64 0:3.5.0-8.6.amzn1 will be installed

—> Package numpy-f2py.x86_64 1:1.7.2-8.10.amzn1 will be installed

–> Processing Dependency: python-devel for package:
1:numpy-f2py-1.7.2-8.10.amzn1.x86_64

—> Package python-nose.noarch 0:1.3.0-1.6.amzn1 will be installed

—> Package tbb.x86_64 0:2.2-3.20090809.2.amzn1 will be installed

—> Package zato.x86_64 0:1.1-1.el6 will be installed

–> Processing Dependency: tix for package: zato-1.1-1.el6.x86_64

–> Running transaction check

—> Package python-devel.noarch 1:2.6-2.26.amzn1 will be installed

–> Processing Dependency: python-devel-abi =3D 2.6 for package:
1:python-devel-2.6-2.26.amzn1.noarch

—> Package zato.x86_64 0:1.1-1.el6 will be installed

–> Processing Dependency: tix for package: zato-1.1-1.el6.x86_64

–> Running transaction check

—> Package python26-devel.x86_64 0:2.6.9-1.55.amzn1 will be installed

—> Package zato.x86_64 0:1.1-1.el6 will be installed

–> Processing Dependency: tix for package: zato-1.1-1.el6.x86_64

–> Finished Dependency Resolution

Error: Package: zato-1.1-1.el6.x86_64 (zato-stable)

       Requires: tix

You could try using --skip-broken to work around the problem

You could try running: rpm -Va --nofiles --nodigest

Hi Darius (and Everyone),

I opted to switch away from Amazon Linux AMI and used an Ububtu 14.04 LTS
server instead.

Installation, as documented on the web page, worked like a charm. Thanks
for your advice :slight_smile:

-Nancy

From: Dariusz Suchojad dsuch@zato.io
Date: Friday, October 24, 2014 at 1:58 AM
To: Nancy Zayed nancy@magic3inc.com, zato-discuss@lists.zato.io
Subject: Re: [Zato-discuss] Zato on an Amazon Linux AMI-based EC2

On 24/10/14 06:52, Nancy Zayed wrote:

Has anyone managed to successfully install zato on this type of EC2?
=20
I followed the instructions
at https://zato.io/docs/admin/guide/install-rhel.html, but the install
fails because of some odd pkg =8Ctix=B9. Googling zato and tix shows nothin=
g.
=20
Following is the output of a yum install zato. I tried '–skip-broken=B9
and 'rpm -Va --nofiles =8Bno digest=B9 ; but the failure persists
=20
Any help would be very much appreciated.

Hi Nancy,

a colleague of mine and me recently installed a development version of
Zato built from GitHub master on an AMI el6 x86_64.

Having never worked with AMI before I was quite surprised to see that
there were a few differences between this system and CentOS.

I’ve just checked it in bash history and tix had to be downloaded and
installed manually

$ wget
ftp://ftp.es.kde.org/sites/centos.org/6/os/x86_64/Packages/tix-8.4.3-5.el6.=
x
86_64.rpm

$ sudo yum install sudo yum install tix-8.4.3-5.el6.x86_64.rpm

The environment now works fine but I’m not sure about the details
because I wasn’t involved in all the works.

Until there are dedicated packages for AMI I would recommend running
Ubuntu on EC2 which is the actual Ubuntu and is guaranteed to work as
expected - Zato including.

On 24/10/14 06:52, Nancy Zayed wrote:

Has anyone managed to successfully install zato on this type of EC2?

I followed the instructions
at https://zato.io/docs/admin/guide/install-rhel.html, but the install
fails because of some odd pkg ‘tix’. Googling zato and tix shows nothing.

Following is the output of a yum install zato. I tried '–skip-broken’
and 'rpm -Va --nofiles —no digest’ ; but the failure persists

Any help would be very much appreciated.

Hi Nancy,

a colleague of mine and me recently installed a development version of
Zato built from GitHub master on an AMI el6 x86_64.

Having never worked with AMI before I was quite surprised to see that
there were a few differences between this system and CentOS.

I’ve just checked it in bash history and tix had to be downloaded and
installed manually

$ wget
ftp://ftp.es.kde.org/sites/centos.org/6/os/x86_64/Packages/tix-8.4.3-5.el6.x86_64.rpm

$ sudo yum install sudo yum install tix-8.4.3-5.el6.x86_64.rpm

The environment now works fine but I’m not sure about the details
because I wasn’t involved in all the works.

Until there are dedicated packages for AMI I would recommend running
Ubuntu on EC2 which is the actual Ubuntu and is guaranteed to work as
expected - Zato including.

On 24/10/14 06:52, Nancy Zayed wrote:

Has anyone managed to successfully install zato on this type of EC2?

I followed the instructions
at https://zato.io/docs/admin/guide/install-rhel.html, but the install
fails because of some odd pkg ‘tix’. Googling zato and tix shows nothing.

Following is the output of a yum install zato. I tried '–skip-broken’
and 'rpm -Va --nofiles —no digest’ ; but the failure persists

Any help would be very much appreciated.

Hi Nancy,

a colleague of mine and me recently installed a development version of
Zato built from GitHub master on an AMI el6 x86_64.

Having never worked with AMI before I was quite surprised to see that
there were a few differences between this system and CentOS.

I’ve just checked it in bash history and tix had to be downloaded and
installed manually

$ wget
ftp://ftp.es.kde.org/sites/centos.org/6/os/x86_64/Packages/tix-8.4.3-5.el6.x86_64.rpm

$ sudo yum install sudo yum install tix-8.4.3-5.el6.x86_64.rpm

The environment now works fine but I’m not sure about the details
because I wasn’t involved in all the works.

Until there are dedicated packages for AMI I would recommend running
Ubuntu on EC2 which is the actual Ubuntu and is guaranteed to work as
expected - Zato including.