Re: [collectd] How often does Collectd read resolv.conf?

2015-06-05 Thread Markus Shorty Uckelmann

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 possibilities, for
example.

If /etc/resolv.conf is read, if it is re-read when modified and so on is
out of our control, unfortunately.


Would be systemd-resolved of any help here? I haven't looked into it. 
Just a guess.


Cheers, Shorty

___
collectd mailing list
collectd@verplant.org
http://mailman.verplant.org/listinfo/collectd


Re: [collectd] How often does Collectd read resolv.conf?

2015-06-05 Thread Dan Fandrich
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 resolution is done depends on the C library – on
 many GNU/Linux systems DNS is one of multiple possibilities, for
 example.
 
 If /etc/resolv.conf is read, if it is re-read when modified and so on is
 out of our control, unfortunately.
 
 Would be systemd-resolved of any help here? I haven't looked into it. Just a
 guess.

Note that IIRC glibc (and probably other resolver libraries) will reread
/etc/resolv.conf when res_init() is called, so it's possible for the
application to have some say in when it's reread.

 Dan

___
collectd mailing list
collectd@verplant.org
http://mailman.verplant.org/listinfo/collectd


Re: [collectd] How often does Collectd read resolv.conf?

2015-05-30 Thread Florian Forster
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
attempt. How the name resolution is done depends on the C library – on
many GNU/Linux systems DNS is one of multiple possibilities, for
example.

If /etc/resolv.conf is read, if it is re-read when modified and so on is
out of our control, unfortunately.

HTH, best regards,
—octo
-- 
collectd – The system statistics collection daemon
Website: http://collectd.org
Google+: http://collectd.org/+
GitHub:  https://github.com/collectd
Twitter: http://twitter.com/collectd


signature.asc
Description: Digital signature
___
collectd mailing list
collectd@verplant.org
http://mailman.verplant.org/listinfo/collectd


[collectd] How often does Collectd read resolv.conf?

2015-05-29 Thread Markus Shorty Uckelmann
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.conf. Is this a desired behaviour?
I think Collectd should once in a while re-read /etc/resolv.conf

Cheers, Shorty



signature.asc
Description: OpenPGP digital signature
___
collectd mailing list
collectd@verplant.org
http://mailman.verplant.org/listinfo/collectd


Re: [collectd] How often does Collectd read resolv.conf?

2015-05-29 Thread Kevin Burton
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 12:05 PM, Markus Shorty Uckelmann sho...@koeln.de
 wrote:

 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.conf. Is this a desired behaviour?
 I think Collectd should once in a while re-read /etc/resolv.conf

 Cheers, Shorty


 ___
 collectd mailing list
 collectd@verplant.org
 http://mailman.verplant.org/listinfo/collectd




-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
https://plus.google.com/102718274791889610666/posts
___
collectd mailing list
collectd@verplant.org
http://mailman.verplant.org/listinfo/collectd