newrelic-daemon does not take new key once setup

Open
#58 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale

Research direction

Start with the New Relic configuration steps in the linked EasyEngine handbook page and inspect how the newrelic daemon container loads its key during startup. Reproduce the account switch, then review /var/log/newrelic/newrelic-daemon.log after restarting the container. Done means the site is registered with the second account rather than remaining in the first.

Written by the indexing model from the issue text.

Description

Steps to reproduce:

  1. Create 2 newrelic account.
  2. Configure newrelic with first account as shown in https://easyengine.io/handbook/configure-new-relic-in-ee4
  3. Wait for newrelic to show data
  4. Now change the key to that of 2nd account.
  5. Disable and enable site and reload(or stop, kill and start) newrelic daemon container.

Expected output:
The site is registered in 2nd account.

Actual output:
The site is registered in 1st account and does not get re-registered in 2nd account.

I additionally verified it by tailing /var/log/newrelic/newrelic-daemon.log in newrelic daemon while it was starting up in step 5.

Dominant language
PHP
Stars
3
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EasyEngine/service-command

All issues in EasyEngine/service-command

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.