[
https://issues.apache.org/jira/browse/BROOKLYN-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490664#comment-16490664
]
Aled Sage commented on BROOKLYN-589:
------------------------------------
Almost certainly unrelated, but worth mentioning in case... The stderr of the
install command in Brooklyn shows:
{noformat}
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for libgcc which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libgcc of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude libgcc.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libgcc installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of libgcc installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: libgcc-4.8.5-28.el7_5.1.i686 !=
libgcc-4.8.5-16.el7.x86_64
{noformat}
> MariaDB install fails on AWS: ftp.hosteurope.de very slow
> ---------------------------------------------------------
>
> Key: BROOKLYN-589
> URL: https://issues.apache.org/jira/browse/BROOKLYN-589
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.12.0
> Reporter: Aled Sage
> Priority: Major
>
> I tried to deploy MariaDB to the centos.org marketplace AMI in AWS
> (eu-central-1/ami-1e038d71).
> This uses the entity
> {{org.apache.brooklyn.entity.database.mariadb.MariaDbNode}}, via the test in
> https://github.com/brooklyncentral/brooklyn-mariadb-node/.
> However, the install ssh command didn't complete. It kept trying to {{curl}}
> the mariadb tar.gz from http://ftp.hosteurope.de, but was getting less than 1
> bytes/sec back.
> Logging into the VM and trying this manually, I saw:
> {noformat}
> curl -v -f -L -k --retry 10 --keepalive-time 30 --speed-time 30
> "http://ftp.hosteurope.de/mirror/archive.mariadb.org/mariadb-10.2.6/bintar-linux-x86_64/mariadb-10.2.6-linux-x86_64.tar.gz";
> -o mariadb-10.2.6-linux-x86_64.tar.gz
> % Total % Received % Xferd Average Speed Time Time Time
> Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
> 0* About to connect() to ftp.hosteurope.de port 80 (#0)
> * Trying 80.237.136.138...
> * Connected to ftp.hosteurope.de (80.237.136.138) port 80 (#0)
> > GET
> > /mirror/archive.mariadb.org/mariadb-10.2.6/bintar-linux-x86_64/mariadb-10.2.6-linux-x86_64.tar.gz
> > HTTP/1.1
> > User-Agent: curl/7.29.0
> > Host: ftp.hosteurope.de
> > Accept: */*
> >
> 0 0 0 0 0 0 0 0 --:--:-- 0:00:30 --:--:--
> 0* Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds
> 0 0 0 0 0 0 0 0 --:--:-- 0:00:30 --:--:-- 0
> * Closing connection 0
> Warning: Transient problem: timeout Will retry in 1 seconds. 10 retries left.
> * About to connect() to ftp.hosteurope.de port 80 (#1)
> * Trying 80.237.136.138...
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
> 0* Connected to ftp.hosteurope.de (80.237.136.138) port 80 (#1)
> > GET
> > /mirror/archive.mariadb.org/mariadb-10.2.6/bintar-linux-x86_64/mariadb-10.2.6-linux-x86_64.tar.gz
> > HTTP/1.1
> > User-Agent: curl/7.29.0
> > Host: ftp.hosteurope.de
> > Accept: */*
> >
> 0 0 0 0 0 0 0 0 --:--:-- 0:00:29 --:--:-- 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
