[one-users] Error monitoring host
Harishbabu Nagaraj
Harishbabu_Nagaraj at mindtree.com
Thu Mar 26 07:16:32 PDT 2009
Hi Raul,
Thanks for the immediate reply. We could be able to solve the issue by adding oneadmin user in the sudoer file.
We are exploring further on deploying the VM's. We will come back if we have any issues.
Thanks and Regards,
Harish
-----Original Message-----
From: users-bounces at lists.opennebula.org [mailto:users-bounces at lists.opennebula.org] On Behalf Of Raul Sampedro
Sent: Thursday, March 26, 2009 1:07 PM
To: Harishbabu Nagaraj
Cc: Rajaraman Swaminathan; users at lists.opennebula.org
Subject: Re: [one-users] Error monitoring host
Hello Harishbabu,
It seems to be a problem sending the script to the host, have you
checked that your oneadmin user belongs to sudoer group?
If that is correct, edit the file $ONE_LOCATION/lib/im_probes/xen.rb
and on line '50' check that appears:
when 'free_memory'
not
when 'max_free_memory'
cheers!
2009/3/26 Harishbabu Nagaraj <Harishbabu_Nagaraj at mindtree.com>:
> Hi,
>
>
>
> We have installed OpenNebula on our system. We are facing some issues. Any
> help would be very much appreciated.
>
>
>
> OpenNebula Server
>
> Hostname - FEDORA.MINDTREE.COM and OS - Fedora 8
>
>
>
> OpenNebula Cluster Node
>
> Hostname - A4MD09479.MINDTREE.COM and OS - RHEL 5
>
>
>
> We are configuring as per the QuickStart guide given in the OpenNebula
> documentation web site. All the configurations are proceeding fine. We could
> able to SSH from the OpenNebula
>
> server to the cluster node without any password.
>
>
>
> [oneadmin at FEDORA ~]# onehost create A4MD09479.MINDTREE.COM im_xen vmm_xen
> tm_ssh
>
>
>
> [oneadmin at FEDORA ~]# onehost list
>
>
>
> HID NAME RVM TCPU FCPU ACPU TMEM FMEM STAT
>
> 0 A4MD09479.MINDTREE.COM 0 100 on
>
>
>
> We are not getting any updated values in TCPU, FCPU, TMEM and FMEM fields.
> Any help is deeply appreciated.
>
>
>
> Here is the oned.log file:
>
>
>
> Wed Mar 25 18:24:44 2009 [ONE][I]: Init OpenNebula Log system
>
> Wed Mar 25 18:24:44 2009 [ONE][I]: Log Level: 3
> [0=ERROR,1=WARNING,2=INFO,3=DEBUG]
>
> Wed Mar 25 18:24:44 2009 [ONE][I]:
> ----------------------------------------------
>
> Wed Mar 25 18:24:44 2009 [ONE][I]: OpenNebula Configuration File
>
> Wed Mar 25 18:24:44 2009 [ONE][I]:
> ----------------------------------------------
>
> Wed Mar 25 18:24:44 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=/opt/nebula/ONE/var/
>
>
> VM_MAD=DEFAULT=vmm_xen/vmm_xen.conf,EXECUTABLE=one_vmm_xen,NAME=vmm_xen,TYPE=xen
>
> VM_POLLING_INTERVAL=10
>
> --------------------------------------------
>
> Wed Mar 25 18:24:44 2009 [ONE][I]: Bootstraping OpenNebula database.
>
> Wed Mar 25 18:24:44 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
>
> Wed Mar 25 18:24:44 2009 [ONE][E]: SQL command was: CREATE TABLE
> vm_attributes (id INTEGER, name TEXT, type INTEGER, value TEXT), error:
> table vm_attributes already exists
>
> Wed Mar 25 18:24:44 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
>
> Wed Mar 25 18:24:44 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
>
> Wed Mar 25 18:24:44 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
>
> Wed Mar 25 18:24:44 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
>
> Wed Mar 25 18:24:44 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
>
> Wed Mar 25 18:24:44 2009 [ONE][E]: SQL command was: CREATE TABLE vn_template
> (id INTEGER, name TEXT, type INTEGER, value TEXT), error: table vn_template
> already exists
>
> Wed Mar 25 18:24:44 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
>
> Wed Mar 25 18:24:44 2009 [VMM][I]: Starting Virtual Machine Manager...
>
> Wed Mar 25 18:24:44 2009 [LCM][I]: Starting Life-cycle Manager...
>
> Wed Mar 25 18:24:44 2009 [InM][I]: Starting Information Manager...
>
> Wed Mar 25 18:24:44 2009 [TrM][I]: Starting Transfer Manager...
>
> Wed Mar 25 18:24:44 2009 [DiM][I]: Starting Dispatch Manager...
>
> Wed Mar 25 18:24:44 2009 [ReM][I]: Starting Request Manager...
>
> Wed Mar 25 18:24:44 2009 [ReM][I]: Starting XML-RPC server, port 2633 ...
>
> Wed Mar 25 18:24:44 2009 [VMM][I]: Virtual Machine Manager started.
>
> Wed Mar 25 18:24:44 2009 [LCM][I]: Life-cycle Manager started.
>
> Wed Mar 25 18:24:44 2009 [InM][I]: Information Manager started.
>
> Wed Mar 25 18:24:44 2009 [TrM][I]: Transfer Manager started.
>
> Wed Mar 25 18:24:44 2009 [DiM][I]: Dispatch Manager started.
>
> Wed Mar 25 18:24:44 2009 [ReM][I]: Starting Request Manager...
>
> Wed Mar 25 18:24:44 2009 [ReM][I]: Starting XML-RPC server, port 2633 ...
>
> Wed Mar 25 18:24:44 2009 [VMM][I]: Virtual Machine Manager started.
>
> Wed Mar 25 18:24:44 2009 [LCM][I]: Life-cycle Manager started.
>
> Wed Mar 25 18:24:44 2009 [InM][I]: Information Manager started.
>
> Wed Mar 25 18:24:44 2009 [TrM][I]: Transfer Manager started.
>
> Wed Mar 25 18:24:44 2009 [DiM][I]: Dispatch Manager started.
>
> Wed Mar 25 18:24:44 2009 [ReM][I]: Request Manager started.
>
> Wed Mar 25 18:24:46 2009 [InM][I]: Loading Information Manager drivers.
>
> Wed Mar 25 18:24:46 2009 [InM][I]: Loading driver: im_xen
>
> Wed Mar 25 18:24:46 2009 [InM][I]: Driver im_xen loaded
>
> Wed Mar 25 18:24:46 2009 [VMM][I]: Loading Virtual Machine Manager drivers.
>
> Wed Mar 25 18:24:46 2009 [VMM][I]: Loading driver: vmm_xen (XEN)
>
> Wed Mar 25 18:24:46 2009 [VMM][I]: Driver vmm_xen loaded.
>
> Wed Mar 25 18:24:46 2009 [TM][I]: Loading Transfer Manager drivers.
>
> Wed Mar 25 18:24:46 2009 [VMM][I]: Loading driver: tm_ssh
>
> Wed Mar 25 18:24:46 2009 [TM][I]: Driver tm_ssh loaded.
>
> Wed Mar 25 18:25:14 2009 [InM][I]: Monitoring host A4MDO9479 (3)
>
> Wed Mar 25 18:25:14 2009 [InM][E]: Error monitoring host 3 : MONITOR FAILURE
> 3 Can not send script to remote machine: A4MDO9479
>
>
>
> Wed Mar 25 18:25:44 2009 [InM][I]: Monitoring host A4MDO9479 (3)
>
> Wed Mar 25 18:25:44 2009 [InM][E]: Error monitoring host 3 : MONITOR FAILURE
> 3 Can not send script to remote machine: A4MDO9479
>
>
>
> Wed Mar 25 18:26:14 2009 [InM][I]: Monitoring host A4MDO9479 (3)
>
> Wed Mar 25 18:26:14 2009 [InM][E]: Error monitoring host 3 : MONITOR FAILURE
> 3 Can not send script to remote machine: A4MDO9479
>
>
>
> Wed Mar 25 18:26:44 2009 [InM][I]: Monitoring host A4MDO9479 (3)
>
> Wed Mar 25 18:26:44 2009 [InM][E]: Error monitoring host 3 : MONITOR FAILURE
> 3 Can not send script to remote machine: A4MDO9479
>
>
>
> Wed Mar 25 18:26:44 2009 [ReM][D]: HostAllocate method invoked
>
> Wed Mar 25 18:27:14 2009 [InM][I]: Monitoring host A4MDO9479 (3)
>
> Wed Mar 25 18:27:14 2009 [InM][I]: Monitoring host A4MD09479.MINDTREE.COM
> (4)
>
> Wed Mar 25 18:27:14 2009 [InM][E]: Error monitoring host 3 : MONITOR FAILURE
> 3 Can not send script to remote machine: A4MDO9479
>
>
>
> Wed Mar 25 18:27:15 2009 [InM][E]: Error monitoring host 4 : MONITOR FAILURE
> 4 Can not send script to remote machine: A4MD09479.MINDTREE.COM
>
>
>
> Let us know if you need any more details.
>
> Thanks in Advance.
>
>
>
> Thanks and Regards,
>
> Harish
>
>
>
> ________________________________
> http://www.mindtree.com/email/disclaimer.html
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
_______________________________________________
Users mailing list
Users at lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
http://www.mindtree.com/email/disclaimer.html
More information about the Users
mailing list