Pages

Tuesday, June 4, 2013

looking for euca2ools,error: failed to find required euca2ools - Eucalyptus 3.2

looking for euca2ools... error: failed to find required euca2ools - Eucalyptus 3.2


Currently I am working in Eucalyptus 3.2.

I have a single system with all the Eucalyptus components configured in that.

Cloud Controller, Cluster Controller, Walrus, Storage Controller,
Node Controller in the Same system.

I was able to install and configure Eucalyptus 3.2 from Source in
Debian (    BOSS GNU/Linux 2.0 (server) )after a hell lot of errors !.

I referred this blog for installing from the source,

http://mdshaonimran.wordpress.com/2012/10/31/eucalyptus-source-installation/



This blog was very much helpful  to me.

I configured all the components and only Node Controller was pending.

I am using Xen 4.1( xen-hypervisor-4.1-amd64 ) for Virtualization.

When I started Node controller,

/etc/init.d/eucalyptus-nc start

I ended up with following error ,

Starting Eucalyptus services: eucalyptus-nc

Node Controller cannot be started: errors in //var/log/eucalyptus/euca_test_nc.log


When I checked the log, It showed the following.

root@boss[console]#cat //var/log/eucalyptus/euca_test_nc.log

This is perl, v5.10.1 (*) built for x86_64-linux-gnu-thread-multi
(with 47 registered patches, see perl -V for more detail)

Copyright 1987-2009, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

looking for system utilities...
2013-06-05 11:03:21  INFO | detected grub 2
ok

looking for euca2ools...
error: failed to find required euca2ools



When  I searched google, I came across this website,

http://fossies.org/linux/misc/eucalyptus-3.1.2.tar.gz:a/eucalyptus-3.1.2/node/test_nc.c

Refer the lines,
211-216

Line Number 213,was having the fprintf statement
 
 fprintf (stderr, "error: failed to find required euca2ools\n");
 
 
The previous line, 212 is having the condition as follows
 
if (verify_helpers (helpers_name, NULL, 3) > 0) {
  
Now I checked the  helpers_name  variable.It contained 
 
  199     fprintf (stderr, "ok\n\nlooking for euca2ools...\n");
  200     static char * helpers_name [3] = {
  201         "euca-bundle-upload",
  202         "euca-check-bucket",
  203         "euca-delete-bundle"
  204     };
  205  

So when we are staring eucalyptus-nc, it checks for the existence of the command,
 
euca-bundle-upload
euca-check-bucket
euca-delete-bundle

Now I searched for the above commands in my system.
Some of the commands were located in 
/usr/local/bin 
 
I already had an older version of euca2ools

root@boss[~]#dpkg -l |grep euca2ools
ii  euca2ools         1.2-1     managing cloud instances for Eucalyptus

When I executed the command,euca-delete-bundle
I got the following error.
 
root@boss[~]#euca-delete-bundle 
Traceback (most recent call last):
  File "/usr/bin/euca-delete-bundle", line 37, in <module>
    from euca2ools import Euca2ool, FileValidationError, Util
ImportError: cannot import name Euca2ool



Now I checked location of this command,that was  referring to /usr/bin .
 
root@boss[~]#which euca-delete-bundle 
/usr/bin/euca-delete-bundle

Move the file to some other location.

mv /usr/bin/euca-delete-bundle /usr/bin/euca-delete-bundle.old
 
Then I replaced this link with 
ln -s  /usr/local/bin/euca-delete-bundle /usr/bin/

I did the same for the commands, euca-check-bucket and euca-delete-bundle

Also I updated the PATH variable in /root/.bashrc

export PATH=$PATH:/usr/local/bin

Now I exited from the terminal and opened a new terminal
Execute the following commands. 

source /root/.bashrc
/etc/init.d/eucalyptus-nc restart
Restarting Eucalyptus services
 
At last eucalyptus-nc started successfully ! 
 
Now I am proceeding to registering the nodes , uploading images and launching instances.
However I anticipate issues in the upcoming tasks ! .

No comments:

Post a Comment