Graphite

Graphite frontend not displaying

Asked by pecastro

Hi all.

I did the Graphite installation and followed all the steps except having the sqlite module installed as I was planning on having the database on MySQL.
I've managed to build the database and perform the instalation and also add the Vhost config file to Apache.
I add some problems with the Memcached module, although being stated has optional I kept on having errors in the Apache log about not being able to connect/use the Memcahed library. After installing it those errors disappeared.

Now, after everything set and done, whenever I fire my browser to where the graphite app lives a only see two horizontal lines being drawn in the screen and these errors in the webapp-error.log

[Thu Jul 10 11:58:21 2008] [error] [client 10.209.41.166] client denied by server configuration: /usr/local/graphite/webapp/
[Thu Jul 10 11:58:21 2008] [error] [client 10.209.41.166] client denied by server configuration: /usr/local/graphite/webapp/browser, referer: http://graphite/
[Thu Jul 10 11:58:21 2008] [error] [client 10.209.41.166] client denied by server configuration: /usr/local/graphite/webapp/composer, referer: http://graphite/
[Thu Jul 10 11:58:21 2008] [error] [client 10.209.41.166] client denied by server configuration: /usr/local/graphite/webapp/browser, referer: http://graphite/composer/?
[Thu Jul 10 11:58:21 2008] [error] [client 10.209.41.166] client denied by server configuration: /usr/local/graphite/webapp/composer, referer: http://graphite/browser/header/

These are the settings that I have on my local_settings.py file.

# Use this file to override settings defined in settings.py
#Default database settings, sqlite is intended for single-server setups, override these in local_settings.py
DATABASE_ENGINE = 'mysql' # 'postgresql', 'mysql', 'sqlite3' or 'ado_mssql'.
DATABASE_NAME = 'graphite' # Or path to database file if using sqlite3.
DATABASE_USER = 'graphite' # Not used with sqlite3.
DATABASE_PASSWORD = 'graphite' # Not used with sqlite3.
DATABASE_HOST = 'localhost' # Set to empty string for localhost. Not used with sqlite3.
DATABASE_PORT = '3306' # Set to empty string for default. Not used with sqlite3.

I also tried increasing the debug level on everything but with no success.... I don't see any increased verbosity on anywhere.
At this point I'm only trying to see the frontend so I could start later on adding data points and metrics....
Am I missing something here?!

Tkx,

   PECastro

Question information

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

The memcache module is optional, but the use of memcached is on by default (I may change this). To turn it off you have to add the following line to your local_settings.py file:

MEMCACHE_HOSTS = []

As far as the "client denied by server configuration" errors, it is an apache configuration issue. I have run into it myself before and I usually fix it by adding a "Allow from all" line inside the <Location "/"> section of the vhost config. Keep in mind I am not an apache expert and this may not be the ideal way to fix this problem. Let me know if that does not work for you. If you continue to have issues with apache then you could test out Graphite by using the development server, this runs Graphite in a python-based webserver instead of inside apache. It is not recommended for anything but testing/development, but it should give you an easier way to evaluate Graphite. To run the development server you will need to use the latest trunk version or wait until I publish a new release, probably on Monday or Tuesday. If you use the latest trunk then you can run ./lib/scripts/run-graphite-development-server.sh from the top-level of trunk.

As far as your mysql problems, do you have "DEBUG = True" in your local_settings.py? If not then you should turn it on. This will cause the error responses from the webapp to be filled with useful information. However your first problem with the apache configuration is probably preventing your requests from even getting to the webapp in the first place. Once you can get a response back from the webapp itself (any non-apache-generated error page) and have "DEBUG = True" set then we should have enough information to see what the problem is, if there even is one (it might all be the first problem).

Can you help with this problem?

Provide an answer of your own, or ask pecastro for more information if necessary.

To post a message you must log in.