Comment 16 for bug 585108

No problem, if i get a error like this again i let you know.

On 22 December 2011 06:16, graziano obertelli <email address hidden>wrote:

> thanks for the confirmation: I will keep the bug incomplete for a bit
> longer in case of more feedback, then I will mark it invalid.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/585108
>
> Title:
> euca_conf --register-nodes returns 0 but the node is not registered
>
> Status in Eucalyptus:
> Incomplete
> Status in “eucalyptus” package in Ubuntu:
> Confirmed
> Status in “eucalyptus” source package in Lucid:
> New
>
> Bug description:
> Using ubuntu 10.04, i have eucalyptus-nc running in the node
> controller but does not have nc.log. In the cc, if i run euca_conf
> --discover-nodes it find no nodes. Even if i run euca_conf --register-
> nodes NODE_IP, i receive a success message (done), but no nodes are
> showed with euca_conf --list-nodes. euca-describe-availability-zones
> verbose returns 0/0 for all types.
>
> My hw configuration are with 2 machines, 1 clc, cc, sc and 1 nc.
>
> I've deregistered everything, cluster through web interface and node
> through command line, then rebooted clc/cc/sc and the nc. After
> reboot, the cluster was automatically registered, i changed the
> eucalytptus-cc.conf and the eucalyptus-sc.conf to c3cluster1 again.
> But euca_conf --list-nodes show no nodes. Even after --register-nodes
> 192.168.1.2 getting success message.
>
> Im sad because with ubuntu 9.10 everything was working and now with
> 10.04 it does not work for some unknow reason.
>
> I have the clc/cc and the nc linked through a hub. The clc/cc have 2
> NIC's, 1 public(10.1.2.x) and 1 private(192.168.1.X) that is used to
> comunicate with the node. In the hub i have a dhcp server that assigns
> IP's in the 10.1.2.X subnet, and it is the gw too. The network
> configuration in the NC is manual(192.168.1.2), in the private iface
> of CLC/CC is manual too(192.168.1.1) and the public iface is dhcp.
>
> Below goes all my logs and conf files, if with this you cant help me,
> there is no solution for me =/
>
> This is also discussed at
> http://forum.eucalyptus.com/forum/no-nclog#comment-11351
> CONFS:
>
> eucalytpus.conf - http://pastebin.com/w2BUzU2v
> eucalyptus.local.conf - http://pastebin.com/xBJSg5XS
> eucalyptus-cc.conf - CC_NAME="c3cluster1"
> eucalytpus-sc.conf - SC_NAME="c3cluster1"
> eucalytpus-ipaddr.conf - http://pastebin.com/xeAaYUZC
> httpd.conf - http://pastebin.com/8FctTYiX
> /etc/network/interfaces - http://pastebin.com/K59BWSDi
>
> LOGS:
> http-cc_error_log - http://pastebin.com/rU6ZJY9c
> axis2c.log - http://pastebin.com/8DF6s1VF
> cc.log - http://pastebin.com/K50x3aZr
> cloud-debug.log - http://pastebin.com/2jPR1X4S
> cloud-error.log - http://pastebin.com/BSQUSVZZ
> cloud-output.log - http://pastebin.com/26sudQh8
> registration.log - http://pastebin.com/UvWzs8DP
>
> If you check the cc.log, you will see that he is not updated since may
> 20, i think this is a problem right?
>
> Since now i thank you.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: eucalyptus-common 1.6.2-0ubuntu30
> ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2
> Uname: Linux 2.6.32-21-server x86_64
> .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="c3cluster1"
> Architecture: amd64
> Date: Mon May 24 14:08:30 2010
> InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64
> (20100427)
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: eucalyptus
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/eucalyptus/+bug/585108/+subscriptions
>

--
*MSc. Eng. Jônata Tyska Carvalho*
Engenheiro de Computação - Mestre em Modelagem Computacional
Telefone (+55) 53 9959.4874
Analista de TI do Centro de Ciências Computacionais - FURG
Sócio fundador da ElefanTI Tecnologia da Informação - www.elefanti.com.br