[one-users] trying to troubleshoot onevm shutdown/stop/restart

Thu Apr 28 15:55:41 PDT 2011

	Thank you for looking over my problem!

> Could you tell us what was the action that was being performed to the
> VM when it failed? To me it looks like stop but I am not sure about
> it.

onevm stop <VM_ID>

> It would be also helpful to take a peek into $ONE_LOCATION/var/config

DB=BACKEND=mysql,DB_NAME=xxxxx,PASSWD=xxxxx,SERVER=localhost,USER=oneadmin
DEBUG_LEVEL=3
DEFAULT_DEVICE_PREFIX=hd
DEFAULT_IMAGE_TYPE=OS
HM_MAD=EXECUTABLE=one_hm
HOST_MONITORING_INTERVAL=60
IMAGE_REPOSITORY_PATH=/srv/vm/images
IM_MAD=ARGUMENTS=kvm,EXECUTABLE=one_im_ssh,NAME=im_kvm
MAC_PREFIX=02:00
MANAGER_TIMER=15
NETWORK_SIZE=254
PORT=2633
SCRIPTS_REMOTE_DIR=/var/tmp/one
TM_MAD=ARGUMENTS=tm_nfs/tm_nfs.conf,EXECUTABLE=one_tm,NAME=tm_nfs
TM_MAD=ARGUMENTS=tm_flexclone-kvm/tm_flexclone-kvm.conf,EXECUTABLE=one_tm,NAME=tm_flexclone-kvm
VM_DIR=/srv/vm
VM_HOOK=ARGUMENTS=$VMID,COMMAND=image.rb,NAME=image,ON=DONE
VM_MAD=ARGUMENTS=kvm,DEFAULT=vmm_ssh/vmm_ssh_kvm.conf,EXECUTABLE=one_vmm_ssh,NAME=vmm_kvm,TYPE=kvm
VM_POLLING_INTERVAL=60
VNC_BASE_PORT=5900

>Also the VM directory in the frontend for self contained installation
>is always $ONE_LOCATION/var, if you want to have the images for
>running VMs stored in another place you can symlink that dir (var) to
>the desired directory.

As you can see, VM_DIR is set to a location outside $ONE_LOCATION

           Thanks,

John Nyhuis, 
jnyhuis at rim.com
Infrastructure Engineering Specialist
Desk: (813)-60556
External: (425)-208-0556
Desk #2073

-----Original Message-----
From: Javier Fontan [mailto:jfontan at gmail.com] 
Sent: Friday, April 15, 2011 2:08 AM
To: John Nyhuis
Cc: users at lists.opennebula.org
Subject: Re: [one-users] trying to troubleshoot onevm shutdown/stop/restart

Could you tell us what was the action that was being performed to the
VM when it failed? To me it looks like stop but I am not sure about
it.

It would be also helpful to take a peek into $ONE_LOCATION/var/config
(delete any password it may contain before sending it).

Also the VM directory in the frontend for self contained installation
is always $ONE_LOCATION/var, if you want to have the images for
running VMs stored in another place you can symlink that dir (var) to
the desired directory.

On Thu, Apr 14, 2011 at 11:28 PM, John Nyhuis <jnyhuis at rim.com> wrote:
>        Greetings,
>
>        I am trying to troubleshoot our OpenNebula 2.0 installation (w/ kvm) and would appreciate some help.
> When we run onevm shutdown <VID> or onevm stop <VID>, the VM fails to stop and enters the 'fail' state.  Once in this state, it can not be restarted using onevm restart or repaired in any way.  We have been deleting the vm and creating it again, which is time consuming and wasteful.   (We are using the $one_location=/srv/vm/ self contained option).
>
>
>        Examination of the vm.log of a failed vm reveals:
> Mon Apr 11 18:46:21 2011 [TM][I]: ERROR MESSAGE --8<------
> Mon Apr 11 18:46:21 2011 [TM][I]: mv: cannot stat `/srv/cloud/var/600/images': No such file or directory
> Mon Apr 11 18:46:21 2011 [TM][I]: ERROR MESSAGE ------>8--
> Mon Apr 11 18:46:21 2011 [TM][I]: ExitCode: 1
> Mon Apr 11 18:46:21 2011 [TM][I]: tm_mv.sh: Moving /srv/cloud/var/600/images
> Mon Apr 11 18:46:21 2011 [TM][I]: tm_mv.sh: ERROR: Command "mv /srv/cloud/var/600/images /srv/vm/600/images" failed.
> Mon Apr 11 18:46:21 2011 [TM][I]: tm_mv.sh: ERROR: mv: cannot stat `/srv/cloud/var/600/images': No such file or directory
> Mon Apr 11 18:46:21 2011 [TM][E]: Error excuting image transfer script: mv: cannot stat `/srv/cloud/var/600/images': No such file or directory
> Mon Apr 11 18:46:21 2011 [DiM][I]: New VM state is FAILED
>
> For some reason, onevm thinks the images are located at /srv/cloud/var/600/images.  The images are located in /srv/vm/<VID>/images/.  The create and delete options for onevm know how to find them there, but for some reason, the stop and shutdown options keep looking in the wrong place.
>
> I could manually create a link to the images directory to solve this, but with over 600 vm's, that's a bit painful, and we would have to remember to re-create the link with every new vm.
>
> Does anyone know where this location is set for onevm stop and onevm shutdown, as it is not in oned.conf or the env?
> The tm_mv.sh script is accepting the source and destination locations via stdin, but I don't know what is calling the tm_mv.sh script.
>
>
>           Thanks,
>
> John Nyhuis,
> jnyhuis at rim.com
> Infrastructure Engineering Specialist
> Desk: (813)-60556
> External: (425)-208-0556
> Desk #2073
>
>
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>

-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.