graphite-dev team mailing list archive

[chrismd <question89138@xxxxxxxxxxxxxxxxxxxxx>]

Question #89138 on Graphite changed:
https://answers.launchpad.net/graphite/+question/89138

    Status: Open => Answered

chrismd proposed the following answer:
Cool thanks for the details. Here's one quick fix for the generated
apache config (I just fixed this bug in trunk a moment ago). Change the
"SetEnv DJANGO_SETTINGS_MODULE web.settings" to "SetEnv
DJANGO_SETTINGS_MODULE graphite.settings".

The other problem, failing to import carbon.conf is strange... from that
same directory can you run python and type "import carbon; print
carbon.__file__" and post the output? Maybe do an ls in the directory of
the file it outputs as well.

That *should* be all you need to get apache working but people often run
into permissions issues too. The whole $GRAPHITE_ROOT/storage/ directory
should be owned by the user apache runs as (chown -R). The development
server (run-graphite-deve-server.py) is very convenient in avoiding the
hassles with apache but it is also very slow and will not scale well.

Carbon-relay is basically a software load-balancer that directs metrics
to one or more carbon-cache's based on a the $GRAPHITE_ROOT/conf/relay-
rules.conf file. You only need it if you want a cluster of graphite
servers. One caveat to using it is that you must change the ports used
by either carbon-relay or carbon-cache as defined in
$GRAPHITE/conf/carbon.conf because they will both try to listen on 2003
by default since that is the standard port clients use to send data to
graphite.

I hope that helps.

-Chris

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.