Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

The newrelic-sysmond is not sending data


#1

Hello
I am running Debian and have had this running on several other servers running the same OS without any problems.

Any help with this matter would be greatly appreciated.

/var/log/newrelic/nrsysmond.log

New Relic 2.3.0 (build 132 - “cloudy” - “8cff29599e1e9619b31da739b2ac86c7213f6b71”) [workers=1 pid=30976 ppid=30974 uid=999 euid=999 gid=999 egid=999 backtrace=yes startup=init os=‘Linux’ rel=‘3.14.79-cerberhost-0.11.0deb7+nbs20161028-grsec’ mach=‘x86_64’ ver=’#1 SMP Fri Oct 28 10’ node=‘eqx11145’]
2018-04-19 21:15:25.892 (30974) info: watcher received signal 15 - killing worker workerpid 30976
2018-04-19 21:16:03.901 (1419) info: Docker: using connection url=‘http://localhost
2018-04-19 21:16:03.901 (1419) info: Docker: connecting over socket=’/var/run/docker.sock’
2018-04-19 21:16:03.901 (1419) info: New Relic 2.3.0 (build 132 - “cloudy” - “8cff29599e1e9619b31da739b2ac86c7213f6b71”) [workers=1 pid=1419 ppid=1418 uid=999 euid=999 gid=999 egid=999 backtrace=yes startup=init os=‘Linux’ rel=‘3.14.79-cerberhost-0.11.0deb7+nbs20161028-grsec’ mach=‘x86_64’ ver=’#1 SMP Fri Oct 28 10’ node=‘eqx11145’]
2018-04-19 21:16:56.176 (1418) info: watcher received signal 15 - killing worker workerpid 1419
2018-04-19 21:16:57.278 (1497) info: Docker: using connection url=‘http://localhost
2018-04-19 21:16:57.278 (1497) info: Docker: connecting over socket=’/var/run/docker.sock’
2018-04-19 21:16:57.279 (1497) info: New Relic 2.3.0 (build 132 - “cloudy” - “8cff29599e1e9619b31da739b2ac86c7213f6b71”) [workers=1 pid=1497 ppid=1495 uid=999 euid=999 gid=999 egid=999 backtrace=yes startup=init os=‘Linux’ rel=‘3.14.79-cerberhost-0.11.0deb7+nbs20161028-grsec’ mach=‘x86_64’ ver=’#1 SMP Fri Oct 28 10’ node=‘eqx11145’]


  • About to connect() to collector.newrelic.com port 443 (#0)
  • Trying 50.31.164.146…
  • connected
  • Connected to collector.newrelic.com (50.31.164.146) 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 change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSL connection using RC4-SHA
  • Server certificate:
  • subject: C=US; ST=California; L=San Francisco; O=New Relic, Inc.; CN=*.newrelic.com
  • start date: 2018-01-19 00:00:00 GMT
  • expire date: 2021-04-16 12:00:00 GMT
  • subjectAltName: collector.newrelic.com matched
  • issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=GeoTrust RSA CA 2018
  • SSL certificate verify ok.

GET /status/mongrel HTTP/1.1
User-Agent: curl/7.26.0
Host: collector.newrelic.com
Accept: /

  • additional stuff not fine transfer.c:1037: 0 0
  • HTTP 1.1 or later with persistent connection, pipelining supported
    < HTTP/1.1 200 OK
    < Content-Type: text/plain
    < Content-Length: 22
    <
    mongrel ==> up (true)
  • Connection #0 to host collector.newrelic.com left intact
  • Closing connection #0
  • SSLv3, TLS alert, Client hello (1):

Best Regards


#2

Hi @newrelic22 -

Sorry it has taken us so long to get back to you. I wanted to make sure you are aware that our Serves product will reach End of Life on May 15:

Because of that, we are not able to offer support at this time for this product. But please let me know ifI misunderstood and you are not inquiring about our Servers product.


#3