[Bug 444352] Re: DB deadlock on reboot prevents UEC from working, temporarily

[Thierry Carrez]

** Description changed:

  Installed 20091006, works alright.
  Rebooted the cloud/cluster controller at 09:46
  Started an instance (i-45410877) at 09:48:06
  The instance stayed at pending (without an IP address assigned), then terminated.
  cloud-output.log shows an apparent DB deadlock condition.
  
  Next one started couldn't get a reservation ("Trying to allocate an address which is already pending")
  Next one started worked.
  
  See cloud-output.log that shows the first two tries. Let me know if you
  need more.
  
  ==================
  Karmic release notes:
  
  UEC might refuse to serve the first requests received after boot
  
- After a UEC boot the system may not answer correctly returning "503
- Forbidden" errors to client requests. This is cause by a database
- deadlock condition which is automatically cleared after some retries. To
- workaround this issue you can restart eucalyptus after boot on the
- cluster controller by running "sudo restart eucalyptus" (444352).
+ After a UEC boot the system may not answer correctly, returning for
+ example "403 Forbidden" errors to client requests. This is cause by a
+ database deadlock condition which is automatically cleared after some
+ retries. To workaround this issue you can restart eucalyptus after boot
+ on the cluster controller by running "sudo restart eucalyptus" (444352).
  
  ==================

-- 
DB deadlock on reboot prevents UEC from working, temporarily
https://bugs.launchpad.net/bugs/444352
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.