TECHZEN Zenoss User Community ARCHIVE  

Zenoss5 auto deploy doesn't work

Subject: Zenoss5 auto deploy doesn't work
Author: [Not Specified]
Posted: 2015-04-01 00:32

I'm running the Zenoss5 autodeploy script on CentOS7. Everything is smooth up to the end where it just scrolls the following error over and over and finally times out.

could not create a client to the master: dial tcp 192.168.3.100:4979: connection refused
#73: Control Service is not fully started, I'm trying in next 10 seconds

#87: Control Service is not fully started, I'm trying in next 10 seconds
rpc: can't find service Master.GetHosts
#88: Control Service is not fully started, I'm trying in next 10 seconds
could not create a client to the master: dial tcp 192.168.3.100:4979: connection refused
#89: Control Service is not fully started, I'm trying in next 10 seconds
echo "could not create a client to the master: dial tcp 192.168.3.100:4979: connection refused" | wc -l
Problem with adding a host - check output from test: could not create a client to the master: dial tcp 192.168.3.100:4979: connection refused

I've tried re-running the script and it does the same thing. Where do I go from here

Thanks



Subject: http://wiki.zenoss.org
Author: Jan Garaj
Posted: 2015-04-01 03:36

http://wiki.zenoss.org/download/core/docs/Zenoss_Core_Installation_Guide...
page 29 - Deploying the Zenoss Core application - you can try to follow documentation

If you provide full installation log from autodeploy script (http://pastebin.com/) + output (http://pastebin.com/) from the. command: journalctl -u serviced -a -n 1000, then author can improve autodeploy script eventually.

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 have followed the
Author: [Not Specified]
Posted: 2015-04-01 08:32

I have followed the documentation numerous times, Step 29 is kind of pointless if I can't even get the darn thing installed or running.

Here is the start up attempt of serviced.
http://pastebin.com/T1RrJHrf



Subject: > Apr 01 08:25:48 zenoss
Author: Jan Garaj
Posted: 2015-04-01 09:50

> Apr 01 08:25:48 zenoss serviced[24491]: F0401 13:25:48.762132 24491 daemon.go:276] exit status 1: Job for nfs-server.service failed. See 'systemc... details.

Investigate problem with nfs-server (systemctl status nfs-server.service, journalctl -u nfs-server -a -n 1000). Which version of OS are you using I know that RHEL 7.1 has some problem with NFS (RHEL 7.0 is OK).

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

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



Subject: Its a minimal install on
Author: [Not Specified]
Posted: 2015-04-01 11:49

Its a minimal install on CentOS 7.

Linux version 3.10.0-123.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.2 20140120 (Red Hat 4.8.2-16) (GCC) ) #1 SMP Mon Jun 30 12:09:22 UTC 2014



Subject: Apr 01 11:53:54 zenoss
Author: [Not Specified]
Posted: 2015-04-01 11:55

Apr 01 11:53:54 zenoss systemd[1]: Starting NFS server and services...
Apr 01 11:53:54 zenoss rpc.nfsd[28314]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
Apr 01 11:53:54 zenoss rpc.nfsd[28314]: rpc.nfsd: unable to set any sockets for nfsd
Apr 01 11:53:54 zenoss systemd[1]: nfs-server.service: main process exited, code=exited, status=1/FAILURE
Apr 01 11:53:54 zenoss systemd[1]: Failed to start NFS server and services.
Apr 01 11:53:54 zenoss systemd[1]: Unit nfs-server.service entered failed state.



Subject: You don't have problem
Author: Jan Garaj
Posted: 2015-04-01 18:20

You don't have problem "Zenoss5 auto deploy doesn't work", but you have "Failed to start NFS server and services" problem.
Solve NFS issue and it should be OK.
I don't how, but you you are not alone - see google "rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)"

Try latest version of autdeploy script. Workaround for rpcbind is included.

https://jira.zenoss.com/browse/CC-903

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

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



Subject: Thanks Jan,
Author: [Not Specified]
Posted: 2015-04-02 10:03

Thanks Jan,
For some reason there was a stale instance of rpcbind running and not allowing the daemon to fireup, killed that one and restarted, now is working.



< Previous
error present in zopectl.log
  Next
ZenOSS 4.2.5 Email Variables
>