Error when using apache 2.4.6

67 views
Skip to first unread message

Jasvir Singh

unread,
Jan 17, 2014, 3:59:32 AM1/17/14
to django...@googlegroups.com
Hello everyone.
I am facing a problem when I access it in browser. I need your help to
solve this error.
I am using apache 2.4.6 as web server and django-1.5.2 as framework.
Here are my httpd.conf file and wsgi script:
http://paste.ubuntu.com/6766758/
http://paste.ubuntu.com/6766759/

When ever I access localhost/automation, it gives following error :
http://pbrd.co/KmTP4Y

Please feel free to ask anything else.

--
Jasvir Singh Grewal
www.jsgrewal.com

Andrew Farrell

unread,
Jan 17, 2014, 10:07:42 AM1/17/14
to django...@googlegroups.com
To bisect your problem, I think that the error happens before the wsgi file even runs.
you can test this by putting
assert False at the top of /home/jass/Automation/apache/django.wsgi and seeing if the error changes to a 500. If it doesn't, I'm right. If it does, the problem is in django.wsgi

Given that,
What does `ls -la /home/jass/Automation/apache/` say?
What about `tail -n 140 /var/log/apache2/error.log`


--
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAN_O85uhhWz1pDtDED9iwphk3oRRCn6QMP4Vd_so%2BwC3OM2zvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Sandeep kaur

unread,
Jan 17, 2014, 10:23:17 AM1/17/14
to django-users

On Fri, Jan 17, 2014 at 2:29 PM, Jasvir Singh <jassig...@gmail.com> wrote:
>
> I am using apache 2.4.6 as web server and django-1.5.2 as framework.
> Here are my httpd.conf file and wsgi script:
> http://paste.ubuntu.com/6766758/
> http://paste.ubuntu.com/6766759/

According to me, in your wsgi file, change
sys.path.append('/home/jass') 
to 
sys.path.append('/home/jass/')

that means add slash at the end.

--
Sandeep Kaur
E-Mail: mkaur...@gmail.com
Blog: sandymadaan.wordpress.com



Jasvir Singh

unread,
Jan 17, 2014, 1:37:53 PM1/17/14
to django...@googlegroups.com
On Fri, Jan 17, 2014 at 8:37 PM, Andrew Farrell <armors...@gmail.com> wrote:
> To bisect your problem, I think that the error happens before the wsgi file
> even runs.
> you can test this by putting
> assert False at the top of /home/jass/Automation/apache/django.wsgi and
> seeing if the error changes to a 500. If it doesn't, I'm right. If it does,
> the problem is in django.wsgi

yes you are right. When I removed wsgi file, error remains same

> Given that,
> What does `ls -la /home/jass/Automation/apache/` say?
total 12
drwxrwxrwx 2 jass jass 4096 Jan 17 23:57 .
drwxrwxrwx 11 jass jass 4096 Jan 17 17:28 ..
-rw-r----- 1 jass jass 203 Jan 17 23:57 django.wsgi

> What about `tail -n 140 /var/log/apache2/error.log`

https://gist.github.com/jasvir99/8478976

Jasvir Singh

unread,
Jan 17, 2014, 1:38:26 PM1/17/14
to django...@googlegroups.com
On Fri, Jan 17, 2014 at 8:53 PM, Sandeep kaur <mkaur...@gmail.com> wrote:
> that means add slash at the end.

No, It didn't works.

carlos

unread,
Jan 17, 2014, 3:37:41 PM1/17/14
to django...@googlegroups.com
Hi i remember one time i try use de version apache 2.4.6 with django and virtualhost but never work correctly
and change apache for nginx i resolved my problem :)

Cheers


--
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 http://groups.google.com/group/django-users.

parnigot

unread,
Jan 17, 2014, 4:17:01 PM1/17/14
to django...@googlegroups.com
Il 17/01/14 19:38, Jasvir Singh ha scritto:
On Fri, Jan 17, 2014 at 8:53 PM, Sandeep kaur <mkaur...@gmail.com> wrote:
that means add slash at the end.
No, It didn't works.

You should try to use the new configuration directives for Apache 2.4.
For more information see here on the Apache documentation.
-- 
e.p.
Reply all
Reply to author
Forward
0 new messages