Marking Invalid as i've not been able to reproduce this, and the stack
seems to be a confusing mismatch of packages.
Thanks for reporting, and do raise further issues you encounter.
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Invalid
--
CLC database stop running, unable to
@bukhary, Apologies for the delay in response to this. I note you
mentioned that you compiled 1.6.2 for Lucid. Can you clarify if you
have used Lucid packages from the normal archive, or actually compiled
it yourself?
Thanks.
--
CLC database stop running, unable to recover by reloading
You mention running 9.10 and using 1.6.2, but 9.10 has 1.6.0... Could you
precise what versions you're running with exactly ? (dpkg -l | grep euca)
There were a few improvements in this area on 1.6.2, any chance you could try
out on Lucid ?
** Changed in: eucalyptus (Ubuntu)
Status: New
we compiled from source and install on ubuntu karmic. We will give it a
try to install it. But for the time being it is a bit expensive for us
to test.We have so called running production of it. Do you have any
opinion on this problem? thanks.
--
CLC database stop running, unable to recover by
Well, that's clearly an unsupported use case. Running lucid's eucalyptus
on top of karmic's Java libraries is... risky at best. Especially around
hsqldb where a few key changes have happened. That doesn't mean there
isn't a bug, it's just that unless you reproduce it on pure lucid, we
can't really
** Attachment added: cloud-output.log
http://launchpadlibrarian.net/45627212/cloud-output.log
--
CLC database stop running, unable to recover by reloading
https://bugs.launchpad.net/bugs/570504
You received this bug notification because you are a member of Ubuntu
Server Team, which is
The second cloud-output.log is cloud-debug.log. My bad.
--
CLC database stop running, unable to recover by reloading
https://bugs.launchpad.net/bugs/570504
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
What worries me here is that, after this crash, and we restart the CLC
somehow, it send out request to Cluster Controller to remove the
iptables routing, ip aliases and even VLAN router on my interface. After
recovery, all instances are running but without network access to it.
--
CLC database
