Yes. But only if you’re in C.. .python, java , etc don’t have access to
res_init.
On Fri, Jun 5, 2015 at 2:46 PM, Dan Fandrich wrote:
> On Fri, Jun 05, 2015 at 11:38:05AM +0200, Markus "Shorty" Uckelmann wrote:
> > Am 30.05.2015 um 19:55 schrieb Florian Forster:
> > >Hi Shorty,
> >
> > Peace oc
On Fri, Jun 05, 2015 at 11:38:05AM +0200, Markus "Shorty" Uckelmann wrote:
> Am 30.05.2015 um 19:55 schrieb Florian Forster:
> >Hi Shorty,
>
> Peace octo,
>
> Thanks for the explanation.
>
> >the write_graphite plugin will call getaddrinfo(3) on every connection
> >attempt. How the name resoluti
Am 30.05.2015 um 19:55 schrieb Florian Forster:
Hi Shorty,
Peace octo,
Thanks for the explanation.
the write_graphite plugin will call getaddrinfo(3) on every connection
attempt. How the name resolution is done depends on the C library – on
many GNU/Linux systems DNS is one of multiple possi
Hi Shorty,
On Fri, May 29, 2015 at 09:05:53PM +0200, Markus "Shorty" Uckelmann wrote:
> So back to it and Collectd wasn't able to resolve it's Graphite host.
> So even after a few hours it didn't re-read /etc/resolv.conf.
the write_graphite plugin will call getaddrinfo(3) on every connection
atte
this is an issue with glibc, NOT with collectd. It’s not fun but most
versions of glibc do not do resolv.conf reloading. I agree it’s not fun
but this is a bug in glibc not collectd.
Long story short, don’t ever change your DNS servers IPs.. otherwise it’s
just no fun.
On Fri, May 29, 2015 at 1
Hi all,
It just happened that one of our servers had a wrong resolv.conf. We
corrected this. A few hours later we saw that we had no metrics from
Collectd from this server. So back to it and Collectd wasn't able to
resolve it's Graphite host. So even after a few hours it didn't re-read
/etc/resolv
