[Bug 483634] [NEW] master can't receive info from node

Public bug reported: hello using ubuntu 9.10 server and a very basic/simple installation, the compute node is not seen in the cluster. tried to restart services, reboot on both master and node : nothing. see the logs and config attached. euca-describe-availability-zones verbose AVAILABILITYZONE

[Bug 483634] Re: master can't receive info from node

** Attachment added: master node conf and logs http://launchpadlibrarian.net/35750451/master_logs-conf.tar.bz2 -- master can't receive info from node https://bugs.launchpad.net/bugs/483634 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 483634] Re: master can't receive info from node

It may be because the server config was missing VNET_DNS parameter : [Mon Nov 16 11:23:10 2009][012652][EUCAWARN ] VNET_DNS is not defined in config [Mon Nov 16 11:23:10 2009][012652][EUCAFATAL ] bad network parameters, must fix before system will work [Mon Nov 16 11:23:10

[Bug 483634] [NEW] master can't receive info from node

Public bug reported: hello using ubuntu 9.10 server and a very basic/simple installation, the compute node is not seen in the cluster. tried to restart services, reboot on both master and node : nothing. see the logs and config attached. euca-describe-availability-zones verbose AVAILABILITYZONE

[Bug 483634] Re: master can't receive info from node

** Attachment added: master node conf and logs http://launchpadlibrarian.net/35750451/master_logs-conf.tar.bz2 -- master can't receive info from node https://bugs.launchpad.net/bugs/483634 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 483634] Re: master can't receive info from node

** Attachment added: node logs and conf http://launchpadlibrarian.net/35750463/node_logs-conf.tar.bz2 -- master can't receive info from node https://bugs.launchpad.net/bugs/483634 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 483634] Re: master can't receive info from node

It may be because the server config was missing VNET_DNS parameter : [Mon Nov 16 11:23:10 2009][012652][EUCAWARN ] VNET_DNS is not defined in config [Mon Nov 16 11:23:10 2009][012652][EUCAFATAL ] bad network parameters, must fix before system will work [Mon Nov 16 11:23:10

[Bug 472785] [NEW] can't register SC

Public bug reported: hello my master is .1, i'd like to move the storage to .2 .2 was installed with ubuntu 9.10 regular server, plus packages SC and WALRUS. i have a temporary password for eucalyptus user on .2 ( https://help.ubuntu.com/community/UEC/PackageInstall then

[Bug 473062] [NEW] new node has eucalyptus-nc down (apache config ?)

Public bug reported: Hello Just installed a node, ubuntu 9.10 final version. During installation, the node mode is selected by default. when i try discover the node from the master, i can't find it. the nc service is not running by default ... ubu...@node2:~$ netstat -a|grep LIST tcp0

[Bug 473062] Re: new node has eucalyptus-nc down (apache config ?)

** Attachment added: system and eucalyptus logs http://launchpadlibrarian.net/35041750/logs.tar -- new node has eucalyptus-nc down (apache config ?) https://bugs.launchpad.net/bugs/473062 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 472785] [NEW] can't register SC

Public bug reported: hello my master is .1, i'd like to move the storage to .2 .2 was installed with ubuntu 9.10 regular server, plus packages SC and WALRUS. i have a temporary password for eucalyptus user on .2 ( https://help.ubuntu.com/community/UEC/PackageInstall then

[Bug 462140] Re: maximum 61 running instances, others shutting down

new tests : v27.1 rebooted cluster, creating security groups, VNET_ADDRSPERNET=512 VNET_PUBLICIPS=192.168.3.1-192.168.5.254 launching vms : export EMI=emi-4158125D euca-run-instances $EMI -n 50 -k mykey -t c1.medium --addressing private --group group2 euca-run-instances $EMI -n 50 -k mykey -t

[Bug 462140] Re: maximum 61 running instances, others shutting down

** Attachment added: symptom : instances being terminated by security groups http://launchpadlibrarian.net/34539244/instances.weird -- maximum 61 running instances, others shutting down https://bugs.launchpad.net/bugs/462140 You received this bug notification because you are a member of

[Bug 462140] Re: maximum 61 running instances, others shutting down

VNET_ADDRSPERNET=32 see logs_3.tar.bz2 ... result : euca-describe-instances |grep running|wc = 75 export EMI=emi-4158125D euca-add-group -d Group 10 group10 euca-add-group -d Group 11 group11 euca-add-group -d Group 12 group12 euca-add-group -d Group 13 group13 euca-add-group -d Group 14 group14

[Bug 462140] Re: maximum 61 running instances, others shutting down

new tests : v27.1 rebooted cluster, creating security groups, VNET_ADDRSPERNET=512 VNET_PUBLICIPS=192.168.3.1-192.168.5.254 launching vms : export EMI=emi-4158125D euca-run-instances $EMI -n 50 -k mykey -t c1.medium --addressing private --group group2 euca-run-instances $EMI -n 50 -k mykey -t

[Bug 462140] Re: maximum 61 running instances, others shutting down

** Attachment added: symptom : instances being terminated by security groups http://launchpadlibrarian.net/34539244/instances.weird -- maximum 61 running instances, others shutting down https://bugs.launchpad.net/bugs/462140 You received this bug notification because you are a member of

[Bug 462140] Re: maximum 61 running instances, others shutting down

VNET_ADDRSPERNET=32 see logs_3.tar.bz2 ... result : euca-describe-instances |grep running|wc = 75 export EMI=emi-4158125D euca-add-group -d Group 10 group10 euca-add-group -d Group 11 group11 euca-add-group -d Group 12 group12 euca-add-group -d Group 13 group13 euca-add-group -d Group 14 group14

[Bug 462140] [NEW] maximum 61 running instances, others shutting down

Public bug reported: hello I have a cluster of 6 machines+master, 384 cores total, seen correctly by AVAILABILITYZONE : AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small 0090 / 0384 1128 2 But when i launch VMs, only 61 end up

[Bug 462140] Re: maximum 61 running instances, others shutting down

** Attachment added: logs and config files (together) http://launchpadlibrarian.net/34495573/log.tar.bz2 -- maximum 61 running instances, others shutting down https://bugs.launchpad.net/bugs/462140 You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 461092] Re: can't add more than 29 instances

thanks, changed VNET_ADDRSPERNET to 512 should have RTFM, sorry. now the problem is 61 instances, see https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/462140 -- can't add more than 29 instances https://bugs.launchpad.net/bugs/461092 You received this bug notification because you are a

[Bug 462140] Re: maximum 61 running instances, others shutting down

Neil, we are talking about 384 cores seen by the sum of all OSes (64 per node OS). No special trick to overprovisione the nodes. In the new intel machines Nehalem class, we have a technology called hyperthreading (remember pentium 4 ? same thing). There's 192 physical cores, but seen as 384

[Bug 462140] Re: maximum 61 running instances, others shutting down

hello The conf is in the attached tar file, but i changed the value from 32 (default) to 512 from the beginning of the install (i ran into this VNET_ADDRPERNET problem yesterday). 64 was never entered. I've just rebooted the entire cluster and ran more tests. I can have more than 61 instances

[Bug 462140] [NEW] maximum 61 running instances, others shutting down

Public bug reported: hello I have a cluster of 6 machines+master, 384 cores total, seen correctly by AVAILABILITYZONE : AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small 0090 / 0384 1128 2 But when i launch VMs, only 61 end up

[Bug 462140] Re: maximum 61 running instances, others shutting down

** Attachment added: logs and config files (together) http://launchpadlibrarian.net/34495573/log.tar.bz2 -- maximum 61 running instances, others shutting down https://bugs.launchpad.net/bugs/462140 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 461092] Re: can't add more than 29 instances

thanks, changed VNET_ADDRSPERNET to 512 should have RTFM, sorry. now the problem is 61 instances, see https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/462140 -- can't add more than 29 instances https://bugs.launchpad.net/bugs/461092 You received this bug notification because you are a

[Bug 462140] Re: maximum 61 running instances, others shutting down

Neil, we are talking about 384 cores seen by the sum of all OSes (64 per node OS). No special trick to overprovisione the nodes. In the new intel machines Nehalem class, we have a technology called hyperthreading (remember pentium 4 ? same thing). There's 192 physical cores, but seen as 384

[Bug 462140] Re: maximum 61 running instances, others shutting down

hello The conf is in the attached tar file, but i changed the value from 32 (default) to 512 from the beginning of the install (i ran into this VNET_ADDRPERNET problem yesterday). 64 was never entered. I've just rebooted the entire cluster and ran more tests. I can have more than 61 instances

[Bug 461092] [NEW] can't add more than 29 instances

Public bug reported: I launch 29 times the command euca-run-instances, and it works fine The 30th time, i get finishedVerify: Internal Error. But i have plenty of free vms in euca-describe-availability-zones verbose cores and memory are available My machine has 32 physical cores, and 64 seen by

[Bug 461092] Re: can't add more than 29 instances

** Attachment added: master node eucalyptus logs http://launchpadlibrarian.net/34412759/C%3A%5CDocuments%20and%20Settings%5Cpguermon%5CDesktop%5Clogs.tar.bz2 -- can't add more than 29 instances https://bugs.launchpad.net/bugs/461092 You received this bug notification because you are a

[Bug 461092] [NEW] can't add more than 29 instances

Public bug reported: I launch 29 times the command euca-run-instances, and it works fine The 30th time, i get finishedVerify: Internal Error. But i have plenty of free vms in euca-describe-availability-zones verbose cores and memory are available My machine has 32 physical cores, and 64 seen by

[Bug 461092] Re: can't add more than 29 instances

** Attachment added: master node eucalyptus logs http://launchpadlibrarian.net/34412759/C%3A%5CDocuments%20and%20Settings%5Cpguermon%5CDesktop%5Clogs.tar.bz2 -- can't add more than 29 instances https://bugs.launchpad.net/bugs/461092 You received this bug notification because you are a