TECHZEN Zenoss User Community ARCHIVE  

unable to install Percona

Subject: unable to install Percona
Author: [Not Specified]
Posted: 2015-05-01 13:59

I've gotten zenoss up and running and everything seems to work, however when i try to install percona tools as recommended in the admin manual i get the following. i also get similar name resolution issues when modeling devices, running host forward/reverse, or attempting to install zenpacks.

------------------------------------------------------------------------------------------------------------------

linadmin@zenoss:~$ serviced service run zope install-percona
I0501 13:57:41.679721 02791 server.go:341] Connected to the control center at port 172.16.10.4:4979
I0501 13:57:41.752337 02791 server.go:435] Acquiring image from the dfs...
I0501 13:57:41.753428 02791 server.go:437] Acquired! Starting shell
Trying to connect to logstash server... 127.0.0.1:5042
Connected to logstash server.
Installing percona to /var/zenoss/percona
Downloading percona toolkit: http://www.percona.com/downloads/percona-toolkit/2.2.12/tarball/percona-...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0curl: (6) Could not resolve host: www.percona.com; Unknown error

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Error downloading percona!
Command returned non-zero exit code 1. Container not commited.



Subject: Try to setup your docker DNS
Author: Jan Garaj
Posted: 2015-05-01 15:13

Try to setup your docker DNS correctly in /etc/sysconfig/docker. You can to define multiple --dns parameters with different values there.

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: Forgive me for being the pest
Author: [Not Specified]
Posted: 2015-05-04 09:13

Forgive me for being the pest i am, but i'm not linux guru. reviewing the advanced IP configuration documentation the following is what i've got in /etc/default/docker. As I understand the parameters this should work, but still does not. i've tried restarting services and rebooting to no avail. any advice would be greatly appreciated. the 10.4.1.1 is the static ip i gave to the docker0 interface since the default overruns some of our internal networks. the 172.16.10.40 is one of our windows DNS servers. i can't access control center at all if i don't specify the docker interface as a dns server.

-----------------------------------------------------------
# Docker Upstart and SysVinit configuration file

# Customize location of Docker binary (especially for development testing).
#DOCKER="/usr/local/bin/docker"

# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS="--bip=10.4.1.1/24 --dns=172.16.1.40 --dns=10.4.1.1 --ip-forward=true"

# If you need Docker to use an HTTP proxy, it can also be specified here.
#export http_proxy="http://127.0.0.1:3128/"

# This is also a handy place to tweak where Docker's temporary files go.
#export TMPDIR="/mnt/bigdrive/docker-tmp"



Subject: I don't know what do you want
Author: Jan Garaj
Posted: 2015-05-05 13:01

I don't know what do you want to do with your IP, but IMHO for DNS should be OK if you specify some another DNS (e.g. google 8.8.8.8):
DOCKER_OPTS="-s btrfs --dns=172.17.42.1 --dns=8.8.8.8"
I don't have idea what is --bip --ip-forward;-)

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: Jan,
Author: [Not Specified]
Posted: 2015-05-07 07:15

Jan,

I appreciate your assistence which led me to the answer. for whatever reason i had to define the host as a dns server, as well as one of my actual dns servers and this has worked. int he above I realized i had typoed my server address.

--bip = statically assigned bridge address (the default conflicts with my internal network)
--ip-forward = allows dns requests to forward outside the container (should be the default but i had to have it set for some reason or my traffic did not go)



Subject: https://www.zenoss.org/forum
Author: Jan Garaj
Posted: 2015-05-07 12:52

https://www.zenoss.org/forum/8886

Docker "--ip-forward" is equivalent of sysctl "net.ipv4.conf.all.forwarding=1"

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



< Previous
Zenoss5 - How to install python modules?
  Next
Installing Zenpacks - where is 'zenpack'
>