Errors at startup are hidden behind the heartbeat file problem
When there is a problem at startup (invalid connection credentials, for instance), the problem doed not appear until you stop manually (Control-C) the bot, because another exception is seen first:
% ./bot.py
2018-06-18 09:35:29,654 - ERROR - Invalid value in heartbeat file /home/dnsresolver/dns-bot-65vc5i6o.heartbeat: ""
2018-06-18 09:35:29,655 - ERROR - No more heartbeats, kill 17088
2018-06-18 09:35:38,666 - ERROR - Invalid value in heartbeat file /home/dnsresolver/dns-bot-bv6qqmmj.heartbeat: ""
2018-06-18 09:35:38,666 - ERROR - No more heartbeats, kill 17090
2018-06-18 09:35:47,678 - ERROR - Invalid value in heartbeat file /home/dnsresolver/dns-bot-6nzsdfu8.heartbeat: ""
2018-06-18 09:35:47,678 - ERROR - No more heartbeats, kill 17092
^C2018-06-18 09:35:50,676 - CRITICAL - Unexpected error in the driver "Specified client id directly, but did not supply secret"
Traceback (most recent call last):
File "./bot.py", line 242, in <module>
time.sleep(TIMER_DELAY)
KeyboardInterrupt