Zenoss ZenTech Community

I´m having problem getting the ".run" scripts running after first reboot when installing

problery missing something with disk layout i asume

can someone give me a screenshot of a working disk (install view) layout

i must have tried 10times..sometimes the script doesent even run after first reboot. the other i end up with just a centos without docker and stuff.

or just a good howto run the iso install (running on proxmox)

+ rm -rf /var/lib/docker
+ /root/appliance/setup_docker_conf.sh
++ /root/appliance/get_devicemapper_name.sh docker
++ xargs
File descriptor 3 (/root/appliance/adminmenu.options) leaked on lvs invocation. Parent PID 11312: /bin/bash
File descriptor 4 (/root/firstrun.2019-03-07T09:39:35.199439.log) leaked on lvs invocation. Parent PID 11312: /bin/bash
Volume group "docker" not found
Cannot process volume group docker
+ TPOOL_NAME=
+ IPV6_EXTRA=
+ '[' -f /etc/ipv6cidr.conf ']'
+ DOCKER_CONF=/etc/systemd/system/docker.service.d/docker.conf
+ DOCKER_OPTIONS=/etc/sysconfig/docker
+ cat
+ LOG_LEVEL=--log-level=error
+ cat
+ mkdir -p /var/lib/docker/
+ ln -s /tmp /var/lib/docker/tmp
+ systemctl stop docker
+ systemctl unmask docker.socket
+ systemctl daemon-reload
+ systemctl start docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
++ ip addr show docker0
++ grep inet
++ awk -F / '{print $1}'
++ grep -v inet6
++ awk '{print $2}'
Device "docker0" does not exist.
+ DOCKER_DNS=
+ DOCKER_BIP=/24
+ sed -i -e 's;--log-level=error;--log-level=error --dns= --bip=/24;' /etc/sysconfig/docker
+ systemctl stop docker
+ systemctl daemon-reload
+ systemctl start docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
+ systemctl disable docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
zenoss/opentsdb 24.0.8

/F

------------------------------
Fredrik
------------------------------

Subject:	RE: Disk layout in virtual machine
Author:	Arthur
Posted:	2019-03-09 08:48

Hi Fredrik
The first thing the setup_docker_conf.sh is doing, is looking for your thinpool (TPOOL_NAME).

#!/bin/bash

#############
##
## Additional docker arguments added to new appliances need to be applied to upgrades
## in /updates/update-cc.sh::update_docker_config()
##
#############

set -x

# find the thinpool lv for docker and get device mapper device name (xargs to strip trailing whitespace)
TPOOL_NAME="$(/root/appliance/get_devicemapper_name.sh docker | xargs)". For this it uses the helper script
get_devicemapper_name.sh.

I assume you are missing your docker thin-pool. A good output looks like this:

# /root/appliance/get_devicemapper_name.sh docker | xargs
File descriptor 3 (/root/appliance/adminmenu.options) leaked on lvs invocation. Parent PID 20809: /bin/bash
/dev/mapper/docker-docker--pool

The lsblk output shows the details about the docker pool

# lsblk --output=NAME,SIZE,TYPE,FSTYPE
NAME SIZE TYPE FSTYPE
sda 29.3G disk
└─sda1 29.3G part xfs
sdb 48.8G disk
└─sdb1 48.8G part LVM2_member
├─docker-docker--pool_tmeta 900M lvm
│ └─docker-docker--pool 42.2G lvm
│ ├─docker-8:1-50339248-7927f09a2a260f744e9910e0dd158684e7e0cfc20dfd84152e44bb132c7330c3 45G dm xfs
│ ├─docker-8:1-50339248-54fbd31e7eb1920fa406634c7d50f3d621c799b9f7921a5ecacbd4274600c16b 45G dm xfs
│ ├─docker-8:1-50339248-4ba5caf637da230aba30a79a595bc3781f94655489eb19a8f831495c5d3278e8 45G dm xfs
│ ├─docker-8:1-50339248-fab2abf0c61ed3816207074d863546e1da44beb2060b2e24805af3cf1a3c37bb 45G dm xfs
│ ├─docker-8:1-50339248-7477741a7df384de1dbd7bf69482c8e7f36e8091c7943ae4c9d645507f076702 45G dm xfs
│ ├─docker-8:1-50339248-bbca206d761991ea0c56c49d688e660366d44b8287ffe8d81752077fdf03c2c7 45G dm xfs
│ └─docker-8:1-50339248-3ed121372caf1e43af3ece6b512337465a77c02b8b165d6b52c990c820234c2a 45G dm xfs
└─docker-docker--pool_tdata 42.2G lvm
└─docker-docker--pool 42.2G lvm
├─docker-8:1-50339248-7927f09a2a260f744e9910e0dd158684e7e0cfc20dfd84152e44bb132c7330c3 45G dm xfs
├─docker-8:1-50339248-54fbd31e7eb1920fa406634c7d50f3d621c799b9f7921a5ecacbd4274600c16b 45G dm xfs
├─docker-8:1-50339248-4ba5caf637da230aba30a79a595bc3781f94655489eb19a8f831495c5d3278e8 45G dm xfs
├─docker-8:1-50339248-fab2abf0c61ed3816207074d863546e1da44beb2060b2e24805af3cf1a3c37bb 45G dm xfs
├─docker-8:1-50339248-7477741a7df384de1dbd7bf69482c8e7f36e8091c7943ae4c9d645507f076702 45G dm xfs
├─docker-8:1-50339248-bbca206d761991ea0c56c49d688e660366d44b8287ffe8d81752077fdf03c2c7 45G dm xfs
└─docker-8:1-50339248-3ed121372caf1e43af3ece6b512337465a77c02b8b165d6b52c990c820234c2a 45G dm xfs
sdc 15.6G disk
└─sdc1 15.6G part swap
sdd 15.6G disk
└─sdd1 15.6G part xfs
sde 48.8G disk
└─sde1 48.8G part xfs
sdf 146.5G disk
└─sdf1 146.5G part xfs
sdg 195.3G disk
└─sdg1 195.3G part LVM2_member
├─serviced-serviced--pool_tmeta 1.8G lvm
│ └─serviced-serviced--pool 172.3G lvm
│ ├─docker-8:1-34019796-2gPEaR5Rxq9uRF6H15H4yt 90G dm ext4
│ └─docker-8:1-34019796-5wXXVSJSgfX48QySzzqpaw 110G dm ext4
└─serviced-serviced--pool_tdata 172.3G lvm
└─serviced-serviced--pool 172.3G lvm
├─docker-8:1-34019796-2gPEaR5Rxq9uRF6H15H4yt 90G dm ext4
└─docker-8:1-34019796-5wXXVSJSgfX48QySzzqpaw 110G dm ext4

------------------------------
Arthur
------------------------------

Subject:	RE: Disk layout in virtual machine
Author:	Denny Hoff
Posted:	2019-03-17 15:13

Are you installing from the iso? If so did you give the machine 512G of storage to work with? If you didn't it does not work because it does not layout the disks properly. An indicator would be if the installer stopped at the options page while installing CentOS. If everything is correct it does not pause for your input. Short answer it needs 512G of disk space and more than 16G ram.

------------------------------
Denny Hoff
Round Rock TX
------------------------------

Subject:	Disk layout in virtual machine
Author:	Fredrik
Posted:	2019-03-07 08:43

Disk layout in virtual machine