![]() |
![]() |
Subject: | Error starting up serviced 1.1.1 |
Author: | [Not Specified] |
Posted: | 2016-03-28 13:06 |
Hi everyone,
I've run into an issue installing resource manager 5.1.1. Wewere running 5.0 but ran out of space, when trying to get the service back up and running after adding space, we ran into the issue of docker complaining about UUID of the data stores being out. In the end I opted to just do a fresh install of 5.1.1 instead of going through the hassle of trying to get the 5.0 machine upgraded.
Now On a fresh isntall of 5.1.1 I'm getting the following when I attempt to start serviced:
Unable to validate server options: Use of devicemapper loop back device is not allowed unless --allow-loop-back=true
Here's the output of docker info:
Containers: 0
Images: 0
Server Version: 1.9.0
Storage Driver: devicemapper
Pool Name: docker-docker--pool
Pool Blocksize: 65.54 kB
Base Device Size: 107.4 GB
Backing Filesystem: xfs
Data file:
Metadata file:
Data Space Used: 1.821 GB
Data Space Total: 96.54 GB
Data Space Available: 94.72 GB
Metadata Space Used: 1.315 MB
Metadata Space Total: 109.1 MB
Metadata Space Available: 107.7 MB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Library Version: 1.02.107-RHEL7 (2015-12-01)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.10.0-327.10.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 4
Total Memory: 23.39 GiB
Name: sfo1zen-hub-prod-01.nbttech.com
ID: 7HMH:FF2M:GL4I:DZKF:ON6P:BLMU:7ILH:MSXH:O6C4:PUVL:EU7N:SL3B
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Any one have any ideas
Subject: | remove |
Author: | [Not Specified] |
Posted: | 2016-03-28 13:33 |
try:
rm -rf /opt/serviced/var/volumes/.devicemapper
rm -rf /var/lib/docker/*
systemctl restart docker
systemctl restart serviced
newbie
Subject: | I have the same problem with |
Author: | [Not Specified] |
Posted: | 2016-04-06 03:57 |
I have the same problem with fresh install of 5.1.1 on similar CentOS 7 system.
Any help would be greatly appreciated.
< |
Previous Strugglingn to get into Control Center/Zenoss Core |
Next Zenoss 5 Installation Issue. |
> |