I've run the installer script twice as well as doing a manual install
with the same results each time. I keep getting internal server 500
errors from the required apps installed in site-packages, so it seems
like there's some problem with my virtualenv/lib/python2.4/site-
packages directory being recognized when settings.py is loaded. I also
tried virtualenv with the --no-site-packages option and setting up the
environment as outlined in the virtualenv docs:
activate_this = '/path/to/env/bin/activate_this.py'
execfile(activate_this, dict(__file__=activate_this))
passenger_wsgi.py:
import sys, os
INTERP = "/home/username/local/bin/python2.4"
if sys.executable != INTERP: os.execl(INTERP, INTERP, *sys.argv)
sys.path.append("/home/username/mysite.com")
os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings'
import django.core.handlers.wsgi
application = django.core.handlers.wsgi.WSGIHandler()
error.log:
[Tue Sep 22 20:32:32 2009] [error] [client 67.171.62.103] Premature
end of script headers:
[Tue Sep 22 20:32:35 2009] [error] [client 67.171.62.103] Premature
end of script headers: internal_error.html
On Sep 18, 6:33 pm, Chris Moffitt <[email protected]> wrote:
> I suspect this has to do with some of the challenges that "C" mentioned
> above. As much as we try to standardize, there's plenty of ways that sys
> admins and distributions change the way they do things that can break this
> process.
>
> Thanks for hanging in there with the process.
>
> -Chris
>
> On Fri, Sep 18, 2009 at 5:16 PM, bobhaugen <[email protected]> wrote:
>
> > On Sep 18, 3:25 pm, C <[email protected]> wrote:
> > > bobhaugen,
> > > Your inability to indicate step by step what you did,
>
> > I followed the steps 1 thru 6 in
> >http://bitbucket.org/chris1610/satchmo/wiki/ImprovedInstallationProcess
> > twice, exactly as written. Both times, copying and pasting from the
> > page.
>
> > > or atleast
> > > provide a transcript from the terminal window(s) you did things from
> > > makes problem determination difficult. If it would be possible for
> > > you to clean up earlier attempts, bring up a terminal window, run
> > > 'script -o /tmp/satchmo_intall.log', and go through the full set of
> > > steps, and send that here, it would be appreciated. Even more
> > > appreciated would be a 'which pip; which getsatchmo.py' after #5
> > > easy_install pip included in your transcript.
>
> > script -o was not accepted.
> > did script -a
>
> > which pip
>
> > /home/bob/satchmostore/bin/pip
>
> > which getsatchmo.py
>
> > /home/bob/satchmostore/bin/getsatchmo.py
>
> > *But* this time, step 6 worked. Ended up with getsatchmo.py, which
> > had not happened the previous times.
>
> > And then everything else worked, and I now have a running Satchmo
> > store!
>
> > Only difference on my end was that I rebooted before the last try.
> > Or, the 3rd time is the charm.
>
> > I can dbpaste the satchmo_install.log if anybody wants it...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/satchmo-users?hl=en
-~----------~----~----~----~------~----~------~--~---
