graphite-dev team mailing list archive

[dggreenbaum <question264678@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Answered => Solved

dggreenbaum confirmed that the question is solved:
@brettswift thank you for the response. I don't think our problems are
related but I left you what advice I could.

I finally managed to fix this right before I went to bed. The problem
stemmed from a disagreement between carbon and graphite about where the
.wsp files should be located. Graphite was looking for them at
/opt/graphite/storage/whisper whereas carbon was putting them in
/var/lib/carbon/whisper.  Symlinking /var/lib/carbon/whisper to
/opt/graphite/storage/whisper solved the problem immediately.

The reason carbon was writing to the wrong place became obvious after
running  ps aux | grep carbon. The carbon-cache python process had been
provided with the non existent /etc/carbon/carbon.conf as configuration.
This is the result of migrating this machine from an unmanaged
graphite/whisper/carbon setup installed via yum to a puppet managed
setup installed via pip. When I uninstalled the old version of carbon I
never stopped the old process. Thus the new process could not start.
After killing the carbon process and restarting the carbon service .wsp
files were now being written to the correct place and I could delete the
symlink.

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