If the previous bundle has not succeeded the next trap is sent in 30 minutes not regarding on what interval was configured. On your master instance there was a hanged bundle process so every subsequent trap didn't succeed.
On Jan 23, 5:15 pm, Arie Fishler <[email protected]> wrote: > ok....it still seems odd to me that I did not have this kind of problems > before switching to the lvm version. > > And what's with that trap being issued every 30 minutes instead of the > configured time (now 2 hours on my farm)? > > Thanks for checking! > > On Fri, Jan 23, 2009 at 5:12 PM, Nickolas Toursky <[email protected]> wrote: > > > The terminated master was hanged on disk operations - it happens > > sometimes with Amazon instances. > > When hanged master went down, slave promoted itself as master and > > works well since that time. Data bundles are being performed without > > problems. > > > On Jan 23, 12:41 pm, afishler <[email protected]> wrote: > > > thanks. And last log lines before it died are again related to the > > > bundling failure > > > 23-01-2009 04:13:43 ERROR i-03b6356a/trap-mysql-data-bundle.sh > > > Failed to bundle MySQL data. > > > 23-01-2009 04:12:28 ERROR i-03b6356a/trap-mysql-data-bundle.sh > > > Snapshot creation failed! > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
