TECHZEN Zenoss User Community ARCHIVE  

Zenoss 5 install

Subject: Zenoss 5 install
Author: [Not Specified]
Posted: 2015-04-22 10:15

Hi,

I am new to using Zenoss and a new Linux user. I am trying to install Zenoss 5 on a Linux system. I actaully downloaded the .OVA file for Zenoss 5 and created a new VM. I am able to log into the console of the new VM, however not sure how to start Zenoss service on it.

I guess the .new VM created from this OVA file would have Zenoss 5 installed on it already. How do I go about starting the Zenoss server and logging into the webpage

Please help.

Thanks



Subject: Did you read the Install
Author: [Not Specified]
Posted: 2015-04-22 11:36

Did you read the Install Guide at all Try Chapter 4

http://wiki.zenoss.org/download/core/docs/Zenoss_Core_Installation_Guide...



Subject: Read the Install
Author: [Not Specified]
Posted: 2015-04-22 13:48

I read the install doc and got to the point of starting the Zenoss service on the Control Center. I started the service and now getting the following error in the logs:

Trying to discover my pool...
masterClient.GetHost 140a2433 failed: hosts_server.go host not found (has this host been added)

Can someone help me with this error



Subject: What does journalctl -u
Author: [Not Specified]
Posted: 2015-04-22 14:05

What does journalctl -u serviced -f show when trying to start the service in CC



Subject: log output
Author: [Not Specified]
Posted: 2015-04-22 14:30

This is what it says:

[root@zenossmaster ~]# journalctl -u serviced -f
-- Logs begin at Wed 2015-04-22 17:27:49 UTC. --
Apr 22 19:29:11 zenossmaster serviced[2422]: W0422 19:29:11.818308 02422 daemon.go:520] masterClient.GetHost 140a2433 failed: hosts_server.go host not found (has this host been added)
Apr 22 19:29:16 zenossmaster serviced[2422]: I0422 19:29:16.818552 02422 daemon.go:510] Trying to discover my pool...
Apr 22 19:29:16 zenossmaster serviced[2422]: W0422 19:29:16.820156 02422 daemon.go:520] masterClient.GetHost 140a2433 failed: hosts_server.go host not found (has this host been added)
Apr 22 19:29:21 zenossmaster serviced[2422]: I0422 19:29:21.820465 02422 daemon.go:510] Trying to discover my pool...
Apr 22 19:29:21 zenossmaster serviced[2422]: W0422 19:29:21.822038 02422 daemon.go:520] masterClient.GetHost 140a2433 failed: hosts_server.go host not found (has this host been added)
Apr 22 19:29:26 zenossmaster serviced[2422]: I0422 19:29:26.822277 02422 daemon.go:510] Trying to discover my pool...
Apr 22 19:29:26 zenossmaster serviced[2422]: W0422 19:29:26.823718 02422 daemon.go:520] masterClient.GetHost 140a2433 failed: hosts_server.go host not found (has this host been added)
Apr 22 19:29:28 zenossmaster systemd[1]: Started Zenoss ServiceD.
Apr 22 19:29:31 zenossmaster serviced[2422]: I0422 19:29:31.823960 02422 daemon.go:510] Trying to discover my pool...
Apr 22 19:29:31 zenossmaster serviced[2422]: W0422 19:29:31.825734 02422 daemon.go:520] masterClient.GetHost 140a2433 failed: hosts_server.go host not found (has this host been added)
Apr 22 19:29:36 zenossmaster serviced[2422]: I0422 19:29:36.826046 02422 daemon.go:510] Trying to discover my pool...
Apr 22 19:29:36 zenossmaster serviced[2422]: W0422 19:29:36.827637 02422 daemon.go:520] masterClient.GetHost 140a2433 failed: hosts_server.go host not found (has this host been added)



Subject: Service up
Author: [Not Specified]
Posted: 2015-04-22 14:58

I had to some changes to hosts file and the zenoss services started working. Now whats the URL of the zenoss web-interface

When i go to the control center, under applications, next to Zenoss.core, it says Virtual hostname = https://zenoss5.zenossmaster
This page doesnot work. When i go to http://zenosmaster:8080 .. it does not work either.

Can someone help



Subject: You will need to either
Author: [Not Specified]
Posted: 2015-04-22 15:15

You will need to either configure the FQDN with a DNS entry. Or if you want to temporary get it going. put an entry in your local hosts file

IP.to.zenoss.box zenoss5.zenossmaster



Subject: Done already
Author: [Not Specified]
Posted: 2015-04-22 15:22

I have that entry in the /etc/hosts file already but still not working.



Subject: Help
Author: [Not Specified]
Posted: 2015-04-23 08:35

Can someone please help



Subject: What exactly does it say when
Author: [Not Specified]
Posted: 2015-04-23 10:15

What exactly does it say when you go to https://zenoss5.zenossmaster

Does it timeout like its not accessing



Subject: FireFox says:
Author: [Not Specified]
Posted: 2015-04-23 10:33

Server not found

Firefox can't find the server at zenoss5.zenossmaster.



Subject: > I guess the .new VM created
Author: Jan Garaj
Posted: 2015-04-23 11:30

> I guess the .new VM created from this OVA file would have Zenoss 5 installed on it already.

That's not true. It's a only basic VM, all docker images must be downloaded, host/app deployed. My recommendation: throw away ova VM (because no official documentation is provided) and follow official installation guide.

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

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



Subject: Zenoss.Core running
Author: [Not Specified]
Posted: 2015-04-23 12:26

When I log into the Control center (https://zenossmaster) it shows me Zenoss.core under Applications and it shows the status as running.

Do you still think that I should go with a new zenoss install

Thanks



Subject: Auto deploy
Author: [Not Specified]
Posted: 2015-04-23 14:03

I uninstalled the zenoss on the VM which I created from the OVA file and followed the auto-deploy instructions. I am getting the following error while auto-deploying:

4.1 Adding current host to the default resource pool
Please be patient, because docker image zenoss/serviced-isvcs must be downloaded before first start.
You can check progress in new console: journalctl -u serviced -f -a
Script is trying to check status every 10s. Timeout for this step is 15 minutes.
serviced host list 2>&1
could not create a client to the master: dial tcp 10.20.51.36:4979: connection refused
#1: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#2: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#3: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#4: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#5: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds

Can you help



Subject: One serious question: what
Author: Jan Garaj
Posted: 2015-04-24 02:50

One serious question: what should script print, that user will be patient (max 15 minutes) Now is printing:
Please be patient, because docker image zenoss/serviced-isvcs must be downloaded before first start.
#5: This is not a problem, because Control Centre service is not fully started,

Control center is downloading docker image in the background - it takes 100sec on my production server and you are complaining after 50sec. Be patient and pls reply for my previous question.

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

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



Subject: Install Issues
Author: [Not Specified]
Posted: 2015-04-24 09:21

I think I was being more aggressive in the install approach that's why I was being impatient. I think I should have waited..

Now when I try to run the core-autodeply again, I get the following error:

./core-autodeploy.sh -d /var/lib/docker -s /opt/serviced/var -v /opt/serviced/var/volumes b /opt/serviced/var/backups
Autodeploy script 2015-04-24 for Control Center master host and Zenoss Core 5/Zenoss Resource Manager 5
Install guide: http://wiki.zenoss.org/download/core/docs/Zenoss_Core_Installation_Guide...
Requirements:
Min number of available CPUs: 4
Min size of available RAM: 20GB
These filesystems must be mounted with correct type and size:
Filesystem Type Min size
/ xfs 30GB
/var/lib/docker btrfs 30GB
/opt/serviced/var xfs 30GB
/opt/serviced/var/volumes btrfs 1GB
/opt/serviced/var/backups xfs 1GB
0 Preparing /var/lib/docker filesystem - device: /var/lib/docker
/var/lib/docker filesystem is already mounted, skipping creating this filesystem
0 Preparing /opt/serviced/var filesystem - device: /opt/serviced/var
/opt/serviced/var filesystem is already mounted, skipping creating this filesystem
0 Preparing /opt/serviced/var/volumes filesystem - device: /opt/serviced/var/volumes
/opt/serviced/var/volumes will be formated to btrfs. All current data on /opt/serviced/var/volumes will be lost and /etc/fstab will be updated. Do you want to continue (y/n)
y
mkfs -t btrfs -f --nodiscard /opt/serviced/var/volumes
SMALL VOLUME: forcing mixed metadata/data groups

WARNING! - Btrfs v3.12 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using

unable to open /opt/serviced/var/volumes: Is a directory
sed -i -e "\|^/opt/serviced/var/volumes|d" /etc/fstab
echo "/opt/serviced/var/volumes /opt/serviced/var/volumes btrfs rw,noatime,nodatacow 0 0" >> /etc/fstab
mount /opt/serviced/var/volumes
mount: /opt/serviced/var/volumes is not a block device
Problem with mounting /opt/serviced/var/volumes

Can you suggest what needs to be done

Thanks



Subject: What does your df -Th output?
Author: [Not Specified]
Posted: 2015-04-24 09:54

What does your df -Th output

Looks like something with your /opt/serviced/var/volumes mount. You cannot just create a folder it has to be a mounted btrfs file system at that path.



Subject: df -Th
Author: [Not Specified]
Posted: 2015-04-24 10:00

Here is the output:

[root@zenossmaster tmp]# df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 xfs 20G 1.3G 19G 7% /
devtmpfs devtmpfs 5.8G 0 5.8G 0% /dev
tmpfs tmpfs 5.8G 0 5.8G 0% /dev/shm
tmpfs tmpfs 5.8G 8.6M 5.8G 1% /run
tmpfs tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup
/dev/sda1 xfs 509M 140M 370M 28% /boot
/dev/sda4 btrfs 222G 6.0G 215G 3% /var/lib/docker
/dev/sda4 btrfs 222G 6.0G 215G 3% /opt/serviced/var



Subject: Page 7 of the install guide.
Author: [Not Specified]
Posted: 2015-04-24 10:29

Page 7 of the install guide. your mounts/file systems are incorrect.

/opt/serviced/var should be an xfs. You don't have a /opt/serviced/var/volumes or /backups.

Here is my df -Th

Filesystem Type Size Used Avail Use% Mounted on
/dev/sda7 xfs 67G 6.9G 61G 11% /
devtmpfs devtmpfs 8.8G 0 8.8G 0% /dev
tmpfs tmpfs 8.8G 0 8.8G 0% /dev/shm
tmpfs tmpfs 8.8G 1.6M 8.8G 1% /run
tmpfs tmpfs 8.8G 0 8.8G 0% /sys/fs/cgroup
/dev/sda3 xfs 40G 6.2G 33G 16% /opt/serviced/var
/dev/sda1 xfs 497M 89M 408M 18% /boot
/dev/sda2 btrfs 147G 13G 132G 9% /var/lib/docker
/dev/sda2 btrfs 147G 13G 132G 9% /opt/serviced/var/volumes
/dev/sda5 xfs 40G 33M 40G 1% /opt/serviced/var/backups



Subject: You can use ./core-autodeploy
Author: Jan Garaj
Posted: 2015-04-24 17:16

You can use ./core-autodeploy.sh -d /var/lib/docker -s /opt/serviced/var -v /opt/serviced/var/volumes b /opt/serviced/var/backups
but block device (harddisk-filesystem) must be parameters, e.g /dev/sda4, /dev/sda3
Block devices(disks) must be unmounted, otherwise autodeploy script skip them.
Or you can still format/mount your disks manually.

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

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



Subject: Installed Zenoss. Getting error now
Author: [Not Specified]
Posted: 2015-04-27 09:00

Created the correct file systems and mounted them as required.. Zenoss install gave no errors. Now when i start zenoss and do journalctl -u serviced -f, I get the following:

Apr 27 09:50:59 zenosstest serviced[2519]: W0427 13:50:59.842772 02519 daemon.go:520] masterClient.GetHost 140a19d9 failed: hosts_server.go host not found (has this host been added)
Apr 27 09:51:04 zenosstest serviced[2519]: I0427 13:51:04.843079 02519 daemon.go:510] Trying to discover my pool...
Apr 27 09:51:04 zenosstest serviced[2519]: W0427 13:51:04.845198 02519 daemon.go:520] masterClient.GetHost 140a19d9 failed: hosts_server.go host not found (has this host been added)
Apr 27 09:51:09 zenosstest serviced[2519]: I0427 13:51:09.845461 02519 daemon.go:510] Trying to discover my pool...
Apr 27 09:51:09 zenosstest serviced[2519]: W0427 13:51:09.847381 02519 daemon.go:520] masterClient.GetHost 140a19d9 failed: hosts_server.go host not found (has this host been added)
Apr 27 09:51:14 zenosstest serviced[2519]: I0427 13:51:14.847685 02519 daemon.go:510] Trying to discover my pool...
Apr 27 09:51:14 zenosstest serviced[2519]: W0427 13:51:14.849855 02519 daemon.go:520] masterClient.GetHost 140a19d9 failed: hosts_server.go host not found (has this host been added)
Apr 27 09:51:19 zenosstest serviced[2519]: I0427 13:51:19.850147 02519 daemon.go:510] Trying to discover my pool...
Apr 27 09:51:19 zenosstest serviced[2519]: W0427 13:51:19.852256 02519 daemon.go:520] masterClient.GetHost 140a19d9 failed: hosts_server.go host not found (has this host been added)
Apr 27 09:51:24 zenosstest serviced[2519]: I0427 13:51:24.852541 02519 daemon.go:510] Trying to discover my pool...

Unable to get to https://zenosstest

Can you please help



Subject: I too, am getting the same:
Author: [Not Specified]
Posted: 2015-06-17 20:38

I too, am getting the same on Zenoss Core 5 install:

Jun 17 21:33:55 zenossmaster serviced[2141]: I0618 01:33:55.167248 02141 daemon.go:511] Trying to discover my pool...
Jun 17 21:33:55 zenossmaster serviced[2141]: W0618 01:33:55.169161 02141 daemon.go:521] masterClient.GetHost 007f0100 failed: hosts_server.go host not found (has this host been added

I have followed the installation guide located at: "http://www.zenoss.com/sites/default/files/documentation/Zenoss_Core_Inst... on Centos 7.

Perhaps I am confused Good thing I've snapshot'd the heck out of my VM :)

Thanks all.



Subject: Auto deploy worked well
Author: [Not Specified]
Posted: 2015-06-28 03:09

We found the auto-deply created by Jan.garaj worked very well (THANKS Jan.garaj!!)

as long as you make sure of the following:
1) use Centos MIN install and properly setup your server with fixed IP address and correct hostname during install
2) use the manual partition method of configuring the HDD - with the correct mount points and file system types
3) make sure you have proper DNS or local host file setup correctly to point IP address to your server's hostname
4) remember to config the ccuser password from the CLI after the install script completes
passwd ccuser
5) change the SERVICED SETTINGS file to allow your DNS name to connect
vi /etc/default/serviced
and set SERVICED_VHOST_ALIASES to your correct hostname and FQDN
6) You should then be able to browser navigate to the HTTPS:\\DNS hostname of your machine (remember its https) - which must match both your DNS or HOSTFILE setup AND the address you added in the SERVICED SETTINGS file
7) select the ZENOSS APP and start it
8) click the ZENOSS APP to show the virtual hosts and add a virtual host for zproxy with the correct DNS URL. you can then delete the app.hostname default virtual host - I dont know why docker setups up container virtual hosts with this ridiculous sub.hostname format

honestly - the entire setup of Zenoss 5 is an incredibly complex beast requiring significant LINUX skills and massive resources... which is why we are seriously consider moving to something else, or just keep our Zenoss 4.2.5 system for the next few years



Subject: Stuck on "trying to discover my pool"
Author: [Not Specified]
Posted: 2015-12-18 13:01

I too have been getting:

Dec 18 13:42:00 ip-172-31-55-100.ec2.internal serviced[12181]: I1218 18:42:00.191255 12181 daemon.go:516] Trying to discover my pool...

Dec 18 13:42:00 ip-172-31-55-100.ec2.internal serviced[12181]: W1218 18:42:00.192475 12181 daemon.go:526] masterClient.GetHost 1fac6437 failed: hosts_server.go host not found (has this host been added)

Has anyone been able to find a work around for this



< Previous
Zenoss5 (deployed via auto-deploy scripts ) - unable to discover network
  Next
Zenoss 5.0.2 -> zenping problem
>