[one-users] cannot locate backend for Nebula
Ruben S. Montero
rubensm at dacya.ucm.es
Sat Apr 26 02:59:26 PDT 2008
Hi,
It seems that your having problems loading the information driver. This driver
is used to get information about the hosts and configured through oned.conf
with:
IM_MAD=[name="one_im",executable="bin/one_im_ssh"...
At the beginning of the $ONE_LOCATION/VAR/one.log you should see something
like
[Nm][I]: Loading Information Manager drivers.
[Nm][I]: Loading driver: one_im
[Nm][I]: Driver one_im loaded
Probably ONE could not load the driver. So please could you try to start it
manually:
1.- (using the account that runs oned) Execute in a shell the program for the
im (as configured in oned.conf). This program does not return anything just
waits for commands.
2.- Write the initialization command (INIT), the driver should answer
with "INIT SUCCESS"
3.- Monitor a host (MONITOR 0 blade30) where blade30 is the name of your host.
The driver should answer with the monitor information
For example:
$ one_im_ssh etc/one_im_ssh.conf
INUIT
INUIT SUCCESS
MONITOR 0 vnode1
MONITOR SUCCESS 0 ARCH=i686,NAME=vnode1,MODELNAME="Intel(R) Core(TM)2 Duo"
Let see if that works for your setup. It should provide useful info when it
fails.
Best Regards and Thank you for your feedback!
Ruben
On Friday 25 April 2008 21:32:21 Wang, Lizhe wrote:
> Hi,
> I got some error information in the one.log
>
> ---------------------------------------------------------------------------
>--------- Sat Apr 26 08:37:05 2008 [DiM][D]: Allocating a new VM
> Sat Apr 26 08:37:16 2008 [InM][I]: Monitoring host blade30 (1)
> Sat Apr 26 08:37:16 2008 [InM][E]: Could not find information driver one_im
> Sat Apr 26 08:37:46 2008 [InM][I]: Monitoring host blade30 (1)
> Sat Apr 26 08:37:46 2008 [InM][E]: Could not find information driver one_im
> Sat Apr 26 08:38:16 2008 [InM][I]: Monitoring host blade30 (1)
> Sat Apr 26 08:38:16 2008 [InM][E]: Could not find information driver one_im
> Sat Apr 26 08:38:46 2008 [InM][I]: Monitoring host blade30 (1)
> Sat Apr 26 08:38:46 2008 [InM][E]: Could not find information driver one_im
>
>
> ---------------------------------------------------------------------------
>-------------
>
> Blade30 is now our backend.
> Can you give some advices?
>
>
> Best regards,
>
> ----------------------------------------------
> Lizhe Wang
> Institute for Scientific Computing (IWR)
> Research Center Karlsruhe (FZK)
> Hermann-von-Helmholtz-Platz 1
> D-76344 Eggenstein-Leopoldshafen, Germany
>
> Tel: 0049-(0)7247-82-6304
> Fax: 0049-(0)7247-82-4972
> e-mail: Lizhe.Wang at iwr.fzk.de
> Office: Zi A-203, IWR, FZK
> ----------------------------------------------
>
>
>
> -----Original Message-----
> From: Javier Fontan [mailto:jfontan at fdi.ucm.es]
> Sent: Mon 4/14/2008 12:20
> To: Wang, Lizhe
> Cc: users at lists.opennebula.org
> Subject: Re: [one-users] cannot locate backend for Nebula
>
>
> Hello,
>
> Seems that oned can not access cloud3 machine using ssh. Could you
> verify that you can ssh to cloud3 from your frontend machine and it
> does not ask for password? Use the same user as the one that is
> running oned. It could also be that the ssh hostkey from your
> frontend is not in the knownhosts file from cloud3, this can be
> easilly added connecting using ssh from cloud3 to your frontend
> machine. It will ask you if you want to add the key.
>
> Tell us if this works for you.
>
> Bye
>
> On Apr 13, 2008, at 7:12 PM, Wang, Lizhe wrote:
> > Hello:
> > I just installed Nebula on one frontend and one backend.
> > I found my virtual machines on backend is also pending.
> > It seems that ONE cannot find my backend server is available.
> > Following are some information.
> > Can you help?
> >
> >
> >
> > Best regards,
> > Lizhe
> > ----------------------------------------------------------------------
> > --------------------------------------
> >
> > 1)
> > onehost list
> > HID NAME RVM TCPU FCPU ACPU
> > TMEM FMEM
> > 0 cloud3 0 100 100
> > 0 0
> > 2)
> >
> > ID NAME STAT CPU MEM HOSTNAME TIME
> > 0 pend 0 0 00 19:50:02
> > 1 pend 0 0 00 19:46:59
> > 2 pend 0 0 00 00:25:38
> > 3) one.log :
> >
> >
> > Mon Apr 14 00:32:37 2008 [ONE][I]: Init Log system
> > Mon Apr 14 00:32:37 2008 [ONE][I]:
> > ----------------------------------------------
> > Mon Apr 14 00:32:37 2008 [ONE][I]: OpenNEbula Configuration
> > File
> > Mon Apr 14 00:32:37 2008 [ONE][I]:
> > ----------------------------------------------
> > Mon Apr 14 00:32:37 2008 [ONE][I]:
> > HOST_MONITORING_INTERVAL=10
> > IM_MAD=ARGUMENTS=etc/one_im_ssh.conf,EXECUTABLE=bin/
> > one_im_ssh,NAME=one_im,OWNER=oneadmin
> > MANAGER_TIMER=30
> > PORT=2633
> > VM_DIR=/opt/nebula/ONE/var
> > VM_MAD=EXECUTABLE=bin/one_vmm_xen,NAME=one_vmm,OWNER=oneadmin
> > VM_POLLING_INTERVAL=10
> > VM_RDIR=/opt/nebula/ONE/var
> > Mon Apr 14 00:32:37 2008 [ONE][I]: Bootstraping OpenNEbula database.
> > Mon Apr 14 00:32:37 2008 [ONE][E]: SQL command was: CREATE TABLE
> > vmpool (oid INTEGER PRIMARY KEY,aid INTEGER,tid INTEGER,uid
> > INTEGER,priority INTEGER,reschedule INTEGER,last_reschedule
> > INTEGER,last_poll INTEGER, template INTEGER,state INTEGER,lcm_state
> > INTEGER,stime INTEGER,etime INTEGER,deploy_id TEXT,memory
> > INTEGER,cpu INTEGER,net_tx INTEGER,net_rx INTEGER), error: table
> > vmpool already exists
> > Mon Apr 14 00:32:37 2008 [ONE][E]: SQL command was: CREATE TABLE
> > vm_template (id INTEGER, name TEXT, type INTEGER, value TEXT),
> > error: table vm_template already exists
> > Mon Apr 14 00:32:37 2008 [ONE][E]: SQL command was: CREATE TABLE
> > history (oid INTEGER,seq INTEGER,hostname TEXT,vm_dir TEXT,hid
> > INTEGER,hsid INTEGER,vmmad TEXT,tmmad TEXT,stime INTEGER,etime
> > INTEGER,pstime INTEGER,petime INTEGER,rstime INTEGER,retime
> > INTEGER,estime INTEGER,eetime INTEGER,reason INTEGER), error: table
> > history already exists
> > Mon Apr 14 00:32:37 2008 [ONE][E]: SQL command was: CREATE TABLE
> > hostpool (hid INTEGER PRIMARY KEY,host_name TEXT,state
> > INTEGER,hsids TEXT,im_mad TEXT,vm_mad TEXT,tm_mad
> > TEXT,last_mon_time INTEGER,managed INTEGER), error: table hostpool
> > already exists
> > Mon Apr 14 00:32:37 2008 [ONE][E]: SQL command was: CREATE TABLE
> > host_attributes (id INTEGER, name TEXT, type INTEGER, value TEXT,
> > PRIMARY KEY(id,name)), error: table host_attributes already exists
> > Mon Apr 14 00:32:37 2008 [ONE][E]: SQL command was: CREATE TABLE
> > hostshares (hsid INTEGER PRIMARY KEY,name TEXT, endpoint
> > TEXT,priority INTEGER,disk_usage INTEGER,mem_usage
> > INTEGER,cpu_usage INTEGER,max_disk INTEGER,max_mem INTEGER,max_cpu
> > INTEGER,running_vms INTEGER), error: table hostshares already exists
> > Mon Apr 14 00:32:37 2008 [VMM][I]: Starting Virtual Machine Manager...
> > Mon Apr 14 00:32:37 2008 [LCM][I]: Starting Life-cycle Manager...
> > Mon Apr 14 00:32:37 2008 [VMM][I]: Virtual Machine Manager started.
> > Mon Apr 14 00:32:37 2008 [LCM][I]: Life-cycle Manager started.
> > Mon Apr 14 00:32:37 2008 [InM][I]: Starting Information Manager...
> > Mon Apr 14 00:32:37 2008 [TrM][I]: Starting Transfer Manager...
> > Mon Apr 14 00:32:37 2008 [DiM][I]: Starting Dispatch Manager...
> > Mon Apr 14 00:32:37 2008 [ReM][I]: Starting Request Manager...
> > Mon Apr 14 00:32:37 2008 [InM][I]: Information Manager started.
> > Mon Apr 14 00:32:37 2008 [TrM][I]: Transfer Manager started.
> > Mon Apr 14 00:32:37 2008 [DiM][I]: Dispatch Manager started.
> > Mon Apr 14 00:32:37 2008 [ReM][I]: Request Manager started.
> > Mon Apr 14 00:32:37 2008 [ReM][I]: Starting XML-RPC server, port
> > 2633 ...
> > Mon Apr 14 00:32:39 2008 [InM][I]: Loading Information Manager
> > drivers.
> > Mon Apr 14 00:32:39 2008 [InM][I]: Loading driver: one_im
> > Mon Apr 14 00:32:39 2008 [InM][I]: Driver one_im loaded
> > Mon Apr 14 00:32:39 2008 [VMM][I]: Loading Virtual Machine Manager
> > drivers for user 0 .
> > Mon Apr 14 00:32:39 2008 [VMM][I]: Loading driver: one_vmm
> > Mon Apr 14 00:32:39 2008 [VMM][I]: Driver one_vmm loaded
> > Mon Apr 14 00:33:07 2008 [InM][I]: Monitoring host cloud3 (0)
> > Mon Apr 14 00:33:07 2008 [InM][E]: Error monitoring host 0 :
> > MONITOR FAILURE 0
> >
> > Mon Apr 14 00:33:37 2008 [InM][I]: Monitoring host cloud3 (0)
> > Mon Apr 14 00:33:37 2008 [InM][E]: Error monitoring host 0 :
> > MONITOR FAILURE 0
> >
> >
> > 4) sched.log:
> >
> > Mon Apr 14 00:34:07 2008 [HOST][D]: Discovered Hosts : 0
> > Mon Apr 14 00:34:07 2008 [VM][D]: Pending virtual machines : 0 1 2
> > Mon Apr 14 00:34:07 2008 [RANK][W]: No rank defined for VM
> > Mon Apr 14 00:34:07 2008 [RANK][W]: No rank defined for VM
> > Mon Apr 14 00:34:07 2008 [RANK][W]: No rank defined for VM
> > Mon Apr 14 00:34:07 2008 [SCHED][I]: Select hosts
> > PRI HID HSID
> > -------------------
> > Virtual Machine: 0
> >
> > Virtual Machine: 1
> >
> > Virtual Machine: 2
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
> --
> Javier Fontan, Grid 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
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
More information about the Users
mailing list