TECHZEN Zenoss User Community ARCHIVE  

Unable to install Quilt and Percona

Subject: Unable to install Quilt and Percona
Author: [Not Specified]
Posted: 2015-05-21 15:32

Hi,

I am almost finished with a fresh Zenoss 5 installation on Centos 7. But now I am stuck at installing Quilt and Percona. I always get an error message from curl: 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known".

Our company proxy is set via environment variables in /etc/profile.d, /etc/sysconfig/docker and yum.conf. Yum and docker have both successful internet access and I can install software with yum or pull images from docker. But it seems that the control center do not use my proxy settings.

Has anyone an idea or advice



Subject: How did you setup your DNS
Author: Jan Garaj
Posted: 2015-05-22 02:28

How did you setup your DNS for docker /etc/sysconfig/docker and -dns option

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

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



Subject: I just followed the
Author: [Not Specified]
Posted: 2015-05-22 07:13

I just followed the installation guide:

DOCKER_OPTS="-s btrfs --dns=172.17.42.1"



Subject: Perfect, could you show full
Author: Jan Garaj
Posted: 2015-05-23 04:04

Perfect, could you show full error please (command and then full error message please)

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

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



Subject: Here are the error Messages:
Author: [Not Specified]
Posted: 2015-05-25 12:36

Here are the error Messages:

[root@des01039 ~]# serviced script run quilt.txt --service Zenoss.core
Logging to logfile: /var/log/serviced/script-2015-05-25-192710-root.log
Script started, file is /var/log/serviced/script-2015-05-25-192710-root.log
I0525 19:27:11.158026 25311 runner.go:160] executing step 0: DESCRIPTION quilt.txt -- add Quilt to a Zenoss image
I0525 19:27:11.158133 25311 runner.go:160] executing step 1: VERSION zenoss-quilt-1.0
I0525 19:27:11.158157 25311 runner.go:160] executing step 2: REQUIRE_SVC
I0525 19:27:11.158175 25311 eval.go:329] checking service requirement
I0525 19:27:11.158195 25311 eval.go:333] verifying service 3ivcs0zs59wvtz1xtslij9vjf
I0525 19:27:11.158642 25311 eval.go:339] found 3ivcs0zs59wvtz1xtslij9vjf tenant id for service 3ivcs0zs59wvtz1xtslij9vjf
I0525 19:27:11.158723 25311 runner.go:160] executing step 3: SNAPSHOT
I0525 19:27:11.158748 25311 eval.go:22] performing snapshot
I0525 19:27:21.324754 25311 eval.go:41] snapshot id: 3ivcs0zs59wvtz1xtslij9vjf_20150525-172718
I0525 19:27:21.324811 25311 runner.go:160] executing step 4: SVC_EXEC COMMIT Zenoss.core yum install -y epel-release
I0525 19:27:21.909417 25311 eval.go:291] running: serviced service shell -s 192721-20150525_3ivcs0zs59wvtz1xtslij9vjf 3ivcs0zs59wvtz1xtslij9vjf yum install -y epel-release
I0525 19:27:22.482745 26325 server.go:341] Connected to the control center at port 10.116.32.39:4979
I0525 19:27:22.599797 26325 server.go:435] Acquiring image from the dfs...
I0525 19:27:22.601223 26325 server.go:437] Acquired! Starting shell
Loaded plugins: fastestmirror
Trying to connect to logstash server... 127.0.0.1:5042
Connected to logstash server.

One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:

yum-config-manager --disable

4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
Could not retrieve mirrorlist http://mirrorlist.centos.org/release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
exit status 1
E0525 19:27:37.764450 25311 runner.go:162] error executing step 4: SVC_EXEC: exit status 1
I0525 19:27:37.764513 25311 runner.go:152] Executing exit functions
I0525 19:27:37.764527 25311 eval.go:45] restoring snapshot 3ivcs0zs59wvtz1xtslij9vjf_20150525-172718
exit status 1
Script done, file is /var/log/serviced/script-2015-05-25-192710-root.log

[root@des01039 ~]# serviced service run zope install-percona
I0525 19:29:11.481683 02951 server.go:341] Connected to the control center at port 10.116.32.39:4979
I0525 19:29:11.606622 02951 server.go:435] Acquiring image from the dfs...
I0525 19:29:11.608175 02951 server.go:437] Acquired! Starting shell
E0525 17:29:12.662839 00001 endpoint.go:514] No proxy for 3ivcs0zs59wvtz1xtslij9vjf_localhost_zenhubPB - no need to set empty address list
E0525 17:29:12.665088 00001 endpoint.go:514] No proxy for 3ivcs0zs59wvtz1xtslij9vjf_zep - no need to set empty address list
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:09 --:--:-- 0curl: (6) Could not resolve host: www.percona.com; Name or service not known

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: 1.) Are you able to resolve
Author: Jan Garaj
Posted: 2015-05-25 13:45

1.) Are you able to resolve name www.percona.com in command line on your CC master
2.) Are you able to resolve name www.percona.com in command line in Zenoss container (start zenoss, run command "serviced service attach Zenoss.core" and try nslookup command, check also dns settings in container, when you will be attached)

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

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



Subject: 1. The server is behind a
Author: [Not Specified]
Posted: 2015-05-26 05:57

1. The server is behind a firewall and is not able to resolve any intenet address with nslookup. But with the http_proxy environment variables I can use yum, curl or docker without a problem:

[root@des01039 ~]# curl -O 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
100 178 100 178 0 0 669 0 --:--:-- --:--:-- --:--:-- 671

2. For nslookup inside the container it is the same as above.

[root@5b1c5747d194 /]# cat /etc/resolv.conf
nameserver 172.17.42.1
search xxx.com xxx.net # our internal suffix list

Can I solve my issue when I add the http_proxy variable into the zenoss image Or is this the wrong way



Subject: Problem is clear. Setup proxy
Author: Jan Garaj
Posted: 2015-05-26 07:40

Problem is clear. Setup proxy for docker - google: "docker setup proxy" or http://www.zenoss.org/forum/4321
> Can I solve my issue when I add the http_proxy variable into the zenoss image Or is this the wrong way
Yes, it's wrong way. Configure docker with your proxy.

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

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



Subject: Hi Jan,
Author: [Not Specified]
Posted: 2015-05-27 03:37

Hi Jan,

as mentioned in my first post, the proxy is already set up in /etc/sysconfig/docker and docker has access to the internet. Even after changing the proxy from /etc/sysconfig/docker to the systemd drop-in directory (https://docs.docker.com/articles/systemd) the results with serviced commands are the same :(



Subject: this looks like a DNS issue
Author: Andrew Kirch
Posted: 2015-05-28 10:07

this looks like a DNS issue not a proxy issue. I had to add my local DNS server to the docker options to get DNS

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



Subject: Second Trelane. my docker
Author: [Not Specified]
Posted: 2015-05-28 13:09

Second Trelane. my docker opts line required my local DNS server as well as the host address of my zenoss machine. in my case for good measure i also enabled ip-forwarding which is supposed to be on by default, but take no chances. the options are documented here. https://docs.docker.com/articles/networking/



Subject: Same Problem
Author: [Not Specified]
Posted: 2015-05-29 13:41

So I believe the problem, but I don't know how to fix it, is that the logstash container is not using the proxy. Our internal DNS will not resolve external host names, but the proxy does that for you, so the request has to be going through the proxy for external name resolution to work.

I believe we may need to pass --env http_proxy= or something to the logstash container so it can resolve and reach percona

see here:
http://superuser.com/questions/890196/how-can-i-let-all-my-docker-contai...

But I'm not real clear on how or where to do that with serviced/zenoss-docker.



Subject: Hi Trelane,
Author: [Not Specified]
Posted: 2015-06-03 06:17

Hi Trelane,

I'm not a linux expert, but I don't think it is a DNS issue. The only way to get files from the internet is our proxy. Docker works (checked it with docker search and docker pull) when I set the http_proxy variables. I guess, that serviced and/or the zenoss image doesn't use my environment variables.



Subject: Lolli: that's entirely
Author: Andrew Kirch
Posted: 2015-06-03 10:35

Lolli: that's entirely possible, but the final error: "Could not resolve host: mirrorlist.centos.org; Name or service not known". is a DNS problem.

You need to start there, connect to your zope instance, run an nslookup, see what it's using for DNS, and correct that

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



< Previous
zodb_session database and tables
  Next
Setting up email alters using gmail
>