• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Resolved Newrelic PHP-Agent not reporting data ( EOENT on /tmp/.newrelic.sock )

nilsringersma_nl

Basic Pleskian
Dear users,

After running into some problems with installing Newrelic on Pleks Onyx operating on CentOS7 we've ran into some problems. We solved the problems with this thread. I've decided to share them with you, maybe helping someone in the future.

Problem:
After installing the newrelic-daemon and the PHP agent ( for whatever version of PHP ), the data is not showing up in Newrelic. Also the php-agent.log show the error: "warning: daemon connect(fd=6 uds=/tmp/.newrelic.sock) returned -1 errno=ENOENT".

Solution:
The error message ENOENT indicates the agent or its worker daemon are being denied entry to /tmp/.newrelic.sock. This file is a Unix Domain Socket, which the agent and daemon use to communicate by default. This error is often related to permissions and security issues.

The error message ECONNREFUSED indicates that the agent cannot detect its worker daemon. This might be because the daemon is not running, or because the agent and daemon are communicating in different ways, or because the daemon does not have permission to edit the current UDS at /tmp/.newrelic.sock.

Resolution
To resolve both of these issues, you can perform the following.

Delete the current file at /tmp/.newrelic.sock.
If it exists, delete the file at /etc/newrelic/newrelic.cfg or simply rename it, for example as newrelic.cfg.bak.
Change the communication method of the agent and daemon by setting the below in the newrelic.ini file:
newrelic.daemon.port= "@newrelic-daemon"
Kill the agent and daemon by running this command: killall newrelic-daemon
Restart the web server to redeploy the agent, which will restart/respawn the daemon.
 
Back
Top