I have created a local repository to install Xen on Centos -6.4 . I have followed the steps to install and download the xen dependecies from this link
http://www.howtoforge.com/virtualization-with-xen-on-centos-6.2-x86_64-paravirtualization-and-hardware-virtualization
When I install from local repository it has installed successfully with no errors. But When I rebooted it is not able to boot completely but i am able to login in that machine. I have started the Xend service manually but when I am given xm list command I am getting this error :
Error: Unable to connect to xend: No such file or directory. Is xend running?
I am not able to resolve this . Kindly help me how can i resolve this problem.
Thanks
Have you verified if Xend is running.
service xend status
(or)
ps -ef|grep xend
also verify
service libvirtd status
Related
We have three Ubuntu (14.04 and 18.04) servers and vasd service is not installed by default in our servers. When I try to check vas service status I'm getting the below error as those directory (/opt/quest/bin) and service are not installed.
/opt/quest/bin/vastool status
-su: /opt/quest/bin/vastool: No such file or directory
I need to install vas service and I need to get the above directories automatically. Can someone please help me to install this?
i have installed Nagios in ubuntu 18.04 by following the instructions given in digitalocean-nagios-installation-ubuntu18.04 . After installation, while we accessing nagios web-interface we are facing How can we resolve this?
I have installed DockerToolbox-1.12.2.exe in Windows 7 from https://github.com/docker/toolbox/releases/tag/v1.12.2 link. After installation, if I try to launch Kitamatic, I am getting
Error: connect ENOENT //./pipe/docker_engine.
I have tried RETRY SETUP and USE VIRTUALBOX options available, but didn't helped much. Can anyone suggest, how to proceed?
Because on Windows 7, docker is not supported native. So, you must have Virtual Box installed on your machine. If it is not already installed, you can re-run the docker toolbox installer, it asks you to install the Oracle VirtualBox with installation.
If it is already installed on your machine, open it and check if there is any default VM created in it and what is the error you are facing when you click on Use VirtualBox?
Using Centos 6.6 and 7 and deciding to move to centos 7 as there are some issues using docker with centos 6.6 (reboot issues for me) and i'm trying to pull the current centos image from docker. (should just be docker pull centos)
However because i already had a docker image of centos installed on the 6.6 virtual machine, i thought it conflicts with the one im trying to pull on the centos 7. It states that the image (f1b something) is already being used on the system and is causing the download to not go through. Simply going over to the centos 6.6 and trying to remove the images (which would be labeled as none by the way, thus you have to do docker images -a),even with force, does nothing. The only solution so far to this is to do a full removal of docker and its dependencies, and reinstall it which should come package free.
Of course this is not the solution i want. One of two things can happen. Either a way to make the two of them to coexist, or a way to remove the current one without removing any other current images. Or if I am not getting this right, take an entirely different approach.
EDIT+1: Ok heres the actual error im receiving when doing the the docker pull...
f1b...: download complete
f1b...:error downloading dependant layers
c85...:Downloading [>
7322...: Error pulling image (latest) from docker.io/centos, endpoint :https://registry-1.docker.io/v1,Dr
7322...:Error pulling image (latest) from docker.io/centos, Driver devicemapper failed to create image rootfs
FATA[0012] Error pulling image (latest) from docker.io/centos, Driver device mapper failed to create image rootfs f1b...:error running DeviceCreate (createSnapDevice) dm_task_run failed
And looking over the problem more im not so sure if its because of the centos 6.6 like i had initially thought despite sharing the same ID's.
EDIT +2: Stranger still is that the fatal error codes keeps changing (im assuming those are FATA[0012]?)
http://docker-sean.readthedocs.org/en/latest/chapter1.html
Theres a config file that needs to be changed for centos 7 docker users which happened to be applying the following change
OPTIONS='-g /docker/data -p /var/run/docker.pid'
in the vim/vi file of /etc/sysconfig/docker.
I swear docker is going to be the death of me...
EDIT +1: Ok lets remap the solution to the following starting from a new centos 7 machine...
yum install docker
service docker start
docker pull centos
ERROR
systemctl enable docker.service
ERROR?
sudo systemctl enable docker.service
systemctl start docker.service
ERROR?
yum remove docker
yum install epel-release.noarch
yum install docker-io
vim /etc/sysconfig/docker
OPTIONS='-g /docker/data -p /var/run/docker.pid'
service docker restart
docker pull centos
and thats how i got docker to work on the new VM if i mapped it correctly.
Also one of the commands i might have used was a thin_check. Somebody used it to verify docker in this link
EDIT +2:
Oh wow, this would explain even better whats happening here. See, the docker server can be installed straight out of the box with centos 7, however the daemon must still be installed from epel. As a reminder, the daemon is the item that actually runs the docker service. The server just allows docker to connect to the internet and view its repositories. Link is right here.
I am following given upload-a-vhd help document to create my openSuse linux vhd:
https://www.windowsazure.com/en-us/manage/linux/common-tasks/upload-a-vhd/
After I installed linux agent (waagent), i am not able to launch waagent in the vhd. When I try "sudo waagent" it return an error and command never execute. I tried installing waagent multiple times in vhd but still problem persist.
Any idea what could be wrong?
This is a known issues with OpenSUSE Linux agent as in OpenSUSE you will need to use sudo /usr/sbin/waagent instead of sudo waagent as the bash shell is not the default shell used in that Image right now.
Please try above and let me know if your problem is resolved.