Graphite unreachable #2535
-
Environment:
Additional context |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
Hi @sieuwe, I will assume you followed these guides:
Accessing your Debian server using SSH (or on the console), you can issue the command curl http://localhost:8000/ You should get a response that looks something like this: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
<!-- Copyright 2008 Orbitz WorldWide
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License. -->
<html>
<head>
<title>Graphite Browser</title>
</head>
<frameset rows="80,*" frameborder="1" border="1">
<frame src="/browser/header" name="Header" id='header' scrolling="no" noresize="true" />
<frame src="/composer?" name="content" id="composerFrame"/>
</frameset>
</html> If you get an error instead, then you have not successfully set up your graphite-web server. Did you choose the Apache or the uwsgi option from the guide?
Graphite has two servers: One called Carbon, which receives metrics/data. Another called graphite-web, which is a web application to browse, graph or otherwise fetch the data stored on disk by Carbon. ipdevpoll would only complain if carbon is not reachable. The web frontend tries to contact graphite-web to produce the graphs, and that seems to be where your problem is. |
Beta Was this translation helpful? Give feedback.
-
Seems like Graphite wasn't installed correctly. |
Beta Was this translation helpful? Give feedback.
-
I have set it up as described, but am receiving a '500 Internal server error' on the curl command.
I have the file '/etc/graphite/local_settings.py' and edited this according to the manual. Did the same with the apache part. But as far as I understand it uses the wrong config file? I installed with the Apache VirtualHost option. |
Beta Was this translation helpful? Give feedback.
-
I had the same problem, and I had to comment out the line I found this mentioning the issue: |
Beta Was this translation helpful? Give feedback.
-
@sieuwe, @datagutten is onto something here. We're probably not testing the Apache version of the recipe very diligently these days, since we've done our production deploys using uwsgi for years. If you look at the uwsgi-version of the recipe, it explicitly sets the |
Beta Was this translation helpful? Give feedback.
-
@datagutten |
Beta Was this translation helpful? Give feedback.
I had the same problem, and I had to comment out the line
os.environ.setdefault('GRAPHITE_SETTINGS_MODULE', 'graphite.local_settings') # noqa
in /usr/share/graphite-web/graphite.wsgiAfter restarting apache, graphite-web works.
I found this mentioning the issue:
https://www.mail-archive.com/[email protected]/msg1821989.html