hi,
I have a problem in verbose configuration. I followed all the steps regarding installation of cloud,cc and nc and have also downloaded the credentials. But while running verbose command i am getting the output as follow.
euca-describe-availability-zones verbose
AVAILABILITYZONE mehul 192.168.9.141
AVAILABILITYZONE |- vm types free / max cpu ram disk
AVAILABILITYZONE |- m1.small 0000 / 0000 1 128 2
AVAILABILITYZONE |- c1.medium 0000 / 0000 1 256 5
AVAILABILITYZONE |- m1.large 0000 / 0000 2 512 10
AVAILABILITYZONE |- m1.xlarge 0000 / 0000 2 1024 20
AVAILABILITYZONE |- c1.xlarge 0000 / 0000 4 2048 20
here free/max values are not appropriate as what i think.. can anyone guide me in that?
Yes , sir my nc is running..
First i started my nc then from clc(and cc as both are on same m/c) i tried to discover nodes using command
"sudo euca_conf --no-rsync --discover-nodes" . In that process node is getting discovered by CLC and i am also able to copy ssh key as shown in the process but when i run the " euca-describe-availability-zones verbose" command i got the output as shown above. Is there any other way to check whether nc is running or not?...
And sir i am using UEC on ubuntu 9.10 and i followed the procedure given on ubuntu site.
https://help.ubuntu.com/community/UEC/PackageInstall
==============
euca_test_nc.log file
==============
This is perl, v5.10.0 built for i486-linux-gnu-thread-multi
Copyright 1987-2007, 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.
total_memory=3092
nr_cores=2
==================
httpd-nc_erro_log file
==================
[Sun Feb 07 04:45:29 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Sun Feb 07 05:12:01 2010] [notice] caught SIGTERM, shutting down
[Sun Feb 07 05:12:02 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Sun Feb 07 05:20:06 2010] [notice] caught SIGTERM, shutting down
[Sun Feb 07 05:20:07 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Sun Feb 07 11:03:53 2010] [notice] caught SIGTERM, shutting down
[Mon Feb 08 07:08:16 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 09 02:49:35 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 09 06:01:32 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 09 12:24:03 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 09 12:29:49 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 09 13:08:49 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 09 13:24:32 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Fri Feb 12 04:04:46 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Fri Feb 12 04:16:55 2010] [notice] caught SIGTERM, shutting down
[Fri Feb 12 13:06:35 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Fri Feb 12 13:07:48 2010] [notice] caught SIGTERM, shutting down
[Sat Feb 13 01:16:31 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Sun Feb 14 03:17:40 2010] [notice] caught SIGTERM, shutting down
[Mon Feb 15 06:07:09 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Mon Feb 15 11:40:15 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 16 02:44:53 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 16 09:02:03 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 16 09:06:46 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 16 09:24:49 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 16 11:33:14 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 16 14:54:05 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 16 15:12:07 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 16 15:15:49 2010] [notice] caught SIGTERM, shutting down
[Tue Feb 16 20:22:35 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Feb 16 20:22:54 2010] [notice] caught SIGTERM, shutting down
[Thu Feb 18 00:20:38 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Thu Feb 18 00:21:14 2010] [notice] caught SIGTERM, shutting down
[Thu Feb 18 10:33:45 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Fri Feb 19 07:42:25 2010] [notice] caught SIGTERM, shutting down
[Sun Feb 21 12:56:48 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Sun Feb 21 12:57:05 2010] [notice] caught SIGTERM, shutting down
[Mon Feb 22 12:44:14 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
[Tue Mar 09 06:16:41 2010] [notice] caught SIGTERM, shutting down
[Tue Mar 09 22:51:16 2010] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0 configured -- resuming normal operations
Hello,
can you check that the nc.log is growing (you can tail -f nc.log and see it scrolling by)? If so, can you restart the nc.log and post here the beginning (after the restart) of the file? It will have information on your systems (max disk, max mem and max cores). Also, on the CLC/CC machine, can you post a snippet of the cc.log? There should be information on the cc trying to contact the nc.
cheers
graziano