On a fresh install of front-end and node controller the cloud works as
expected:
ubu...@frontend:/var/log/eucalyptus$ euca-describe-availability-zones verbose
AVAILABILITYZONEtorsten 192.168.1.103
AVAILABILITYZONE|- vm types free / max cpu ram disk
AVAILABILITYZONE
I think there is still an issue around re-registration of nodes, I did
fall into that hole once. We just need to reproduce it to pinpoint where
it comes from. Please confirm that it works for you on a fully-new
install, so that we can rename that bug "Re-registered NC fails to be
detected" :)
--
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
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 ? When you
deregistered/registered manually the node, did you get any error ? After
deregister, what do you have in /var/lib/eucalyptus/nodes.list ? Could
you reproduce o
After reinstallation nothing changes. I removed quiet and splash from the
kernel boot command line and see the following report:
init: eucalyptus-network (lo) main process (704) killed by TERM signal
--
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this bu
I confirm that on my cloud there is an eucalyptus-nc.conf on the node and it
reads
CC_NAME="torstentest"
I will reinstall the node controller next and see if the problem
persists.
--
[alpha3] NC fails to be detected.
https://bugs.launchpad.net/bugs/530091
You received this bug notification beca
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
[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
Thierry,
Agreed. My issue was actually different. I filed this under: Bug
#530937, and I have committed a fix for my issue to the tree.
I'm not sure what's going on with Torsten's issue. I'm going to
unassign myself from this bug for now.
** Changed in: eucalyptus (Ubuntu)
Assignee: Dust
@Dustin: In Torsten's logs, the publication is working alright, since
the node is detected on the CC's registration logs:
2010-02-26 15:10:29+01:00 | 2758 -> Calling node torstentest node 192.168.1.106
2010-02-26 15:10:30+01:00 | 2758 -> euca_conf --register-nodes returned 0
Also eucalyptus/clust
I believe I've tracked down where this problem was introduced:
http://bazaar.launchpad.net/~ubuntu-core-
dev/eucalyptus/ubuntu/revision/909
My nodes don't have [ -f "/etc/eucalyptus/eucalyptus-nc.conf" ], so the
publication job isn't starting.
This is because the debconf key/value for eucalyptus
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
--
[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.
I'm confirming this.
I have a new UEC setup this morning from the current archive.
CLC+WC+CC+SC, and 4xNC.
The CLC was definitely up and running and serving the preseed.conf
before the NCs were installed.
The NCs installed correctly, and they have the CLC's ssh key in
/var/lib/eucalyptus/.ssh/au
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://
Anything in euca_test_nc.log or 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
Ubu
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/53009
Everything looks good on the install side... Maybe try sudo euca_conf
--deregister-nodes "IP" && sudo euca_conf --register-nodes "IP" and see
if you get any error ?
If it succeeds, it's probably an issue on the NC side, do you get
anything in the NC logs ?
--
[alpha3] NC fails to be detected.
ht
I'm pretty sure I waited for the front-end to be ready, e.g. euca-
describe-availability-zones verbose returns a good output. I attach the
registration log from the front-end.
On the node the authorized_keys file contain a good key for the
frontend. As user eucalyptus on the front-end I can do a p
There are some changes in the nodes registration process. It should now
work automatically and not require "discover-nodes". You can look into
the CC's /var/log/eucalyptus/registration.log if it detected the NC and
(if yes) what the euca_conf --register-nodes command returned.
>From your last atte
18 matches
Mail list logo
