Urgent Kadira Update

arunoda · May 19, 2015, 3:31am

Hi,

Today, we had an issue with connecting to Kadira mostly from apps hosted at modulus. But it turns out that, it’s not a modulus problem but a problem on the AWS DNS resolver. It couldn’t identify kadira’s DNS entry which is engine.kadira.io.

So, we’ve added another DNS entry point for kadira called enginex.kadira.io and it’ll fix the issue.

Since this is an AWS issue, this affects most of the Kadira deployments including apps hosted on *.meteor.com, modulus and heroku.

How to get the fix

Option 1 - Simply update kadira to the latest version (2.20.6)
Option 2 - Update kadira endpoint, if you can’t update your meteor app - https://gist.github.com/arunoda/554cfc3111267a8a7600

Thanks.

meonkeys · May 19, 2015, 4:28am

Thanks for the heads-up. I don’t understand the cause for the problem, though. Why did the domain name suddenly start returning NXDOMAIN? Was a DNS record inadvertently deleted?

arunoda · May 19, 2015, 4:32am

Yesterday, we update a DNS entry. We do it time to time.

Somehow, it got updated everywhere but not in AWS’s resolver.
That was the issue.

andrejsm · May 19, 2015, 7:05am

An email with warning and explanations should be sent to all your customers.

andrejsm · May 19, 2015, 7:58am

My apologies. Found the email in spam folder.

arunoda · May 19, 2015, 7:59am

Oh! That’s unfortunate.