Opened 16 months ago
Last modified 16 months ago
#117 new defect
Install Newrelic on Crin2
| Reported by: | chris | Owned by: | chris |
|---|---|---|---|
| Priority: | major | Milestone: | Maintenance |
| Component: | crin2 | Version: | |
| Keywords: | Cc: | peter | |
| Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
| Billable?: | yes | Total Hours: | 0.5 |
Description
Peter has requested that Newrelic be installed on Crin2.
Note that last time it was installed we had to remove it due to the resources it was using, see this thread ticket:73#comment:24, so I'd advise against leaving it on the server all the time.
Change History (9)
comment:1 Changed 16 months ago by chris
- Add Hours to Ticket changed from 0 to 0.25
- Total Hours set to 0.25
comment:2 Changed 16 months ago by chris
The firewall needs updating on Crin1 to allow incoming connections from New Relic:
comment:3 Changed 16 months ago by chris
- Add Hours to Ticket changed from 0 to 0.25
- Total Hours changed from 0.25 to 0.5
Looking at the networks page, it is mostly about outging traffic and none is blocked, there is also:
If you want to configure your firewall to allow New Relic to access your monitoring URL
I assume that "monitoring URL" is going to use HTTP or HTTPS? In which case that isn't an issue either as we allow port 80 and 443 traffic to the server, it is a web server after all...
So I can't see that we need to do anything?
Peter -- have I missed something here?
comment:4 Changed 16 months ago by peter
Hi Chris. Have we restarted php-fpm? On Tue, 23 May 2017 at 13:24 CRIN Trac <trac@trac.crin.org> wrote: > #117: Install Newrelic on Crin2 > ------------------------------------+----------------------------------- > Reporter: chris | Owner: chris > Type: defect | Status: new > Priority: major | Milestone: Maintenance > Component: crin2 | Version: > Resolution: | Keywords: > Estimated Number of Hours: 0 | Add Hours to Ticket: 0.25 > Billable?: 1 | Total Hours: 0.25 > ------------------------------------+----------------------------------- > Changes (by chris): > > * hours: 0 => 0.25 > * totalhours: 0.25 => 0.5 > > > Comment: > > Looking at the [https://docs.newrelic.com/docs/apm/new-relic-apm/getting- > started/networks networks page], it is mostly about outging traffic and > none is blocked, there is also: > > > If you want to configure your firewall to allow New Relic to access your > monitoring URL > > I assume that "monitoring URL" is going to use HTTP or HTTPS? In which > case that isn't an issue either as we allow port 80 and 443 traffic to the > server, it is a web server after all... > > So I can't see that we need to do anything? > > Peter -- have I missed something here? > > -- > Ticket URL: <https://trac.crin.org.archived.website/trac/ticket/117#comment:3> > CRIN Trac <https://trac.crin.org.archived.website/trac> > Trac project for CRIN website and servers. >
comment:5 Changed 16 months ago by peter
We are missing the newrelic.ini file.
The mods-available is pointing to a file that does not exist.
I'll see what we need to put in it.
lrwxrwxrwx 1 root root 33 May 14 2016 20-newrelic.ini ->
../../mods-available/newrelic.ini
On Tue, 23 May 2017 at 14:20 CRIN Trac <trac@trac.crin.org> wrote:
> #117: Install Newrelic on Crin2
> ------------------------------------+-----------------------------------
> Reporter: chris | Owner: chris
> Type: defect | Status: new
> Priority: major | Milestone: Maintenance
> Component: crin2 | Version:
> Resolution: | Keywords:
> Estimated Number of Hours: 0 | Add Hours to Ticket: 0
> Billable?: 1 | Total Hours: 0.5
> ------------------------------------+-----------------------------------
>
> Comment (by peter):
>
> {{{
> Hi Chris. Have we restarted php-fpm?
>
> On Tue, 23 May 2017 at 13:24 CRIN Trac <trac@trac.crin.org> wrote:
>
> > #117: Install Newrelic on Crin2
> > ------------------------------------+-----------------------------------
> > Reporter: chris | Owner: chris
> > Type: defect | Status: new
> > Priority: major | Milestone: Maintenance
> > Component: crin2 | Version:
> > Resolution: | Keywords:
> > Estimated Number of Hours: 0 | Add Hours to Ticket: 0.25
> > Billable?: 1 | Total Hours: 0.25
> > ------------------------------------+-----------------------------------
> > Changes (by chris):
> >
> > * hours: 0 => 0.25
> > * totalhours: 0.25 => 0.5
> >
> >
> > Comment:
> >
> > Looking at the [https://docs.newrelic.com/docs/apm/new-relic-
> apm/getting-
> > started/networks networks page], it is mostly about outging traffic and
> > none is blocked, there is also:
> >
> > > If you want to configure your firewall to allow New Relic to access
> your
> > monitoring URL
> >
> > I assume that "monitoring URL" is going to use HTTP or HTTPS? In which
> > case that isn't an issue either as we allow port 80 and 443 traffic to
> the
> > server, it is a web server after all...
> >
> > So I can't see that we need to do anything?
> >
> > Peter -- have I missed something here?
> >
> > --
> > Ticket URL: <https://trac.crin.org.archived.website/trac/ticket/117#comment:3>
> > CRIN Trac <https://trac.crin.org.archived.website/trac>
> > Trac project for CRIN website and servers.
> >
> }}}
>
> --
> Ticket URL: <https://trac.crin.org.archived.website/trac/ticket/117#comment:4>
> CRIN Trac <https://trac.crin.org.archived.website/trac>
> Trac project for CRIN website and servers.
>
comment:6 Changed 16 months ago by peter
PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20131226/newrelic.so'
We are also missing the main object file for the php plugin.
On Tue, 23 May 2017 at 14:31 CRIN Trac <trac@trac.crin.org> wrote:
> #117: Install Newrelic on Crin2
> ------------------------------------+-----------------------------------
> Reporter: chris | Owner: chris
> Type: defect | Status: new
> Priority: major | Milestone: Maintenance
> Component: crin2 | Version:
> Resolution: | Keywords:
> Estimated Number of Hours: 0 | Add Hours to Ticket: 0
> Billable?: 1 | Total Hours: 0.5
> ------------------------------------+-----------------------------------
>
> Comment (by peter):
>
> {{{
> We are missing the newrelic.ini file.
> The mods-available is pointing to a file that does not exist.
> I'll see what we need to put in it.
>
>
> lrwxrwxrwx 1 root root 33 May 14 2016 20-newrelic.ini ->
> ../../mods-available/newrelic.ini
>
>
>
>
> On Tue, 23 May 2017 at 14:20 CRIN Trac <trac@trac.crin.org> wrote:
>
> > #117: Install Newrelic on Crin2
> > ------------------------------------+-----------------------------------
> > Reporter: chris | Owner: chris
> > Type: defect | Status: new
> > Priority: major | Milestone: Maintenance
> > Component: crin2 | Version:
> > Resolution: | Keywords:
> > Estimated Number of Hours: 0 | Add Hours to Ticket: 0
> > Billable?: 1 | Total Hours: 0.5
> > ------------------------------------+-----------------------------------
> >
> > Comment (by peter):
> >
> > {{{
> > Hi Chris. Have we restarted php-fpm?
> >
> > On Tue, 23 May 2017 at 13:24 CRIN Trac <trac@trac.crin.org> wrote:
> >
> > > #117: Install Newrelic on Crin2
> > >
> ------------------------------------+-----------------------------------
> > > Reporter: chris | Owner: chris
> > > Type: defect | Status: new
> > > Priority: major | Milestone:
> Maintenance
> > > Component: crin2 | Version:
> > > Resolution: | Keywords:
> > > Estimated Number of Hours: 0 | Add Hours to Ticket: 0.25
> > > Billable?: 1 | Total Hours: 0.25
> > >
> ------------------------------------+-----------------------------------
> > > Changes (by chris):
> > >
> > > * hours: 0 => 0.25
> > > * totalhours: 0.25 => 0.5
> > >
> > >
> > > Comment:
> > >
> > > Looking at the [https://docs.newrelic.com/docs/apm/new-relic-
> > apm/getting-
> > > started/networks networks page], it is mostly about outging traffic
> and
> > > none is blocked, there is also:
> > >
> > > > If you want to configure your firewall to allow New Relic to
> access
> > your
> > > monitoring URL
> > >
> > > I assume that "monitoring URL" is going to use HTTP or HTTPS? In
> which
> > > case that isn't an issue either as we allow port 80 and 443 traffic
> to
> > the
> > > server, it is a web server after all...
> > >
> > > So I can't see that we need to do anything?
> > >
> > > Peter -- have I missed something here?
> > >
> > > --
> > > Ticket URL: <https://trac.crin.org.archived.website/trac/ticket/117#comment:3>
> > > CRIN Trac <https://trac.crin.org.archived.website/trac>
> > > Trac project for CRIN website and servers.
> > >
> > }}}
> >
> > --
> > Ticket URL: <https://trac.crin.org.archived.website/trac/ticket/117#comment:4>
> > CRIN Trac <https://trac.crin.org.archived.website/trac>
> > Trac project for CRIN website and servers.
> >
> }}}
>
> --
> Ticket URL: <https://trac.crin.org.archived.website/trac/ticket/117#comment:5>
> CRIN Trac <https://trac.crin.org.archived.website/trac>
> Trac project for CRIN website and servers.
>
comment:7 Changed 16 months ago by peter
I have it working: Ran the agent install again. sudo apt-get install newrelic-php5
comment:8 Changed 16 months ago by chris
Thanks Peter, I hasn't installed the newrelic-php5 package, only the newrelic-sysmond package, see ticket:117#comment:1.
comment:9 Changed 16 months ago by chris
Hi Peter
Any interesting stats so far?
Would it also be worth installing on Crin1? Or is there enough data in /var/log/mysql/mysql-slow.log to work with already?
Note: See
TracTickets for help on using
tickets.
Following the instructions, we already had a /etc/apt/sources.list.d/newrelic.list file containing "deb http://apt.newrelic.com/debian/ newrelic non-free" so the gpg key will also be there so:
So there should soon be some stats...