Hi there, On Mon, 27 Jun 2022, 16:51:55 +0200, David T-G wrote:
Freek, et al --
...and then Freek de Kruijf said... % % Op maandag 27 juni 2022 12:32:03 CEST schreef David T-G: % > ... % > uptime? Carlos usually has great ideas here :-) You might try adding % > some debug info into the script to give you a picture of the world each % > time cron kicks it off. What if you run the command manually oh, say, % > 1000 times with no waiting? % > % Tried it 1000 times, without waiting and a sleep 1. Both reported one issue, % respectively on count 450 and 179. [snip]
Oho! At least you can rule out cron, which makes things one step simpler. Yay.
Time to turn this back over to the experts. I'm just an out-of-work admin who fumbles around OK :-) But a big branch of the decision tree has just been pruned away, so I can feel like I helped.
this smells like what I have seen every once in a while when resolving host names with an IPv6 address. At least I don't have IPv6 available here, it ended up with error messages; this mostly happened with ntpd. @Freek: if you don't usually use IPv6 (or if you even can't), can you add a "-4" option to your "dig smtp.gmail.com" command? It helped for my case. HTH, cheers. l8er manfred