TECHZEN Zenoss User Community ARCHIVE  

Fresh install issues zenoss core 5.1.9 & 5.2.1

Subject: Fresh install issues zenoss core 5.1.9 & 5.2.1
Author: [Not Specified]
Posted: 2017-03-03 10:07

HiAll,

Im having some issues getting things off the ground. I original installed 5.1.9 from the ISO/DVD successfully onto an old desktop I had lying around (HP 6200 PRO MT 8GB ram and 500Gb sata disk) I got things up and running and was monitoring a couple of servers and some switches, Iquickly realised this machine wouldnt be enough for my testbut I liked what i'd seen so far with ZenOSS.. so decided to do a fresh install on better hardwareand this is where everything has unravelled kind of.... I should state that with the ISO /DVD Ive tried fully automated install setting no options just letting it do its thing(which is what i though I did on my dekstop machine)and changingthings like host/static ip as part of setup. The installation goes as expected(no erros during install on screen) and after selecting "Master" and change the passwords the installaton only responds on 22 53 and 8090. I've still got the original ZenOSS desktop running and i've compared as many files/logs as i can find looking for something to tell me whats not happening so i can fix it... I cannot find that magically line of code in the logfiles so I've come here to ask for advise or help as i'm stuck and dont know what I've done wrong or how to correct the situation.

What Ive tried so far

Bare metal

ZenOSS core 5.1.9 installed onDell T310 with 16GB ram, 180GB raid 1 - let it automatically partition disk, let it install with default values ie DHCP IP and not setting hostname or search domain.

ZenOSS core 5.19 installed same as above but set static IP/hostname/search domain.

ZenOSS core 5.2.1 wont install barfs about sdb just before GUI installer starts.

ZenOSS core 5.2.1 added another HD so it has sda sdb before installing, again barfs about sdcthis time just before GUI starts.

VMware guest

ZenOSS core 5.1.9 ESXi 6.5 guest VM 16GB ram,180GB disk - let it automatically partition disk, let it install with default values ie DHCP IP and not setting hostname or search domain

ZenOSS core 5.1.9 installed same as above but set static IP/hostname/search domain.

ZenOSS core 5.1.9VMware vSphere 5 Enterprise guest VM same as above two.

ZenOSS core 5.2.1 Barfs about sdb/sdc just before GUI installer starts.

Results from above always the same

Only ports 22 53 & 8090 open and working as expected, ip addr / ps axu shown below. When i compare this tomy working host i can see77 veth connections linked to docker0. When i compare the output of #ps axu , my working host has lots of redis & and a ton of dockerprocesses running but as you can see below ive got SOD all running for docker and redis.. Ive tried multiple installs of the above, by nuking the host/guest vm and nothing is working.

Is there anything simple that I'm missing or no doing that is causing this or is there a problem with the media I'm running out of machines to try installing on so i cant 100% rule out media... but for now as I've installed successfully the first time from the same media used I'm assuming its good and the issues is somewhere between the chair & keyboard. Im very new to docker hence why I used the resources/ISO in the email Igot from ZenOSS. I'm aware i can manually install ZenOSS which will be my next step I just didnt want that learning curve at the same time as evaluating ZenOSS.

Any help / advise / suggestions would be great - Idont like losing to computers so would really like to understand whats going on and why its not working before I pull out what little hair Ihaveleft.

Many thanks in advance.

Gabe

#ip addr

docker0: flags=4099 mtu 1500
inet 172.17.0.1 netmask 255.255.255.0 broadcast 0.0.0.0
ether 02:42:6d:b6:f5:b3 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens160: flags=4163 mtu 1500
inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::250:56ff:fe9c:392f prefixlen 64 scopeid 0x20
ether 00:50:56:9c:39:2f txqueuelen 1000 (Ethernet)
RX packets 32840 bytes 2806883 (2.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 495 bytes 64045 (62.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 12 bytes 740 (740.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12 bytes 740 (740.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

#ps axu

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 41288 3748 Ss 13:40 0:01 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
root 2 0.0 0.0 0 0 S 13:40 0:00 [kthreadd]
root 3 0.0 0.0 0 0 S 13:40 0:00 [ksoftirqd/0]
root 5 0.0 0.0 0 0 S< 13:40 0:00 [kworker/0:0H]
root 6 0.0 0.0 0 0 S 13:40 0:00 [kworker/u8:0]
root 7 0.0 0.0 0 0 S 13:40 0:00 [migration/0]
root 8 0.0 0.0 0 0 S 13:40 0:00 [rcu_bh]
root 9 0.0 0.0 0 0 S 13:40 0:00 [rcuob/0]
root 10 0.0 0.0 0 0 S 13:40 0:00 [rcuob/1]
root 11 0.0 0.0 0 0 S 13:40 0:00 [rcuob/2]
root 12 0.0 0.0 0 0 S 13:40 0:00 [rcuob/3]
root 13 0.0 0.0 0 0 S 13:40 0:00 [rcu_sched]
root 14 0.0 0.0 0 0 S 13:40 0:00 [rcuos/0]
root 15 0.0 0.0 0 0 S 13:40 0:00 [rcuos/1]
root 16 0.0 0.0 0 0 S 13:40 0:00 [rcuos/2]
root 17 0.0 0.0 0 0 S 13:40 0:00 [rcuos/3]
root 18 0.0 0.0 0 0 S 13:40 0:00 [watchdog/0]
root 19 0.0 0.0 0 0 S 13:40 0:00 [watchdog/1]
root 20 0.0 0.0 0 0 S 13:40 0:00 [migration/1]
root 21 0.0 0.0 0 0 S 13:40 0:00 [ksoftirqd/1]
root 22 0.0 0.0 0 0 S 13:40 0:00 [kworker/1:0]
root 23 0.0 0.0 0 0 S< 13:40 0:00 [kworker/1:0H]
root 24 0.0 0.0 0 0 S 13:40 0:00 [watchdog/2]
root 25 0.0 0.0 0 0 S 13:40 0:00 [migration/2]
root 26 0.0 0.0 0 0 S 13:40 0:00 [ksoftirqd/2]
root 28 0.0 0.0 0 0 S< 13:40 0:00 [kworker/2:0H]
root 29 0.0 0.0 0 0 S 13:40 0:00 [watchdog/3]
root 30 0.0 0.0 0 0 S 13:40 0:00 [migration/3]
root 31 0.0 0.0 0 0 S 13:40 0:00 [ksoftirqd/3]
root 33 0.0 0.0 0 0 S< 13:40 0:00 [kworker/3:0H]
root 34 0.0 0.0 0 0 S< 13:40 0:00 [khelper]
root 35 0.0 0.0 0 0 S 13:40 0:00 [kdevtmpfs]
root 36 0.0 0.0 0 0 S< 13:40 0:00 [netns]
root 37 0.0 0.0 0 0 S< 13:40 0:00 [perf]
root 38 0.0 0.0 0 0 S< 13:40 0:00 [writeback]
root 39 0.0 0.0 0 0 S< 13:40 0:00 [kintegrityd]
root 40 0.0 0.0 0 0 S< 13:40 0:00 [bioset]
root 41 0.0 0.0 0 0 S< 13:40 0:00 [kblockd]
root 42 0.0 0.0 0 0 S< 13:40 0:00 [md]
root 47 0.0 0.0 0 0 S 13:40 0:00 [khungtaskd]
root 48 0.0 0.0 0 0 S 13:40 0:00 [kswapd0]
root 49 0.0 0.0 0 0 SN 13:40 0:00 [ksmd]
root 50 0.0 0.0 0 0 SN 13:40 0:00 [khugepaged]
root 51 0.0 0.0 0 0 S 13:40 0:00 [fsnotify_mark]
root 52 0.0 0.0 0 0 S< 13:40 0:00 [crypto]
root 60 0.0 0.0 0 0 S< 13:40 0:00 [kthrotld]
root 61 0.0 0.0 0 0 S 13:40 0:00 [kworker/2:1]
root 62 0.0 0.0 0 0 S 13:40 0:00 [kworker/u8:1]
root 63 0.0 0.0 0 0 S< 13:40 0:00 [kmpath_rdacd]
root 64 0.0 0.0 0 0 S 13:40 0:00 [kworker/3:1]
root 65 0.0 0.0 0 0 S< 13:40 0:00 [kpsmoused]
root 66 0.0 0.0 0 0 S 13:40 0:00 [kworker/3:2]
root 67 0.0 0.0 0 0 S< 13:40 0:00 [ipv6_addrconf]
root 86 0.0 0.0 0 0 S< 13:40 0:00 [deferwq]
root 116 0.0 0.0 0 0 S 13:40 0:00 [kauditd]
root 123 0.0 0.0 0 0 S 13:40 0:00 [kworker/1:1]
root 298 0.0 0.0 0 0 S< 13:40 0:00 [ata_sff]
root 299 0.0 0.0 0 0 S 13:40 0:00 [scsi_eh_0]
root 300 0.0 0.0 0 0 S< 13:40 0:00 [scsi_tmf_0]
root 301 0.0 0.0 0 0 S 13:40 0:00 [scsi_eh_1]
root 302 0.0 0.0 0 0 S< 13:40 0:00 [scsi_tmf_1]
root 304 0.0 0.0 0 0 S< 13:40 0:00 [mpt_poll_0]
root 305 0.0 0.0 0 0 S< 13:40 0:00 [mpt/0]
root 307 0.0 0.0 0 0 S< 13:40 0:00 [events_power_ef]
root 313 0.0 0.0 0 0 S 13:40 0:00 [scsi_eh_2]
root 314 0.0 0.0 0 0 S< 13:40 0:00 [scsi_tmf_2]
root 318 0.0 0.0 0 0 S< 13:40 0:00 [ttm_swap]
root 331 0.0 0.0 0 0 S< 13:40 0:00 [kworker/0:1H]
root 392 0.0 0.0 0 0 S< 13:40 0:00 [kdmflush]
root 393 0.0 0.0 0 0 S< 13:40 0:00 [bioset]
root 404 0.0 0.0 0 0 S 13:40 0:00 [kworker/0:2]
root 405 0.0 0.0 0 0 S< 13:40 0:00 [kdmflush]
root 406 0.0 0.0 0 0 S< 13:40 0:00 [bioset]
root 419 0.0 0.0 0 0 S< 13:40 0:00 [xfsalloc]
root 420 0.0 0.0 0 0 S< 13:40 0:00 [xfs_mru_cache]
root 421 0.0 0.0 0 0 S< 13:40 0:00 [xfs-buf/dm-0]
root 422 0.0 0.0 0 0 S< 13:40 0:00 [xfs-data/dm-0]
root 423 0.0 0.0 0 0 S< 13:40 0:00 [xfs-conv/dm-0]
root 424 0.0 0.0 0 0 S< 13:40 0:00 [xfs-cil/dm-0]
root 425 0.0 0.0 0 0 S 13:40 0:02 [xfsaild/dm-0]
root 500 0.0 0.1 36812 8424 Ss 13:40 0:00 /usr/lib/systemd/systemd-journald
root 522 0.0 0.0 0 0 S< 13:40 0:00 [kworker/1:1H]
root 524 0.0 0.0 126672 1340 Ss 13:40 0:00 /usr/sbin/lvmetad -f
root 525 0.0 0.0 0 0 S< 13:40 0:00 [rpciod]
root 531 0.0 0.0 43116 1852 Ss 13:40 0:00 /usr/lib/systemd/systemd-udevd
root 615 0.0 0.0 0 0 S< 13:40 0:00 [kdmflush]
root 616 0.0 0.0 0 0 S< 13:40 0:00 [bioset]
root 618 0.0 0.0 0 0 S< 13:40 0:00 [xfs-buf/sda1]
root 619 0.0 0.0 0 0 S< 13:40 0:00 [xfs-data/sda1]
root 620 0.0 0.0 0 0 S< 13:40 0:00 [xfs-conv/sda1]
root 621 0.0 0.0 0 0 S< 13:40 0:00 [xfs-cil/sda1]
root 623 0.0 0.0 0 0 S 13:40 0:00 [xfsaild/sda1]
root 628 0.0 0.0 0 0 S< 13:40 0:00 [xfs-buf/dm-2]
root 629 0.0 0.0 0 0 S< 13:40 0:00 [xfs-data/dm-2]
root 630 0.0 0.0 0 0 S< 13:40 0:00 [xfs-conv/dm-2]
root 631 0.0 0.0 0 0 S< 13:40 0:00 [xfs-cil/dm-2]
root 632 0.0 0.0 0 0 S 13:40 0:00 [xfsaild/dm-2]
root 647 0.0 0.0 51180 1624 S root 670 0.0 0.0 287412 5660 Ssl 13:41 0:00 /usr/sbin/rsyslogd -n
dbus 672 0.0 0.0 26716 1796 Ss 13:41 0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
chrony 674 0.0 0.0 100640 1624 S 13:41 0:00 /usr/sbin/chronyd
root 682 0.0 0.1 432808 8048 Ssl 13:41 0:00 /usr/sbin/NetworkManager --no-daemon
root 684 0.0 0.0 26392 1712 Ss 13:41 0:00 /usr/lib/systemd/systemd-logind
root 687 0.0 0.0 19308 1256 Ss 13:41 0:00 /usr/sbin/irqbalance --foreground
root 692 0.0 0.0 203352 1224 Ssl 13:41 0:00 /usr/sbin/gssproxy -D
root 700 0.0 0.0 126328 1568 Ss 13:41 0:00 /usr/sbin/crond -n
polkitd 706 0.0 0.1 522700 11796 Ssl 13:41 0:00 /usr/lib/polkit-1/polkitd --no-debug
root 708 0.0 0.0 0 0 S< 13:41 0:00 [kworker/2:1H]
root 709 0.0 0.1 110508 15820 S 13:41 0:00 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-ens160.pid -lf /v
root 710 0.0 0.0 53056 2684 Ss 13:41 0:00 /usr/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant/wpa_suppli
root 918 0.0 0.0 0 0 S< 13:41 0:00 [kworker/3:1H]
nobody 920 0.0 0.0 15544 1232 Ss 13:41 0:00 /usr/sbin/dnsmasq -k
root 921 0.0 0.2 553056 16516 Ssl 13:41 0:00 /usr/bin/python -Es /usr/sbin/tuned -l -P
root 926 0.0 0.2 527348 23632 Ssl 13:41 0:02 /usr/bin/docker daemon -H fd:// -s devicemapper --storage-opt dm.basesize=45G --storage-opt
root 932 0.0 0.0 82544 3620 Ss 13:41 0:00 /usr/sbin/sshd -D
root 941 0.0 0.2 221528 17800 Ss 13:41 0:01 /opt/import4/bin/python /opt/import4/bin/gunicorn --pid /run/import4/pid -k eventlet -b 0.0.
root 965 0.0 0.0 110028 840 tty1 Ss+ 13:41 0:00 /sbin/agetty --noclear tty1 linux
root 1567 0.0 0.0 0 0 S< 13:41 0:00 [loop0]
root 1569 0.0 0.0 0 0 S< 13:41 0:00 [loop1]
root 1576 0.0 0.0 0 0 S< 13:41 0:00 [kdmflush]
root 1601 0.0 0.0 0 0 S< 13:41 0:00 [dm_bufio_cache]
root 1612 0.0 0.0 91124 2128 Ss 13:41 0:00 /usr/libexec/postfix/master -w
root 1646 0.0 0.0 0 0 S< 13:41 0:00 [bioset]
root 1656 0.0 0.0 0 0 S< 13:41 0:00 [kcopyd]
root 1657 0.0 0.0 0 0 S< 13:41 0:00 [bioset]
root 1658 0.0 0.0 0 0 S< 13:41 0:00 [dm-thin]
root 1659 0.0 0.0 0 0 S< 13:41 0:00 [bioset]
postfix 1697 0.0 0.0 91404 4112 S 13:41 0:00 qmgr -l -t unix -u
root 1962 0.0 0.2 242088 21772 S 13:41 0:01 /opt/import4/bin/python /opt/import4/bin/gunicorn --pid /run/import4/pid -k eventlet -b 0.0.
root 3183 0.0 0.0 0 0 S 15:01 0:00 [kworker/0:0]
postfix 3208 0.0 0.0 91228 3896 S 15:19 0:00 pickup -l -t unix -u
root 3210 0.0 0.0 0 0 S 15:26 0:00 [kworker/2:0]
root 3211 0.0 0.0 147820 6064 Rs 15:31 0:00 sshd: root@pts/0
root 3213 0.0 0.0 115888 2316 pts/0 Ss 15:31 0:00 -bash
root 3230 0.0 0.0 148984 6708 pts/0 S 15:31 0:00 python /root/appliance/adminmenu.py
root 3231 0.0 0.0 115904 2628 pts/0 S 15:31 0:00 bash
root 3242 0.0 0.0 0 0 S 15:31 0:00 [kworker/2:2]
root 3244 1.0 0.0 139492 1628 pts/0 R+ 15:33 0:00 ps axu

# service docker status
Redirecting to /bin/systemctl status docker.service
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/docker.service.d
docker.conf
Active: active (running) since Fri 2017-03-03 15:41:43 UTC; 2s ago
Docs: https://docs.docker.com
Main PID: 3629 (docker)
CGroup: /system.slice/docker.service
3629 /usr/bin/docker daemon -H fd:// -s devicemapper --storage-opt dm.basesize=45G --storage-opt dm.thinpooldev= --exec-opt native.cgroupdriv...

Mar 03 15:41:43 core systemd[1]: Starting Docker Application Container Engine...
Mar 03 15:41:43 core systemd[1]: Started Docker Application Container Engine.



Subject: Solved
Author: [Not Specified]
Posted: 2017-03-06 09:29

Hi All,

While no one offered any help/suggestion/advice, I decided to try 1 more time on a different server... after installing on another server and getting th same issue today with no specific error that i can see or find.. the only thing that is different between my desktop test machine and the servers was the amount of HD avaliable. Once i gave the server more total disk space the installation worked without issue....

Im still a little confused as to why if HD space is so important it didnt fail or warn me... at least i can now continue.

Thanks

Gabe



Subject: The installation from ISO/OVA
Author: [Not Specified]
Posted: 2017-03-14 05:07

The installation from ISO/OVA requires 7 disks.
Unless you install 5.2.2 manually. Let me know if you need help with your Zenoss installation.

 

Kind regards,

Robert E.

zenoss@webhostingspace.net

Zenoss Core/Service Dynamics 5.2.2 High Availability - the missing guide is here



Subject: RE: The installation from ISO/OVA
Author: Poornasai Kodigala
Posted: 2017-05-31 02:20

I am installed zencore VM using ISO Image and we dont have any technical documnet for post installation steps for application up & running. Can you please share the any SOP or steps further.

------------------------------
Poornasai Kodigala
HCL
Noida
------------------------------


< Previous
Need to install SAML for Zope
  Next
Zenoss Core 5 - Why can't I start serviced due to the docker container having mo ...
>