Re: [Bug 530091] Re: [alpha3] NC fails to be detected.

2010-03-03 Thread Torsten Spindler
On Wed, 2010-03-03 at 09:48 +, Thierry Carrez wrote:
 Looking at the authorized_keys, might be a node re-registration issue.
 Did you register the same Node IP with the CC in the past ? 

Yes, it was registered before.


 When you
 deregistered/registered manually the node, did you get any error ?

Nope. But when I register the node it is not listed anywhere, e.g.

$ sudo euca_conf --register-nodes 192.168.1.106

INFO: We expect all nodes to have eucalyptus installed
in //var/lib/eucalyptus/keys for key synchronization.

Trying rsync to sync keys with 192.168.1.106...The authenticity of
host '192.168.1.106 (192.168.1.106)' can't be established.
RSA key fingerprint is 5e:3f:83:e2:83:18:c5:f9:04:3f:a1:f2:9a:94:30:4e.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.106' (RSA) to the list of known
hosts.
eucalyp...@192.168.1.106's password: 
done.

ubu...@frontend:/etc/eucalyptus$ grep -ri 106 *
grep: preseed/preseed.conf: Permission denied


  After
 deregister, what do you have in /var/lib/eucalyptus/nodes.list ? 

sudo euca_conf --deregister-nodes 192.168.1.106
[sudo] password for ubuntu: 
SUCCESS: removed node '192.168.1.106'
ubu...@frontend:~$ cd /etc/eucalyptus/
ubu...@frontend:/etc/eucalyptus$ grep 106 *
eucalyptus.conf:NODES=192.168.1.106

I added it manually to eucalyptus.conf in the past, will remove it.


 Could
 you reproduce on a full new setup (reinstall the CC)? (I can't)

I will do so, first reinstall the CC, then the NC and report back if the
situation changes.


 The process is:
 0/ NC Installer copies CC key to NC authorized_keys
 1/ NC publishes its existence
 2/ CC picks up the publication
 3/ CC runs euca_conf --register-nodes
 4/ euca_conf --register-nodes syncs up the eucalyptus CC keys to the NC 
 /var/lib/eucalyptus/keys
 5/ euca_conf --register-nodes adds IP to the CC nodes.list
 6/ NC picks up keys and starts up, starts writing up messages to nc.log
 
 From your logs it looks like 0-3 is working alright, and that 6 never
 happens. Could you tell where it stops ?
 
 ** Changed in: eucalyptus (Ubuntu)
Importance: High = Medium
 
 ** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Incomplete


-- 
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 530091] Re: [alpha3] NC fails to be detected.

2010-03-02 Thread Torsten Spindler
I tried the deregister and register but not change in the overall
situation.

For the logs on the node controller, I don't see nc.log:

ubu...@node01:/var/log/eucalyptus$ ls
axis2c.log  euca_test_nc.log  httpd-nc_error_log

-- 
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 530091] Re: [alpha3] NC fails to be detected.

2010-03-02 Thread Torsten Spindler
Nothing of interest in there, I attach the two


** Attachment added: httpd-nc_error_log
   http://launchpadlibrarian.net/39962164/httpd-nc_error_log

** Attachment added: euca_test_nc.log
   http://launchpadlibrarian.net/39962165/euca_test_nc.log

-- 
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs