TECHZEN Zenoss User Community ARCHIVE  

Failed to install Percona-Toolkit

Subject: Failed to install Percona-Toolkit
Author: [Not Specified]
Posted: 2015-12-29 14:32

I can't seem to get Percona-Toolkit to install. I have started MariaDB with

serviced service start mariadb

after reading this thread:

http://www.zenoss.org/forum/136776

but it says that the service is already started. I can not get it to install either after manual installation, and it does not install with the auto-deploy script either. I have made a lot of progress, but I would like everything to be setup and ready to go before I go any further. Hope someone can help! BTW thanks for all the help I've received on here recently.



Subject: I will add that the error
Author: [Not Specified]
Posted: 2015-12-29 14:34

I will add that the error message I am getting is similar to the previous post of:

serviced service run zope install-percona
I1229 14:54:49.112033 24754 server.go:341] Connected to the control center at port 172.31.58.222:4979
I1229 14:54:49.192990 24754 server.go:442] Acquiring image from the dfs...
I1229 14:54:49.193877 24754 server.go:444] 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-toolkit-2.2.12.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 178 100 178 0 0 1143 0 --:--:-- --:--:-- --:--:-- 1148
percona-toolkit-2.2.12/README
percona-toolkit-2.2.12/MANIFEST
percona-toolkit-2.2.12/Makefile.PL
percona-toolkit-2.2.12/INSTALL

.....

percona-toolkit-2.2.12/bin/pt-align
F1229 14:54:57.138858 24754 shell.go:241] failed to stop container: 332a65f07f3ca0812cfb02c83911d98650d03d6f4c74506fa392c576e05bcae8 (Container not running: 332a65f07f3ca0812cfb02c83911d98650d03d6f4c74506fa392c576e05bcae8)

Hope this helps.



Subject: Autodeploy script includes
Author: Jan Garaj
Posted: 2015-12-29 15:04

Autodeploy script includes also some my knowledge, which is not included in official Zenoss guides. So I'm surprised, that you have a problem. https://github.com/monitoringartist/zenoss5-core-autodeploy/blob/master/core-autodeploy.sh#L1120 dbservice=$(serviced service list | grep -i mariadb | awk '{print $1}' | sort -r | grep -i 'mariadb' | head -n 1) serviced service start $dbservice serviced service run zope install-percona

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

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



Subject: Again, thanks for your help.
Author: [Not Specified]
Posted: 2015-12-29 15:10

Again, thanks for your help. But I am still getting the same error saying that it has failed to stop container.



Subject: Please use always full
Author: Jan Garaj
Posted: 2015-12-29 15:43

Please use always full pastebin logs and how did you try to solve your problem. You will increase your response chance.

Let's start with your autodeploy problem. Please provide full pastebin logs from autodeployement and what was the problem 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: Autodeploy script log:http:/
Author: [Not Specified]
Posted: 2015-12-29 16:07

Autodeploy script log:
http://pastebin.com/9CbtrX8h

After script finished I rebooted the VM.Then restarted serviced and tried to install again:
http://pastebin.com/nasGsMeE

Still the same error. Then I tried the commands you mentioned after stopping and starting serviced.
http://pastebin.com/S7Q3HBP3

This is the journalctl -u serviced -f log when I stop and restart serviced.
http://pastebin.com/R9048CsS

Are there any other logs you need to see



Subject: Autodeploy and manual
Author: Jan Garaj
Posted: 2015-12-29 18:59

Autodeploy and manual installation have the same problem. I've seen it also before. However it's only Zenoss tuning, so I've ignored it. (It's nice to have, but it's not required for Zenoss 5). Try it again and add also docker journalctl log please. I can't find any log about container id in the log: F1229 17:01:27.216073 12251 shell.go:241] failed to stop container: b5681596b781fac1f6cd3714135a6280b117631b345d937f6ab48fc0ad59b20a (Container not running: b5681596b781fac1f6cd3714135a6280b117631b345d937f6ab48fc0ad59b20a) Also you can try to install it manually. Definition of install-percona command: "install-percona": "NOCOMMIT=true ${ZENHOME:-/opt/zenoss}/bin/zenrun percona.sh install", serviced service shell -s Fping -i Zope bash /opt/zenoss/bin/zenrun percona.sh install Thx

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

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



< Previous
Unable to log in to fresh install of Zenoss Core 5
  Next
Monitoring in zenoss 4.2.5
>