I was able to fix the problem I was having and successfully deployed.

I started over from a basic mezzanine project.  It worked perfectly.  Then 
I slowly merged in my settings and apps.  I'm using amazon s3 for my cdn 
and everything snapped together fine.  There was a few things I had to 
adjust to get the filebrower working with s3 but I expected that :)

I believe the original cause of the issue was I was working in the wrong 
virtualenv which caused a bunch of issues with supervisor.  While I was 
able to fix the issues with supervisor I was ultimately in the wrong 
virtualenv which caused problems with gunicorn.

Thanks for the help!





On Thursday, January 16, 2014 6:35:58 AM UTC-5, Klamann, Norbert wrote:
>
> I repeated the whole exercise and now it works .
>
> gunicorn.conf.py is changed an looks like that.
>
> mezzanine@wsa02:~/mezz_test/project$ cat gunicorn.conf.py
>
> from __future__ import unicode_literals
> import multiprocessing
> bind = "127.0.0.1:8000"
> workers = multiprocessing.cpu_count() * 2 + 1
> loglevel = "error"
> proc_name = "mezz_test"
>
> Now I get a Error 500  when I visit the new instance but that is another 
> problem i presume.
>
>
> Thanks for your help
>
> Norbert
>
>
>
>
>
>
> 2014/1/16 Stephen McDonald <st...@jupo.org <javascript:>>
>
>> Thanks Harry
>>
>> FWIW my successful test used 8000 for the gunicorn port.
>>
>>
>> On Thu, Jan 16, 2014 at 11:32 AM, <har...@iinet.net.au <javascript:>>wrote:
>>
>>> At least for the most basic deployment of mezzanine (ie. no custom theme 
>>> app yet) I seem to have resolved the issue.
>>>
>>> Although I did a few different things, I think that the major factor was 
>>> changing the gunicorn port from 8000 to anything else (8001, 8888).
>>>
>>> I'll keep you posted as to whether this moment of success persists.
>>>
>>> Harry
>>>
>>>
>>> On Friday, 10 January 2014 13:41:31 UTC+8, har...@iinet.net.au wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> I'm very new to Mezzanine and have been loving it --- especially the 
>>>> fabric deploment.  However, I seem to be having some troubles with 
>>>> gunicorn.
>>>>
>>>> I started from a fresh linode running debian and allowed 'fab all' to 
>>>> build the full system.
>>>>
>>>> I would very much appreciate some assistance with this.
>>>>
>>>> My basic process is:
>>>>
>>>> server:
>>>>
>>>> new linode profile
>>>> ssh as root
>>>> adduser user
>>>> apt-get install sudo vim
>>>> add harry to sudoers file
>>>> on local machine:
>>>> ssh-copy-id -i ~/.ssh/id_rsa.pub
>>>> sudo pip install virtualenvwrapper
>>>> add to bashrc:
>>>>
>>>> export WORKON_HOME=$HOME/.virtualenvs
>>>> source /usr/local/bin/virtualenvwrapper.sh
>>>> export PIP_VIRTUALENV_BASE=$WORKON_HOME
>>>>
>>>> local:
>>>>
>>>> mkvirtualenv black_earth_{project}
>>>> pip install -r requirements.txt
>>>> createdb {project}
>>>> mezzanine-project {project}
>>>> set database parameters in local_settings.py
>>>> copy keys and deploy setting (FABRIC) to local_settings.py
>>>> set allowed_hosts in settings.py
>>>> ALLOWED_HOSTS = [
>>>>     'localhosts',
>>>>     '.mysite.org.au',
>>>> ]
>>>> python manage.py createdb
>>>> check local server
>>>> set up git repository
>>>> git init
>>>> git add .
>>>> git  git remote add origin {gitserver}
>>>> git push -u origin master
>>>> pip freeze > requirements.txt
>>>> fab all
>>>>
>>>> pip error:
>>>> sudo pip install setuptools --no-use-wheel --upgrade
>>>>
>>>> At the final point in the deployment --- restart --- I get the error:
>>>>
>>>> $ supervisorctl start black_earth_semina:gunicorn_black_earth_semina ->
>>>>
>>>> [blackearthcollective.org.au] out: sudo password:
>>>> [blackearthcollective.org.au] out: 
>>>> black_earth_semina:gunicorn_black_earth_semina: 
>>>> ERROR (abnormal termination)
>>>> [blackearthcollective.org.au] out: 
>>>>
>>>> This is with a completely standard mezzanine setup.  I thought that the 
>>>> problem was with my theme project.
>>>>
>>>> from the supervisor gunicorn log:
>>>>
>>>> !!!
>>>> !!! WARNING: This command is deprecated.
>>>> !!!
>>>> !!!     You should now run your application with the WSGI interface
>>>> !!!     installed with your project. Ex.:
>>>> !!!
>>>> !!!         gunicorn myproject.wsgi:application
>>>> !!!
>>>> !!!     See https://docs.djangoproject.com/en/1.4/howto/deployment/
>>>> wsgi/gunicorn/
>>>> !!!     for more info.
>>>> !!!
>>>>
>>>> 2014-01-10 01:16:35 [12088] [CRITICAL] WORKER TIMEOUT (pid:12097)
>>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to mezzanine-use...@googlegroups.com <javascript:>.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> -- 
>> Stephen McDonald
>> http://jupo.org 
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Mezzanine Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/mezzanine-users/Ltmdrd3D2aw/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> mezzanine-use...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to