Re: Django debug= false throwing 503 error

2015-12-28 Thread Web Architect
Hi,

Thanks for your response.

I had run the server using runserver and it threw the same error:

December 28, 2015 - 08:57:30

Django version 1.8.4, using settings 'jivaana.settings'

Starting development server at http://0.0.0.0:8600/

Quit the server with CONTROL-C.

HTTPError = 503

*[28/Dec/2015 08:57:31] "GET /catalogue/ HTTP/1.1" 500 2990*

HTTPError = 503

*[28/Dec/2015 08:57:37] "GET /accounts/login/ HTTP/1.1" 500 2990*

HTTPError = 503

*[28/Dec/2015 09:01:55] "GET /catalogue/ HTTP/1.1" 500 2990*


*I am sorry I should have mentioned. After all the above debugging, I was 
clueless what was going wrong.*


The DEBUG and ALLOWED_HOSTS was set as per documentation. Not sure if 
anything more was needed.


Thanks.

On Monday, December 28, 2015 at 3:40:24 PM UTC+5:30, esauro wrote:
>
> Hi,
> I assume the development server is working. If that is the case it could 
> be that you have a problem with your production stack. I remember a 
> situation long time ago (like Django 1.1 or so) a project I run with apache 
> + mod_wsgi and we have a problem like this (I don't remember the error 
> code) because there were a "print" in the code.
>
> So please confirm you can use "runserver"
> * If so, try to put more data on your production stack (web server, 
> wsgi gateway, etc.)
> * If no you'll probably have much more data to fix the problem.
>
> Regards,
> Esau.
>
>
>
> On Mon, Dec 28, 2015 at 8:46 AM, Web Architect  > wrote:
>
>> Hi,
>>
>> I have set the following in settings.py for our production system:
>>
>> DEBUG=False
>>
>> ALLOWED_HOSTS = ['*'] (in fact any value is not working)
>>
>> The server is throwing "HTTPError = 503". 
>>
>> There are no logs and I am clueless about the reason for the error. I 
>> tried searching the net and looking into DJango documents but couldn't find 
>> the possible reason.
>>
>> Django version is 1.8.3. 
>>
>> Would really appreciate if anyone could help with the above.
>>
>> Thanks.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Esaú Rodríguez
> esa...@gmail.com 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/284d41eb-fbba-469c-b9e0-148b65daf38c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django debug= false throwing 503 error

2015-12-28 Thread Web Architect
I had run the server locally using ./manage.py runserver and it threw the 
error on the console:

December 28, 2015 - 08:57:30

Django version 1.8.4, using settings 'jivaana.settings'

Starting development server at http://0.0.0.0:8600/

Quit the server with CONTROL-C.

HTTPError = 503

*[28/Dec/2015 08:57:31] "GET /catalogue/ HTTP/1.1" 500 2990*

HTTPError = 503

*[28/Dec/2015 08:57:37] "GET /accounts/login/ HTTP/1.1" 500 2990*

HTTPError = 503

*[28/Dec/2015 09:01:55] "GET /catalogue/ HTTP/1.1" 500 2990*


*I do not have any other logs which I could share. If any more info is 
needed, I could try to gather.*


*Thanks.*

On Monday, December 28, 2015 at 3:08:01 PM UTC+5:30, monoBOT monoBOT wrote:
>
> ​Your server is not working, the first thing to do always is see what is 
> the error message:
>
> 503 Service Unavailable
>
> The server is currently unable to handle the request due to a temporary 
> overloading or maintenance of the server. The implication is that this is a 
> temporary condition which will be alleviated after some delay. If known, 
> the length of the delay MAY be indicated in a Retry-After header. If no 
> Retry-After is given, the client SHOULD handle the response as it would for 
> a 500 response.
>
> Note: The existence of the 503 status code does not imply that a server 
> must use it when becoming overloaded. Some servers may wish to simply 
> refuse the connection.
>
> When you face similar things you should test them locally (with manage.py 
> runserver) with the exact same configuration for django to show you the 
> error message.​ 
> You have not explained too much so we can not help you more.
>
>
> 2015-12-28 8:46 GMT+00:00 Web Architect :
>
>> Hi,
>>
>> I have set the following in settings.py for our production system:
>>
>> DEBUG=False
>>
>> ALLOWED_HOSTS = ['*'] (in fact any value is not working)
>>
>> The server is throwing "HTTPError = 503". 
>>
>> There are no logs and I am clueless about the reason for the error. I 
>> tried searching the net and looking into DJango documents but couldn't find 
>> the possible reason.
>>
>> Django version is 1.8.3. 
>>
>> Would really appreciate if anyone could help with the above.
>>
>> Thanks.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> *monoBOT*
> Visite mi sitio(Visit my site): monobotsoft.es/blog/
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/060a429d-06a1-4232-a316-b2fcfaea922f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django debug= false throwing 503 error

2015-12-28 Thread Web Architect
Thanks for your message.

On Production, I am running the server behind Nginx. Its run using uwsgi. 
The server works fine with "DEBUG=True" but when it's set to false, it 
throws http 503 error. I saw it in uwsgi logs. Also, when I ran the server 
locally with ./manage.py runserver, its on the console.

Thanks.

On Monday, December 28, 2015 at 3:01:39 PM UTC+5:30, aRkadeFR wrote:
>
> Hello,
>
> How do you run your server in production?
> Where do you see the server throwing the 503 error?
>
> Thanks,
>
> On 12/28/2015 09:46 AM, Web Architect wrote:
>
> Hi, 
>
> I have set the following in settings.py for our production system:
>
> DEBUG=False
>
> ALLOWED_HOSTS = ['*'] (in fact any value is not working)
>
> The server is throwing "HTTPError = 503". 
>
> There are no logs and I am clueless about the reason for the error. I 
> tried searching the net and looking into DJango documents but couldn't find 
> the possible reason.
>
> Django version is 1.8.3. 
>
> Would really appreciate if anyone could help with the above.
>
> Thanks.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users...@googlegroups.com .
> To post to this group, send email to django...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> 
> https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> aRkadeFR
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ccd569ad-e8a4-4670-a0b9-47d494f5847e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django debug= false throwing 503 error

2015-12-28 Thread Esau Rodriguez
Hi,
I assume the development server is working. If that is the case it could be
that you have a problem with your production stack. I remember a situation
long time ago (like Django 1.1 or so) a project I run with apache +
mod_wsgi and we have a problem like this (I don't remember the error code)
because there were a "print" in the code.

So please confirm you can use "runserver"
* If so, try to put more data on your production stack (web server,
wsgi gateway, etc.)
* If no you'll probably have much more data to fix the problem.

Regards,
Esau.



On Mon, Dec 28, 2015 at 8:46 AM, Web Architect  wrote:

> Hi,
>
> I have set the following in settings.py for our production system:
>
> DEBUG=False
>
> ALLOWED_HOSTS = ['*'] (in fact any value is not working)
>
> The server is throwing "HTTPError = 503".
>
> There are no logs and I am clueless about the reason for the error. I
> tried searching the net and looking into DJango documents but couldn't find
> the possible reason.
>
> Django version is 1.8.3.
>
> Would really appreciate if anyone could help with the above.
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Esaú Rodríguez
esa...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAB4Jw77oU1kmem6vbo-y0HJoCqvmx%3DZjnimxtX9x2tSLPyhijA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django debug= false throwing 503 error

2015-12-28 Thread monoBOT
​Your server is not working, the first thing to do always is see what is
the error message:

503 Service Unavailable

The server is currently unable to handle the request due to a temporary
overloading or maintenance of the server. The implication is that this is a
temporary condition which will be alleviated after some delay. If known,
the length of the delay MAY be indicated in a Retry-After header. If no
Retry-After is given, the client SHOULD handle the response as it would for
a 500 response.

Note: The existence of the 503 status code does not imply that a server
must use it when becoming overloaded. Some servers may wish to simply
refuse the connection.

When you face similar things you should test them locally (with manage.py
runserver) with the exact same configuration for django to show you the
error message.​
You have not explained too much so we can not help you more.


2015-12-28 8:46 GMT+00:00 Web Architect :

> Hi,
>
> I have set the following in settings.py for our production system:
>
> DEBUG=False
>
> ALLOWED_HOSTS = ['*'] (in fact any value is not working)
>
> The server is throwing "HTTPError = 503".
>
> There are no logs and I am clueless about the reason for the error. I
> tried searching the net and looking into DJango documents but couldn't find
> the possible reason.
>
> Django version is 1.8.3.
>
> Would really appreciate if anyone could help with the above.
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*monoBOT*
Visite mi sitio(Visit my site): monobotsoft.es/blog/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2BxOsGAA%3DgESnoEOWT1XstS2nZUOyJ5eCRHWt8NmzzkMdB89zA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django debug= false throwing 503 error

2015-12-28 Thread aRkadeFR

Hello,

How do you run your server in production?
Where do you see the server throwing the 503 error?

Thanks,

On 12/28/2015 09:46 AM, Web Architect wrote:

Hi,

I have set the following in settings.py for our production system:

DEBUG=False

ALLOWED_HOSTS = ['*'] (in fact any value is not working)

The server is throwing "HTTPError = 503".

There are no logs and I am clueless about the reason for the error. I 
tried searching the net and looking into DJango documents but couldn't 
find the possible reason.


Django version is 1.8.3.

Would really appreciate if anyone could help with the above.

Thanks.
--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com 
.
To post to this group, send email to django-users@googlegroups.com 
.

Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
aRkadeFR

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5681010B.9060600%40arkade.info.
For more options, visit https://groups.google.com/d/optout.


Django debug= false throwing 503 error

2015-12-28 Thread Web Architect
Hi,

I have set the following in settings.py for our production system:

DEBUG=False

ALLOWED_HOSTS = ['*'] (in fact any value is not working)

The server is throwing "HTTPError = 503". 

There are no logs and I am clueless about the reason for the error. I tried 
searching the net and looking into DJango documents but couldn't find the 
possible reason.

Django version is 1.8.3. 

Would really appreciate if anyone could help with the above.

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a3a76d7c-438c-442d-a68b-3d31859b4708%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.