Not Showing Up in New Relic

[ghost]

I am not getting any errors, and I have ran the script with a 'set -x', to watch as it runs. Appears normal, anything special I need to do to ensure it is working? The CURL even completes without error.

[zyclonite]

did you configure licensekey, host and name?

[ghost]

Yes I did. Triple checked
On Aug 30, 2014 2:29 AM, "Lukas Prettenthaler" notifications@github.com
wrote:

did you configure licensekey, host and name?

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[zyclonite]

it should show up in your newrelic console under the menu section "OpenWrt"

what version/built of openwrt are you using?

[ghost]

Agreed, this is was I am expecting, but not what I am getting...

Here is the version:

---

| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || _|| _|
|_____|| |___||||____||**| |**|
|| W I R E L E S S F R E E D O M

---

BARRIER BREAKER (r38031)

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Mon, Sep 1, 2014 at 3:09 AM, Lukas Prettenthaler <
notifications@github.com> wrote:

it should show up in your newrelic console under the menu section "OpenWrt"
[image: screen shot 2014-09-01 at 10 06 37]
https://cloud.githubusercontent.com/assets/674137/4105705/2aa4e9d0-31af-11e4-8fab-bfa7bbf8a306.png

what version/built of openwrt are you using?

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[ghost]

If you contact me directly I will send you the copy of my 'set -x' with
license in it; I just dont want that key publicly posted.

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Tue, Sep 2, 2014 at 10:22 AM, Matthew Curry matt@mattcurry.com wrote:

Agreed, this is was I am expecting, but not what I am getting...

Here is the version:

---

| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || _|| _|
|_____|| |___||||____||**| |**|
|| W I R E L E S S F R E E D O M

---

BARRIER BREAKER (r38031)

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Mon, Sep 1, 2014 at 3:09 AM, Lukas Prettenthaler <
notifications@github.com> wrote:

it should show up in your newrelic console under the menu section
"OpenWrt"
[image: screen shot 2014-09-01 at 10 06 37]
https://cloud.githubusercontent.com/assets/674137/4105705/2aa4e9d0-31af-11e4-8fab-bfa7bbf8a306.png

what version/built of openwrt are you using?

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[ghost]

any ideas? Firewall rules or anything?

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Tue, Sep 2, 2014 at 10:24 AM, Matthew Curry matt@mattcurry.com wrote:

If you contact me directly I will send you the copy of my 'set -x' with
license in it; I just dont want that key publicly posted.

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Tue, Sep 2, 2014 at 10:22 AM, Matthew Curry matt@mattcurry.com wrote:

Agreed, this is was I am expecting, but not what I am getting...

Here is the version:

---

| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || _|| _|
|_____|| |___||||____||**| |**|
|| W I R E L E S S F R E E D O M

---

BARRIER BREAKER (r38031)

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Mon, Sep 1, 2014 at 3:09 AM, Lukas Prettenthaler <
notifications@github.com> wrote:

it should show up in your newrelic console under the menu section
"OpenWrt"
[image: screen shot 2014-09-01 at 10 06 37]
https://cloud.githubusercontent.com/assets/674137/4105705/2aa4e9d0-31af-11e4-8fab-bfa7bbf8a306.png

what version/built of openwrt are you using?

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[zyclonite]

the script does not do any magic...

can you telnet to platform-api.newrelic.com port 443 on your device?
i have it running with AA as well as BB and bleeding edge releases of openwrt

[ghost]

root@Gaki:~# telnet platform-api.newrelic.com 443
Connection closed by foreign host

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Wed, Sep 3, 2014 at 6:59 AM, Lukas Prettenthaler <
notifications@github.com> wrote:

the script does not do any magic...

can you telnet to platform-api.newrelic.com port 443 on your device?
i have it running with AA as well as BB and bleeding edge releases of
openwrt

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[ghost]

which is odd, my other devices can get to it just fine; and the firewall is
off on that machine. It is saying that the remote server refused its
connection.... Any thoughts on why it would do that?

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Wed, Sep 3, 2014 at 6:59 AM, Lukas Prettenthaler <
notifications@github.com> wrote:

the script does not do any magic...

can you telnet to platform-api.newrelic.com port 443 on your device?
i have it running with AA as well as BB and bleeding edge releases of
openwrt

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[ghost]

sorry not trying to be a bother; I am a Linux Engineer; and I was suprised
when this didn't work. I appreciate the help, I am just new to New Relic,
and I have 4 of these devices to monitor; and I was hoping to tie it in to
an already established account. This would help me immensely if I could
get it going. Does it work on DD Wrt as well?

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Wed, Sep 3, 2014 at 10:07 AM, Matthew Curry matt@mattcurry.com wrote:

root@Gaki:~# telnet platform-api.newrelic.com 443
Connection closed by foreign host

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Wed, Sep 3, 2014 at 6:59 AM, Lukas Prettenthaler <
notifications@github.com> wrote:

the script does not do any magic...

can you telnet to platform-api.newrelic.com port 443 on your device?
i have it running with AA as well as BB and bleeding edge releases of
openwrt

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[zyclonite]

The only other thing i could think of is a routing problem on that specific device...

I don't know dd-wrt but if it is based on busybox too, there is a great chance that it will work. I run it on a synology diskstation...

[ghost]

well it pings just fine, and its getting "Refused", so it appears to be
getting to the target...I will see if I can run a traceroute...

Matthew Curry
MattCurry.com
BitMessage ID: BM-NBJCYLB8jQ2XBUMxrvrkTQ9MQoZ3JVrw

On Wed, Sep 3, 2014 at 2:21 PM, Lukas Prettenthaler <
notifications@github.com> wrote:

The only other thing i could think of is a routing problem on that
specific device...

I don't know dd-wrt but if it is based on busybox too, there is a great
chance that it will work. I run it on a synology diskstation...

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[zyclonite]

any update or did you give up?