[one-users] Can not send script to remote machine

[Tino Vazquez]

Hi there,

Yes, you need to be able to do ssh passwordlessly.

Another reason why OpenNebula may not be able to send the script is
that in the remote nodes, a /tmp/im_ne_scripts directory already
exists with permissions set so oneadmin cannot place the scripts over
there. If this is the case, try erasing that directory.

Regards,

-Tino

--
Constantino Vázquez, Grid Technology Engineer/Researcher:
http://www.dsa-research.org/tinova
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org



On Thu, Oct 8, 2009 at 2:01 PM, Liu, Zhentao
<Zhentao.Liu at fokus.fraunhofer.de> wrote:
> Hi, Tino
>
> As you said, I have run oned daemon as <oneadmin>. I still get the same
> error.
>
> But maybe there is a problem that the at the first, <oneadmin> directory was
> /var/lib/one in the remote node, but this directory is not suitable for me
> to do an "ssh 193.175.134.144" passwordlessly.  So I changed the directory
> to /home/oneadmin and put authorized_keys in /home/oneadmin/.ssh, and then I
> can do "ssh 193.175.134.144" passwordlessly. Does this affect something?
>
> Thanks
>
> Zhentao
>
>
> -----Original Message-----
> From: tinova79 at gmail.com on behalf of Tino Vazquez
> Sent: Thu 10/8/2009 11:27 AM
> To: Liu, Zhentao
> Cc: users at lists.opennebula.org
> Subject: Re: [one-users] Can not send script to remote machine
>
> Hi Zhentao,
>
> Are you running 'oned' as root? The recommended way of running the
> oned daemon is as <oneadmin>.
>
> In any case, the user that runs the process needs to be able to do an
> "ssh 193.175.134.144" passwordlessly. Can you confirm this is the
> case?
>
> Regards,
>
> -Tino
>
> --
> Constantino Vázquez, Grid Technology Engineer/Researcher:
> http://www.dsa-research.org/tinova
> DSA Research Group: http://dsa-research.org
> Globus GridWay Metascheduler: http://www.GridWay.org
> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>
>
>
> On Wed, Oct 7, 2009 at 10:55 AM, Liu, Zhentao
> <Zhentao.Liu at fokus.fraunhofer.de> wrote:
>> Hello,
>>
>> Why I can't get the CPU source of remote node?
>> ps: 193.175.134.144 is my remote physical node.
>>
>> oned.log:
>>
>> -----------------------------------------------------------------------------------------------------------------------------------------
>>
>> Wed Oct  7 10:44:28 2009 [InM][I]: Monitoring host 193.175.134.144 (4)
>> Wed Oct  7 10:46:07 2009 [InM][E]: Error monitoring host 4 : MONITOR
>> FAILURE
>> 4 Can not send script to remote machine: 193.175.134.144
>>
>> -----------------------------------------------------------------------------------------------------------------------------------------
>>
>> sched.log:
>>
>> -----------------------------------------------------------------
>> Wed Oct  7 10:51:00 2009 [HOST][D]: Discovered Hosts (enabled): 4
>> Wed Oct  7 10:51:00 2009 [VM][D]: Pending virtual machines : 0
>> Wed Oct  7 10:51:00 2009 [RANK][W]: No rank defined for VM
>> Wed Oct  7 10:51:00 2009 [SCHED][I]: Select hosts
>>         PRI     HID     HSID
>>         -------------------
>>
>>
>> --------------------------------------------------------------------
>>
>> onehost list:
>>
>>
>> --------------------------------------------------------------------------------
>> root at taresian:/var/log/one# onehost list
>>  HID NAME                      RVM   TCPU   FCPU   ACPU    TMEM    FMEM
>> STAT
>>    4 193.175.134.144             0             0    100         7593960
>> on
>>
>> --------------------------------------------------------------------------------
>>
>>
>> Any ideas?
>>
>> Thanks
>>
>> Zhentao Liu
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>