Greetings, We're having trouble reproducing this problem on our lucid systems against eucalyptus-cloud-1.6.2~bzr1124-0ubuntu3. We think that the issue is possibly related to some process startup behavior, but it would be great to get some more system information or a process by which the issue can often be triggered - some questions follow, the answers to which will help us try to reproduce:
1.) does this condition appear on a fresh boot (i.e. there are definitely no prior eucalyptus-cloud processes running when a new eucalyptus-cloud process is started)? 2.) does this condition appear when there is certainly the primary network interface up and configured? 3.) does this condition on 'start eucalyptus-cloud', 'restart eucalyptus-cloud' or both? 4.) do you see the condition when the cloud/walrus/sc are all on the same system or is this a stand-alone cloud service (or some other topology)? 5.) does this happen after a cloud has been configured/working or is it always during the initial setup (during registration of other components)? If we can trap the problem a bit further, we'll surely be able to find the solution! regards -dan -- eucalyptus-cloud doesn't reply to requests https://bugs.launchpad.net/bugs/503180 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
