graphite-dev team mailing list archive

[Nate Campbell <question218547@xxxxxxxxxxxxxxxxxxxxx>]

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

Nate Campbell posted a new comment:
You are correct - the carbon-cache process was still functioning
correctly. Now that I have worked around the problem I understand it a
little bit better. Basically, my apache configuration never had a
Directory directive allowing access to /opt/graphite/webapp/content. My
webapp error.log file contained a lot of lines like:

[Mon Jan 07 11:40:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/ext/resources/css/ext-all.css, referer: http://ndmnvc-ops002:8010/composer/?
[Mon Jan 07 11:40:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/ext/adapter/ext/ext-base.js, referer: http://ndmnvc-ops002:8010/composer/?
[Mon Jan 07 11:40:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/ext/ext-all.js, referer: http://ndmnvc-ops002:8010/composer/?
[Mon Jan 07 11:40:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/composer_widgets.js, referer: http://ndmnvc-ops002:8010/composer/?
[Mon Jan 07 11:41:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/ext/resources/css/ext-all.css, referer: http://ndmnvc-ops002:8010/composer/?
[Mon Jan 07 11:41:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/ext/adapter/ext/ext-base.js, referer: http://ndmnvc-ops002:8010/composer/?
[Mon Jan 07 11:41:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/ext/ext-all.js, referer: http://ndmnvc-ops002:8010/composer/?
[Mon Jan 07 11:41:57 2013] [error] [client 10.1.72.33] client denied by server configuration: /opt/graphite/webapp/content/js/composer_widgets.js, referer: http://ndmnvc-ops002:8010/composer/?

The strange thing is that the UI functionality that seems to rely on
those javascript files was working correctly when I first finished the
graphite install, even though Apache wasn't allowing access to the
content at that time either. The UI only became unusable after I invoked
the "configureUI" function for the first time using the navbar buttons.
Adding this directive to my Apache config and restarting apache fixed
the issue:

        <Directory> /opt/graphite/webapp/content/>
                Order deny,allow
                Allow from all
        </Directory>

So, I am no longer having a problem with this and honestly it seems like
I was doing it wrong the whole time. My remaining confusion simply stems
from the fact that the UI worked in the first place when I didn't have
Apache configured correctly, and then I was somehow able to trigger a
break in functionality via navbar buttons.

I no longer need an answer on this but I am happy to work with you
further if you are interested in reproducing it.

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