[one-users] Hosts not monitored
Alexandru - Florian Antonescu
florinantonescu at gmail.com
Fri Oct 7 05:00:37 PDT 2011
This problem is persisting even re-installation of OpenNebula 3.0.
I have tried to enable debugging by exporting ONE_MAD_DEBUG but I see no
extra messages logged to oned.log and no new file created in var folder.
Everything appears to be working properly, except that it doesn't.
These are the messages logged to var/oned.log
Fri Oct 7 09:18:53 2011 [InM][I]: Monitoring host zrhs9 (0)
Fri Oct 7 09:18:55 2011 [InM][I]: ExitCode: 0
Fri Oct 7 09:18:59 2011 [ReM][D]: HostPoolInfo method invoked
>From here it would seem that the monitoring code is executed properly.
Also, when I run onehost show 0 this is what is displayed:
HOST 0 INFORMATION
ID : 0
NAME : zrhs69
STATE : INIT
IM_MAD : im_kvm
VM_MAD : vmm_kvm
TM_MAD : tm_shared
HOST SHARES
MAX MEM : 0
USED MEM (REAL) : 0
USED MEM (ALLOCATED) : 0
MAX CPU : 0
USED CPU (REAL) : 0
USED CPU (ALLOCATED) : 0
RUNNING VMS : 0
MONITORING INFORMATION
The monitoring information is missing and no extra error message is
displayed.
Can someone give me some help with debugging this?
Best regards,
Florian
On Thu, Oct 6, 2011 at 3:14 PM, Alexandru - Florian Antonescu <
florinantonescu at gmail.com> wrote:
> Hello,
>
> After digging though the scripts, I reached the point were the
> one_im_exec.rb ruby script is called and from here I couldn't follow
> anymore.
> When running the script I don't get any output, and if I interrupt the
> script I get the following output.
> Can someone help me identify what is going on?
>
> ./lib/mads/one_im_exec.rb -r 0 -t 15 kvm
> ^C/srv/cloud/one/lib/ruby/ActionManager.rb:168:in `wait': Interrupt
> from /srv/cloud/one/lib/ruby/ActionManager.rb:168:in
> `start_listener'
> from /srv/cloud/one/lib/ruby/ActionManager.rb:166:in `synchronize'
> from /srv/cloud/one/lib/ruby/ActionManager.rb:166:in
> `start_listener'
> from /srv/cloud/one/lib/ruby/OpenNebulaDriver.rb:300:in
> `start_driver'
> from ./lib/mads/one_im_exec.rb:117
>
> Best regards,
> Florian
>
>
> On Thu, Oct 6, 2011 at 12:30 PM, Valentin Bud <valentin.bud at gmail.com>wrote:
>
>>
>>
>> On Thu, Oct 6, 2011 at 1:09 PM, Alexandru - Florian Antonescu <
>> florinantonescu at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I have recently installed OpenNebula 3.0 (from source) and noticed that
>>> the added hosts are not being monitored, they just remain in INIT state. In
>>> var/oned.log I see entries like these:
>>> Thu Oct 6 08:01:51 2011 [InM][I]: Monitoring host zrhs69 (2)
>>> Thu Oct 6 08:01:51 2011 [InM][I]: Monitoring host zrhs6a (3)
>>> Thu Oct 6 08:02:06 2011 [ReM][D]: HostPoolInfo method invoked
>>> oneadmin user is able to ssh into the hosts without a password.
>>>
>>> After looking in etc/im_kvm folder I saw that it is empty. Is this
>>> normal? How are hosts being monitored in OpenNebula 3.0 ?
>>>
>>> Can anyone give me a hint on how to proceed?
>>>
>>> Best regards,
>>> Florian
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>> Hello Florian,
>>
>> In /etc/one/oned.conf at the " KVM Information Driver Manager
>> Configuration " section:
>> IM_MAD = [
>> name = "im_kvm",
>> executable = "one_im_ssh",
>> arguments = "-r 0 -t 15 kvm" ]
>>
>> The executable one_im_ssh is located in /usr/lib/one/mads
>> or $ONE_LOCATION/lib/mads, depends if you installed OpenNebula self
>> contained on in root (/).
>> The one_im_ssh script sets $MAD_LOCATION and
>> executes $MAD_LOCATION/one_im_exec $*. Maybe you can find out what happens
>> following the logic found in those scripts.
>>
>> The monitoring part works for me. I have ONE3.0 on Debian Squeeze (6.0.2)
>> as frontend. The nodes are also Debian 6.0.2 with qemu-kvm 0.12.5
>> and libvirt 0.8.3-5.
>>
>> Have a great day,
>> v
>>
>>
>> --
>> network warrior
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20111007/1fdcb106/attachment-0003.htm>
More information about the Users
mailing list