[one-users] Information Retrieval Failure
Damien Cerbelaud
dcerbelaud at gmail.com
Mon Feb 23 10:19:10 PST 2009
Hi,
I had the same issue last week. Basically, sudo xm info needs to be
launched from an active console. You need to comment out the option
#default requiretty
in the /etc/sudoers file of your CentOS machine.
Damien
On Mon, Feb 23, 2009 at 9:55 AM, Miguel J. - Templeir <mjcampos at citic.es> wrote:
> Hello
>
> I have installed ONE, in FrontEnd Pc using this parameters:
>
> one-1.2.0.tar.gz | I have compiled with scons and I have
> installed using self contained installation.
>
> Ubuntu 8.04.1 NIS
> Software prerequisites: ruby sqlite3 libsqlite3-dev libsqlite3-ruby
> libxmlrpc-c3 libxmlrpc-c3-dev scons g++
>
> hostname: master-nebula
>
> -----------
>
> In Cluster Pc using this parameters:
>
> Centos 5.2 +
> NIS
> ruby sudo
> Xen 3.3.1
>
> hostname: nebula1
> -------------
> Both systems are updated.
>
> I have configured NIS Server in FrontEnd and NIS Client in Cluster, also
> ssh connection without authentification from FrontEnd to Cluster was
> configured.
>
> Then i tested ONE with this commands:
>
> oneadmin at master-nebula:~$ onehost create nebula1 im_xen vmm_xen tm_ssh
> oneadmin at master-nebula:~$ onehost list
> HID NAME RVM TCPU FCPU ACPU TMEM FMEM STAT
> 0 nebula1 0 0 100 on
>
> -------------------
> oned.log looks like this:
>
> Mon Feb 23 18:16:11 2009 [ONE][I]: Init OpenNebula Log system
> Mon Feb 23 18:16:11 2009 [ONE][I]: Log Level: 3
> [0=ERROR,1=WARNING,2=INFO,3=DEBUG]
> Mon Feb 23 18:16:11 2009 [ONE][I]:
> ----------------------------------------------
> Mon Feb 23 18:16:11 2009 [ONE][I]: OpenNebula Configuration File
> Mon Feb 23 18:16:11 2009 [ONE][I]:
> ----------------------------------------------
> Mon Feb 23 18:16:11 2009 [ONE][I]:
> --------------------------------------------
> DEBUG_LEVEL=3
> HOST_MONITORING_INTERVAL=10
>
> IM_MAD=ARGUMENTS=im_xen/im_xen.conf,DEFAULT=im_xen/im_xen.conf,EXECUTABLE=one_im_ssh,NAME=im_xen
> MAC_PREFIX=00:03
> MANAGER_TIMER=30
> NETWORK_SIZE=254
> PORT=2633
>
> TM_MAD=ARGUMENTS=tm_ssh/tm_ssh.conf,DEFAULT=tm_ssh/tm_ssh.conf,EXECUTABLE=one_tm,NAME=tm_ssh
> VM_DIR=/usr/local/nebula/var/
>
> VM_MAD=DEFAULT=vmm_xen/vmm_xen.conf,EXECUTABLE=one_vmm_xen,NAME=vmm_xen,TYPE=xen
> VM_POLLING_INTERVAL=10
> --------------------------------------------
> Mon Feb 23 18:16:11 2009 [ONE][I]: Bootstraping OpenNebula database.
> Mon Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE vm_pool
> (oid INTEGER PRIMARY KEY,uid INTEGER,last_poll INTEGER, template_id
> 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 vm_pool already exists
> Mon Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE
> vm_attributes (id INTEGER, name TEXT, type INTEGER, value TEXT), error:
> table vm_attributes already exists
> Mon Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE history
> (vid INTEGER,seq INTEGER,host_name TEXT,vm_dir TEXT,hid INTEGER,vm_mad
> TEXT,tm_mad TEXT,stime INTEGER,etime INTEGER,pstime INTEGER,petime
> INTEGER,rstime INTEGER,retime INTEGER,estime INTEGER,eetime INTEGER,reason
> INTEGER,PRIMARY KEY(vid,seq)), error: table history already exists
> Mon Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE host_pool
> (oid INTEGER PRIMARY KEY,host_name TEXT,state INTEGER,im_mad TEXT,vm_mad
> TEXT,tm_mad TEXT,last_mon_time INTEGER,managed INTEGER), error: table
> host_pool already exists
> Mon Feb 23 18:16:11 2009 [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 Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE host_shares
> (hid INTEGER PRIMARY KEY, endpoint TEXT,disk_usage INTEGER,mem_usage
> INTEGER,cpu_usage INTEGER,max_disk INTEGER,max_mem INTEGER,max_cpu
> INTEGER,running_vms INTEGER), error: table host_shares already exists
> Mon Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE
> network_pool (oid INTEGER,uid INTEGER, name TEXT PRIMARY KEY,type INTEGER,
> bridge TEXT), error: table network_pool already exists
> Mon Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE vn_template
> (id INTEGER, name TEXT, type INTEGER, value TEXT), error: table vn_template
> already exists
> Mon Feb 23 18:16:11 2009 [ONE][E]: SQL command was: CREATE TABLE leases (oid
> INTEGER,ip INTEGER, mac_prefix INTEGER,mac_suffix INTEGER,vid INTEGER, used
> INTEGER, PRIMARY KEY(oid,ip)), error: table leases already exists
> Mon Feb 23 18:16:11 2009 [VMM][I]: Starting Virtual Machine Manager...
> Mon Feb 23 18:16:11 2009 [VMM][I]: Virtual Machine Manager started.
> Mon Feb 23 18:16:11 2009 [LCM][I]: Starting Life-cycle Manager...
> Mon Feb 23 18:16:11 2009 [LCM][I]: Life-cycle Manager started.
> Mon Feb 23 18:16:11 2009 [InM][I]: Starting Information Manager...
> Mon Feb 23 18:16:11 2009 [InM][I]: Information Manager started.
> Mon Feb 23 18:16:11 2009 [TrM][I]: Starting Transfer Manager...
> Mon Feb 23 18:16:11 2009 [TrM][I]: Transfer Manager started.
> Mon Feb 23 18:16:11 2009 [DiM][I]: Starting Dispatch Manager...
> Mon Feb 23 18:16:11 2009 [DiM][I]: Dispatch Manager started.
> Mon Feb 23 18:16:11 2009 [ReM][I]: Starting Request Manager...
> Mon Feb 23 18:16:11 2009 [ReM][I]: Request Manager started.
> Mon Feb 23 18:16:11 2009 [ReM][I]: Starting XML-RPC server, port 2633 ...
> Mon Feb 23 18:16:13 2009 [InM][I]: Loading Information Manager drivers.
> Mon Feb 23 18:16:13 2009 [InM][I]: Loading driver: im_xen
> Mon Feb 23 18:16:13 2009 [InM][I]: Driver im_xen loaded
> Mon Feb 23 18:16:13 2009 [VMM][I]: Loading Virtual Machine Manager drivers.
> Mon Feb 23 18:16:13 2009 [VMM][I]: Loading driver: vmm_xen (XEN)
> Mon Feb 23 18:16:13 2009 [VMM][I]: Driver vmm_xen loaded.
> Mon Feb 23 18:16:13 2009 [TM][I]: Loading Transfer Manager drivers.
> Mon Feb 23 18:16:13 2009 [VMM][I]: Loading driver: tm_ssh
> Mon Feb 23 18:16:13 2009 [TM][I]: Driver tm_ssh loaded.
> Mon Feb 23 18:19:41 2009 [ReM][D]: HostAllocate method invoked
> Mon Feb 23 18:20:04 2009 [InM][I]: Monitoring host nebula1 (0)
> Mon Feb 23 18:20:08 2009 [InM][D]: Host 0 successfully monitored.
>
> All drivers seems to load succesfully.
>
> I have updated sqlite3 to sqlite3 3.5.9 (i thought that the old version of
> SQLite was causing the problem)
> but the problem persists.
>
> when i execute onehost show command i get this output:
> oneadmin at opennebula:~$ onehost show 7
> HID = 7
> HOSTNAME = nebula1
> IM MAD = im_xen
> VMM MAD = vmm_xen
> TM MAD = tm_ssh
> MANAGED = 1
> ATTRIBUTES
> ARCH=i686
> HOSTNAME=nebula1
> MODELNAME=Intel(R) Pentium(R) 4 CPU 3.00GHz
> HOST SHARES
> HID = 7
> ENDPOINT = MAX_CPU = 0
> MAX_MEMORY = 0
> MAX_DISK = 0
> CPU_USAGE = 0
> MEMORY_USAGE = 0
> DISK_USAGE = 0
> RUNNING_VMS = 0
>
> Hostname, modelname and architecture seems to be correct but there is no
> clue about XEN information. I have launched the script
> xen.rb that lives in im_probes directory in nebula1 machine and the script
> shows the desired info so i suspect the failure
> is somewhere while transfering the info. And i've tested the presence of the
> script in the tmp directory in nebula1
> machine.
>
> BTW i've executed the driver in its own and execute INIT and MONITOR, that's
> the output:
> $ /usr/lib/one/mads/one_im_ssh /etc/one/im_xen/im_xen.conf
> INIT
> INIT SUCCESS
> MONITOR 0 nebula1
> MONITOR SUCCESS 0 ARCH=i686,HOSTNAME=nebula1,MODELNAME="Intel(R) Pentium(R)
> 4 CPU 3.00GHz"
>
> so where is XEN info?? is causing this the problem?
> Thank you very much.
>
>
>
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
More information about the Users
mailing list