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 188.8.131.52 nameserver 184.108.40.206
# /etc/network/interfaces dns-nameservers 220.127.116.11 18.104.22.168
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.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×