DNS issue causing CRON jobs to fail because of timeout
We were using OpenDNS instead of GoogleDNS on our Digital Ocean Server. Looks like some outrage in the DNS in Google and OpenDNS is causing the following time out erros
NoMethodError: undefined method `fb_error_code' for #<Faraday::ConnectionFailed>
I have changed the following configuration
# /etc/resolv.conf nameserver 22.214.171.124 nameserver 126.96.36.199
# /etc/network/interfaces dns-nameservers 188.8.131.52 184.108.40.206
and rebooted the system. But The sidekiq which used to normally take 1-2 min is not taking over 20mins to complete and throwing a lot of errors.