Skip to content
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.

sim2h_server newrelic error #2118

Open
Connoropolous opened this issue Feb 17, 2020 · 4 comments
Open

sim2h_server newrelic error #2118

Connoropolous opened this issue Feb 17, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@Connoropolous
Copy link
Collaborator

Connoropolous commented Feb 17, 2020

Running sim2h_server where the version is v0.0.43-alpha3 results in an error:

$ sim2h_server -V
2020-02-17 17:07:44.425 -0500 (18408 4743669) error: failed to connect to the daemon using a timeout of 0 ms at the path /tmp/.newrelic.sock
sim2h_server 0.0.43-alpha3

Is there some kind of configuration that we need to know about to magically make this work?

@Connoropolous Connoropolous added the bug Something isn't working label Feb 17, 2020
@Connoropolous Connoropolous linked a pull request Mar 8, 2020 that will close this issue
2 tasks
@freesig
Copy link
Contributor

freesig commented Mar 9, 2020

This isn't so much a bug as just a report that it hasn't connected to the newrelic server. But I don't think it should emit this error unless the env var is set and then it can't connect.

@freesig
Copy link
Contributor

freesig commented Mar 9, 2020

Also it should probably be a warn not an error

@Connoropolous
Copy link
Collaborator Author

True... it's just strange that the default logging has this line show up when you run sim2h_server and nothing else...

2020-02-17 17:07:44.425 -0500 (18408 4743669) error: failed to connect to the daemon using a timeout of 0 ms at the path /tmp/.newrelic.sock

That's the whole log unless you change the logging level

@freesig
Copy link
Contributor

freesig commented Mar 10, 2020

Yeh it happens before logging is enabled

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants