Dns Error Caching Ip Address No Address For Collector.newrelic.com
Reporting. After looking at the newrelic-daemon logs I can see there is a connectivity problem. One of the errors is: 2014-09-09 15:25:51.049 (671) warning: RPM call='metric_data' for app='xxx' failed 2014-09-09 15:29:51.312 (671) error: RPM cmd='metric_data' for 'xxx' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com' This is probably an issue on my end, but I decided to post it here in case anyone else has seen this problem and knows how to fix it. The errors occurs for several minutes and then stop for a couple of hours. I included a more complete log below: 014-09-09 14:08:51.521 (671) error: RPM cmd='metric_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:08:51.521 (671) warning: RPM call='metric_data' for app='wvega.com' failed 2014-09-09 14:09:11.599 (671) error: RPM cmd='analytic_event_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:09:11.599 (671) warning: RPM call='analytic_event_data' for app='wvega.com' failed 2014-09-09 14:11:50.712 (671) error: RPM cmd='metric_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:11:50.712 (671) warning: RPM call='metric_data' for app='wvega.com' failed 2014-09-09 14:17:51.079 (671) error: RPM cmd='metric_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:17:51.079 (671) warning: RPM call='metric_data' for app='wvega.com' failed 2014-09-09 14:20:50.767 (671) error: RPM cmd='metric_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:20:50.767 (671) warning: RPM call='metric_data' for app='wvega.com' failed 2014-09-09 14:21:10.845 (671) error: RPM cmd='analytic_event_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:21:10.845 (671) warning: RPM call='analytic_event_data' for app='wvega.com' failed 2014-09-09 14:22:51.166 (671) error: RPM cmd='metric_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:22:51.166 (671) warning: RPM call='metric_data' for app='wvega.com' failed 2014-09-09 14:24:50.837 (671) error: RPM cmd='metric_data' for 'wvega.com' failed: (6): 'Couldn't resolve host 'collector-108.newrelic.com'' 2014-09-09 14:24:50.837 (671) warning: RPM call='metric_data' for app='wvega.com' failed 2014-09-09 14:25:51.080 (671) error: RPM cmd='metric_data' for 'wvega.com' failed: (6
From the log (nrsysmond.log): [1977/timer] error: RPM command 'metric_data' failed(6): Couldn't resolve host 'collector-135.newrelic.com' But when I try to ping this host from the VPS, it works. Restart didn't help. Turning off SSL in the config file didn't help, too. Any idea? chrisw 2014-09-10 10:33:53 UTC #2 Hi @jkostolansky, Looks like your VPS had some connectivity issues with our network.We didn't have any issues with the collectors recently that could account for this outage.You can check it out https://discuss.newrelic.com/t/server-not-reporting-couldnt-resolve-host-collector-108-newrelic-com/5118 here: https://status.newrelic.com/ I am afraid if everything is currently working there isn't much we can do to troubleshoot.Here are some commands that can be useful to run during a period of connectivity outage. [non-SSL] curl -v http://collector.newrelic.com/status/mongrel [SSL] curl -v https://collector.newrelic.com/status/mongrel Can you also test your route to the collector with: traceroute collector.newrelic.com If the agent is https://discuss.newrelic.com/t/difficulties-with-sending-data/5134 unable to connect to us, the traceroute will be useful. Hopefully it can give an idea of where the network path is failing. I know these routes change, so it isn't going to really guarantee anything. I hope this answer was helpful to you, if you have any questions, don't hesitate to ask! jkostolansky 2014-09-10 19:40:23 UTC #3 Hi @chrisw, thank you for the response. Here are outputs from your suggestions during a period of connectivity outage: CURL $ curl -v https://collector.newrelic.com/status/mongrel * About to connect() to collector.newrelic.com port 443 (#0) * Trying 50.31.164.140... * connected * Connected to collector.newrelic.com (50.31.164.140) port 443 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS
Contains methods that deal with connecting to the server Instance Method Summary collapse #api_server ⇒ Object the server we should contact for api requests, like uploading deployments and the like. #cert_file_path ⇒ Object The path to the certificate file used to verify the SSL connection http://www.rubydoc.info/gems/newrelic_rpm/3.3.1/NewRelic/Control/ServerMethods if verify_peer is enabled. #convert_to_ip_address(host) ⇒ Object Check to see if we need to look up the IP address If it's an IP address already, we pass it through. #http_connection(host = nil) ⇒ Object http://kx.cloudingenium.com/page/16/ Return the Net::HTTP with proxy configuration given the NewRelic::Control::Server object. #proxy_server ⇒ Object a new instances of the proxy server - this passes through if there is no proxy, otherwise it has proxy dns error configuration information pulled from the config file. #resolve_ip_address(host) ⇒ Object Look up the ip address of the host using the pure ruby lookup to prevent blocking. #server ⇒ Object #server_from_host(hostname = nil) ⇒ Object turns a hostname into an ip address and returns a NewRelic::Control::Server that contains the configuration info. Instance Method Details #api_server ⇒ Object the server we should contact for api requests, like uploading dns error caching deployments and the like 20 21 22 23 24 25 26 27 # File 'lib/new_relic/control/server_methods.rb', line 20 def api_server api_host = self['api_host'] || 'rpm.newrelic.com' @api_server ||= NewRelic::Control::Server.new \ api_host, (self['api_port'] || self['port'] || (use_ssl? ? 443 : 80)).to_i, nil end #cert_file_path ⇒ Object The path to the certificate file used to verify the SSL connection if verify_peer is enabled 80 81 82 # File 'lib/new_relic/control/server_methods.rb', line 80 def cert_file_path File.expand_path(File.join(newrelic_root, 'cert', 'cacert.pem')) end #convert_to_ip_address(host) ⇒ Object Check to see if we need to look up the IP address If it's an IP address already, we pass it through. If it's nil, or localhost, we don't bother. Otherwise, use `resolve_ip_address` to find one 50 51 52 53 54 55 56 57 58 # File 'lib/new_relic/control/server_methods.rb', line 50 def convert_to_ip_address(host) # here we leave it as a host name since the cert verification # needs it in host form return host if verify_certificate? return nil if host.nil? || host.downcase == "localhost" ip = resolve_ip_address(host) log.info "Resolved #{host} to #{ip}" ip end #http_connection(host = nil) ⇒ Object Return the Net::HTTP with proxy configuration given the NewRelic::Control::Server object. Default is the collector but for api calls you need to pass api_server Exper
Many complaints have surface around the performance of php 5.x and even hhvm came out as a result of that. We had a lot of interest in hhvm, but we never got it … View full post How to: Cache static HTML with CloudFlare? How to: Cache static HTML with CloudFlare? So… I have been working with CloudFlare for quite sometime but every now and then when my web server goes down CloudFlare seems to be unable to serve my pages while it comes back. I had to create my own cache server for it but it involved another … View full post How to: Configure Dynamic DNS Service on the Unifi Security Gateway via config.gateway.json How to: Configure Dynamic DNS Service on the Unifi Security Gateway via config.gateway.json Thankfully the latest versions of Ubiquiti's Unifi Controller allow the user to configure dynamic DNS services via the Web UI. However, there are cases when you rather keep the configuration on the config.gateway.json file. In my case the main motivation to use … View full post How to: Install a .deb file via the Command line? Packages are manually installed via the dpkg command (Debian Package Management System). dpkg is the backend to commands like apt-get and aptitude, which in turn are the backend for GUI install apps like the Software Center and Synaptic. Something along the lines of: dpkg -> apt-get, aptitude -> Synaptic, Software Center But of course the … View full post Google IP address ranges Google IP address ranges Recently I decided to try the Google Compute Engine Cloud, and one of the things I liked right from the beginning was the ability to connect via SSH to your Ubuntu box. I am going to have to read a bit more about it but basically it seems like it generates … View full post Pro Tip: Upgrade to PHP7How to: Cache static HTML with CloudFlare?How to: Configure Dynamic DNS Service on the Unifi Security Gateway via config.gateway.jsonHow to: Install a .deb file via the Command line?Google IP address ranges Dec 14 How to: Resolve slow Logging in issues and Sudo rights use when using your own DNS in Windows Azure Categories: Windows Azure *Cloud* by Juan Carlos How to: Resolve slow Logging in issues and Sudo rights use when using your own DN