no graphs in graphite

Asked by cnsmith

For some reason graphs are not populating in graphite. Neither the graphite directory nor the user graphs in the tree have graphs.
I installed graphite and am able to view the webapp. I have carbon running and I believe the example-load script can connect to it and send the data. The logs I've viewed seem fine, no errors. Im guessing im not viewing the correct logs?

What I have noticed is Whisper has no data in /usr/local/graphite/storage/whisper/
But, it does have data in: /opt/my_graphite_branch/graphite-0.9.4/storage/whisper ]$ ls
carbon system

/opt/my_graphite_branch/graphite-0.9.4/storage/whisper/system ]$ ls
loadavg_15min.wsp loadavg_1min.wsp loadavg_5min.wsp

apache 30713 0.0 0.1 9764 2920 ? S 00:12 0:04 python ./carbon-agent.py -u apache
apache 30714 0.0 0.2 10736 4824 ? S 00:12 0:00 python ./carbon-cache.py 6 9

Am I running the example script correctly? And is my schema setup properly?
Schema:
 /usr/local/graphite/storage ]$ cat servers.fourmoons.cpu
[server_load]
priority = 100
pattern = ^servers\.
retentions = 60:43200,900:350400

example script crontab:
* * * * * ~/scripts/example_client.py 2> /dev/null

/usr/local/graphite/storage/log ]$ cat info.log
Wed Feb 11 09:44:20 2009 :: path= pattern=*
Wed Feb 11 09:59:34 2009 :: path= pattern=*

P.S. I did read the other posts for graphs not showing up in the tree and the solution didnt seem to work for me.

MORE LOGS

 /opt/my_graphite_branch/graphite-0.9.4/carbon/log ]$ cat agent.log
Tue Feb 10 22:43:43 2009: carbon-agent started (pid=30358)
Tue Feb 10 22:43:43 2009: created cache pipe, fds=['6', '7']
Tue Feb 10 22:43:43 2009: created persister pipe, fds=['8', '9']
Tue Feb 10 22:43:43 2009: carbon-cache started with pid 30359
Tue Feb 10 22:43:43 2009: carbon-persister started with pid 30360
Tue Feb 10 22:43:43 2009: listener socket ready
Tue Feb 10 23:18:00 2009: accepted connection from ('127.0.0.1', 42648)
Tue Feb 10 23:20:21 2009: lost connection from ('127.0.0.1', 42648)
Tue Feb 10 23:21:28 2009: accepted connection from ('127.0.0.1', 41893)
Tue Feb 10 23:48:37 2009: lost connection from ('127.0.0.1', 41893)
Wed Feb 11 00:01:43 2009: accepted connection from ('127.0.0.1', 44663)
Wed Feb 11 00:06:01 2009: lost connection from ('127.0.0.1', 44663)
Wed Feb 11 00:09:02 2009: accepted connection from ('127.0.0.1', 36345)

cache log

Wed Feb 11 00:11:02 2009: Sorted 3 cache queues in 0.000 seconds
Wed Feb 11 00:12:00 2009: doCheckpoint() now=1234332660 stats={'cacheQueries': 0}
Wed Feb 11 00:12:00 2009: Resorting 3 cache queues by size...
Wed Feb 11 00:12:00 2009: Sorted 3 cache queues in 0.000 seconds

persister.log

took 0.000263 seconds
Wed Feb 11 00:11:01 2009: update_many: ../storage/whisper/carbon/agents/fourmoons/committedPoints.wsp 1 data points took 0.000267 seconds
Wed Feb 11 00:11:02 2009: update_many: ../storage/whisper/system/loadavg_5min.wsp 1 data points took 0.000439 seconds
Wed Feb 11 00:11:02 2009: update_many: ../storage/whisper/system/loadavg_1min.wsp 1 data points took 0.000303 seconds
Wed Feb 11 00:11:02 2009: update_many: ../storage/whisper/system/loadavg_15min.wsp 1 data points took 0.000276 seconds

Question information

Language:
English Edit question
Status:
Solved
For:
Graphite Edit question
Assignee:
No assignee Edit question
Solved by:
cnsmith
Solved:
Last query:
Last reply:
Revision history for this message
cnsmith (cnsmith21) said :
#1

Also, where can I get PypeD?

Revision history for this message
chrismd (chrismd) said :
#2

It looks like you are running carbon out of your bzr checkout rather than out of the /usr/local/graphite/ installation. You should stop the running carbon daemons and do this:

cd /usr/local/graphite/carbon/
./carbon-agent.py

That will start the right carbon daemon. Also the example-client.py script keeps running until you kill it so you should not put it in a cron (unless you modified it and took out the while loop). Everything else you said looks fine. As for pyped it is unfortunately still not ready for an open source release, it is something I need to spend some more time on.

Revision history for this message
cnsmith (cnsmith21) said :
#3

Does carbon-agent.py need to be started as sudo? It wont start for me unless I do sudo ./carbon-agent.py start

/usr/local/graphite/carbon ]$ ls -l
total 60
-rwxr-xr-x 1 apache apache 5703 Feb 10 17:07 carbon-agent.py
-rwxr-xr-x 1 apache apache 7141 Feb 10 17:07 carbon-cache.py
-rwxr-xr-x 1 apache apache 4386 Feb 10 17:07 carbon-persister.py
-rwxr-xr-x 1 apache apache 924 Feb 10 17:07 init-script.sh

/usr/local/graphite/carbon ]$ ps aux | grep py
apache 7028 0.0 0.1 9748 2648 ? S 18:33 0:00 python ./carbon-agent.py
apache 7029 0.0 0.1 9560 3572 ? S 18:33 0:00 python ./carbon-cache.py 6 9
apache 7030 0.0 0.0 0 0 ? Z 18:33 0:00 [python] <defunct>
500 7033 0.0 0.1 9064 3264 pts/2 S+ 18:34 0:00 /usr/bin/python ./getcpu.py

getcpy.py is the example.py script (not modified)

Revision history for this message
chrismd (chrismd) said :
#4

You should run carbon as the user that owns the storage directory (if you run it as root it drops privileges to apache or a user specified by the -u option). I see in your ps output that it looks like the carbon-persister process died. Look at $GRAPHITE_ROOT/carbon/log/persister.log to see why, there should be some error message.

Revision history for this message
cnsmith (cnsmith21) said :
#5

That worked. Thanks.