Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to create standalone carbon relay #199

Closed
sonnysideup opened this issue Oct 22, 2014 · 5 comments
Closed

Unable to create standalone carbon relay #199

sonnysideup opened this issue Oct 22, 2014 · 5 comments

Comments

@sonnysideup
Copy link
Contributor

carbon-relay.py fails to execute after using the following recipe/LWRP:

include_recipe "graphite::carbon"

graphite_carbon_relay "i_stand_alone" do
  config(...) # them details
end

and here's the exception that is thrown:

image

I checked the system and confirmed that pip never installed "whisper" on the system.

The graphite_carbon_cache LWRP installs "whisper" using a backend attribute whereas graphite_carbon_relay is lacking this sub-operation.

I can understand the reasoning behind forgoing a backend install (i.e. whisper ) when creating a relay, but the fact remains that the carbon-relay daemon will not launch without it.

@sonnysideup
Copy link
Contributor Author

I just noticed that the same condition exists when using the graphite::web recipe. Does it really make sense to force users to invoke the graphite_storage LWRP in order to use any facet of this library?

@joelgriffiths
Copy link

Sorry if it's a dumb question, but what is the workaround for this?

@sonnysideup
Copy link
Contributor Author

Just make sure you invoke the storage LWRP when you're creating a standalone relay.

graphite_storage 'default'

@damacus
Copy link
Member

damacus commented Apr 27, 2017

Closing this issue down as it looks like it's solved.

Thanks all!

@damacus damacus closed this as completed Apr 27, 2017
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants