Changes to the
newrelic.ini file are not taking effect immediately.
Restart your web server (Apache, Nginx, PHP-FPM, etc.) after you make any changes to your INI settings.
When your web server (Apache, Nginx, PHP-FPM, etc.) first starts up and initializes PHP, it reads all of the INI settings. It also sets the global defaults for any missing settings.
Apache then creates a pool of "worker" processes to deal with requests. These worker processes inherit the settings set during initialization. You have no way of knowing exactly which worker process will deal with a given request. When you make INI file changes, there may still be hundreds of worker processes left with the old settings, and the main Apache process itself (which will periodically kill existing and spawn new worker processes) also has the original INI settings.
Until you restart your Apache server, most changes to your INI files will go unnoticed. The only exception is if you use PHP's "per-directory" setting mechanism using
.htaccess files. Such settings are rare.
If you need more help, check out these support and learning resources:
- Suggest a change and learn how to contribute to our PHP agent open source repository.
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.