Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-31 Thread Josh Cartmell
Thanks again for the help Steve! I ended up figuring it out and feel a bit silly now, I had some CDN hosted javascript inside the compress template tag resulting in an incompressible file error. My biggest question at this point is which log file should I have found that in. I'm still wondering

Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-31 Thread Doug Evenhouse
I'm interested in the gunicorn logging question as well. I had a similar issue as yours Josh and ended up putting the following line in the gunicorn.conf.py file of my project in order to get some logged output that led me to the cause of the error. errorlog = /tmp/gunicorn.error.log On

Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-31 Thread Matthew Summers
Just for reference, --log-file and --error-logfile are the same http://docs.gunicorn.org/en/latest/settings.html#errorlog Cheers, Matt -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails

Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-31 Thread Josh Cartmell
Thanks Matt and Doug, that's very helpful. So logging is disabled by default and then enabled if you specify a file location? On Mon, Mar 31, 2014 at 2:05 PM, Matthew Summers msummer...@gmail.comwrote: Just for reference, --log-file and --error-logfile are the same

Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-31 Thread Stephen McDonald
As I understand supervisor will log stdout/stderr for any procs it manages under /var/log/supervisord), such as gunicorn. This is why gunicorn's own logging is disabled in the default setup. Maybe it'd be better to configure the opposite (gunicorn logs all and sends nothing to stdout/stderr),

Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-31 Thread Josh Cartmell
Thanks Steve and Matt, I'm running with DEBUG = False now which is great. I think you are spot on Steve, I see now that the supervisor directory in /var/log has three log files, and two of them appear to be specific to gunicorn. I'm guessing that will help me moving forwards, and is probably

Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-30 Thread Stephen McDonald
I can't reproduce this - just did deploy of Mezzanine 3.0.9 to a fresh ubuntu 12.04 machine without any issue. Only thing I can think of is some mismatch between ALLOWED_HOSTS, Site objects, and NGINX config - triple check those since the behaviour changes with DEBUG False. On Sat, Mar 29, 2014

Re: [mezzanine-users] Default fabfile deploy, Internal Server Error

2014-03-30 Thread Josh Cartmell
Thanks for giving it a shot Steve! I didn't get it to work yet (since it was just a non production demo I was satisfied to leave it with DEBUG True). I'll triple check those things in the morning and let you know how it goes. By the way, does gunicorn have a log of it's own or is it logged with