no wsp files being written to disk

Asked by jasonleitch

I don't know what crazy hell I've found myself in, but I'm in it. I have 3 systems running 3 separate broken graphite installs. As far as i'm aware I'd like to take a step back and say this isn't rocket science. I don't know if this is a centos issue or if it's just me but god damn i'm about ready to just no care anymore. I have a lot going on at work and this is part of a big project and I'm literally getting no where. I'm not a programmer and i'm not a developer I have extensive linux knowledge and i'm a network admin. I know some python and i'm not stupid. Get this:

The problem

so just to be clear

machine 1
carbon
  writes wsp files to disk
     doesn't show folder structure in webui
     console.log has traceback erros on site-packages I have
     no idea how to fix or where to start

NOTE
log files report writes with SOME values
now broken and just shows NONE
graphite.db file has grown in size

machine 2
carbon
   can't write files to disk
      shows folder structure in webui

NOTE
log files report carbon writes value NONE
graphite.db has grown in size

when I fix it (via local_settings) variable to show the entire root / on machine one in the webui
the wsp files show up but immediately broke LOL

initial set up
What did I do (the jist)
I installed
some deps
whisper
carbon
graphite-web

I checked deps with the .py file.
Installed any other deps I could find from online resources.
I ran the setup.py files. Created the carbon.conf schema and wsgi files,
     set USER = carbon
     mostly kept everything else to default
I hosted the site on apache vhost and all.
Created the users,
Set the permission
Created and synced the db file
I started the carbon-cache.py

HEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEELP!

Question information

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

The night really is darkest just before the dawn, I had some crazy Django issue or something major conflicts my test environment got all messed, I removed every shred of it and contained and kept track of it a lot better and it appears to be working. Great learning experience trying to juggle so much.

Advice: Use pip