Re: [Xen-users] Problemi using vif-route script

[Giorgio Mossa <mossa@xxxxxxxxxxxxxxxxxxxx>]

Hi,
I've tryed to do as you suggested and added the lines to vif-route script
by the way I cannot get where the script fails and there's also 
something strange it seems that the script is called four times.


Here the vif-route.log file's content, do you see anything useful?

/etc/xen/scripts/vif-route online type_if=vif at ven 26 ott 2012, 14.14.23, CEST
++ dirname /etc/xen/scripts/vif-route
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+++ dirname /etc/xen/scripts/vif-route
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ '[' -n '' ']'
++++ dirname /etc/xen/scripts/vif-route
+++ dir=/etc/xen/scripts
+++ . /etc/xen/scripts/hotplugpath.sh
++++ SBINDIR=/usr/sbin
++++ BINDIR=/usr/bin
++++ LIBEXEC=/usr/lib/xen/bin
++++ LIBDIR=/usr/lib
++++ SHAREDIR=/usr/share
++++ PRIVATE_BINDIR=/usr/lib/xen/bin
++++ XENFIRMWAREDIR=/usr/lib/xen/boot
++++ XEN_CONFIG_DIR=/etc/xen
++++ XEN_SCRIPT_DIR=/etc/xen/scripts
++++ XEN_LOCK_DIR=/var/lock
++++ XEN_RUN_DIR=/var/run/xen
++++ XEN_PAGING_DIR=/var/lib/xen/xenpaging
+++ . /etc/xen/scripts/logging.sh
+++ . /etc/xen/scripts/xen-script-common.sh
++++ set -e
+++ . /etc/xen/scripts/locking.sh
++++ LOCK_BASEDIR=/var/run/xen-hotplug
+++ exec
/etc/xen/scripts/vif-route online type_if=vif at Fri Oct 26 14:14:23 CEST 2012
++ dirname /etc/xen/scripts/vif-route
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+++ dirname /etc/xen/scripts/vif-route
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ '[' -n 1 ']'
+++ xenstore-read libxl/disable_udev
+++ exit 0
/etc/xen/scripts/vif-route offline type_if=vif at Fri Oct 26 14:14:23 CEST 2012
/etc/xen/scripts/vif-route offline type_if=vif at ven 26 ott 2012, 14.14.23, 
CEST
++ dirname /etc/xen/scripts/vif-route
++ dirname /etc/xen/scripts/vif-route
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+++ dirname /etc/xen/scripts/vif-route
+++ dirname /etc/xen/scripts/vif-route
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ '[' -n 1 ']'
+++ xenstore-read libxl/disable_udev
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ '[' -n '' ']'
+++ exit 0
++++ dirname /etc/xen/scripts/vif-route
+++ dir=/etc/xen/scripts
+++ . /etc/xen/scripts/hotplugpath.sh
++++ SBINDIR=/usr/sbin
++++ BINDIR=/usr/bin
++++ LIBEXEC=/usr/lib/xen/bin
++++ LIBDIR=/usr/lib
++++ SHAREDIR=/usr/share
++++ PRIVATE_BINDIR=/usr/lib/xen/bin
++++ XENFIRMWAREDIR=/usr/lib/xen/boot
++++ XEN_CONFIG_DIR=/etc/xen
++++ XEN_SCRIPT_DIR=/etc/xen/scripts
++++ XEN_LOCK_DIR=/var/lock
++++ XEN_RUN_DIR=/var/run/xen
++++ XEN_PAGING_DIR=/var/lib/xen/xenpaging
+++ . /etc/xen/scripts/logging.sh
+++ . /etc/xen/scripts/xen-script-common.sh
++++ set -e
+++ . /etc/xen/scripts/locking.sh
++++ LOCK_BASEDIR=/var/run/xen-hotplug
+++ exec



On Fri, Oct 26, 2012 at 08:40:41AM +0100, Ian Campbell wrote:
> On Fri, 2012-10-26 at 08:28 +0100, Giorgio Mossa wrote:
> >  libxl: error: libxl_device.c:978:device_hotplug_child_death_cb:
> > script: /etc/xen/scripts/vif-route failed; error detected.
> 
> This means that a command has failed somewhere in the script (i.e. 'set
> -e' and 'trap .. ERR' are in use). Sadly it doesn't give much hint as to
> what/where it has failed.
> 
> To debug this I would add near the top of vif-route something like:
>       exec 1>>/tmp/vif-route.log
>       exec 2>&1
>       echo "$0 $@ at `date`
>       set -x
> 
> and then try it and look and see what the logs have to say.
> 
> Ian.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users