Re: django problem at dreamhost

[Jaanus]

> Does the "apps" directory have an __init__.py file in it? Generally
> that "no module named..." error signifies there's no __init__.py.

ha! that may have been it. killed apps now so cant check, but this may
have been it. thanks for the pointer.


-- 
rgds,
Jaanus


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Adrian Holovaty]

On 3/20/06, Jaanus <[EMAIL PROTECTED]> wrote:
> I can understand this and this all makes sense. What doesn't make sense
> though, is that if the app lives in the "apps" directory, Django tells
> me "no module named apps" - although all the settings are correct and
> it works in another host with the same settings.

Does the "apps" directory have an __init__.py file in it? Generally
that "no module named..." error signifies there's no __init__.py.

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Jaanus]

limodou wrote:
> It'll setup a app named appname in current directory, but not apps
> directory. So if you want to create a new app in apps directory, you
> should go into apps directory, and run the django-admin.py. Or create
> the app manually it easy.

I can understand this and this all makes sense. What doesn't make sense
though, is that if the app lives in the "apps" directory, Django tells
me "no module named apps" - although all the settings are correct and
it works in another host with the same settings.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[limodou]

On 3/20/06, Jaanus <[EMAIL PROTECTED]> wrote:
>
> hmm.. and just as I wrote this, I noticed the Django demo page on that
> Linux host says...
>
> "Start your first app by running trmproject/manage.py startapp
> [appname]."
>
> After I did it, the new app showed up right in the project's directory,
> without "apps". So in one host it is with "apps" and in another it's
> not. What's the logic behind that? At least I got it to work for myself
> but would be good to know...
>

In a directory, if you run manage.py startapp appname

It'll setup a app named appname in current directory, but not apps
directory. So if you want to create a new app in apps directory, you
should go into apps directory, and run the django-admin.py. Or create
the app manually it easy.

cd apps
mkdir appname
cd appname
>__init__.py

that's ok. If you need models.py:

>models.py

if you need urls.py

>urls.py

if you need views.py

>views.py

>filename represents create a empty file, and you can copy code from
existed files to it.

--
I like python!
My Blog: http://www.donews.net/limodou
NewEdit Maillist: http://groups.google.com/group/NewEdit

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[James Bennett]

On 3/19/06, Jaanus <[EMAIL PROTECTED]> wrote:
> After I did it, the new app showed up right in the project's directory,
> without "apps". So in one host it is with "apps" and in another it's
> not. What's the logic behind that? At least I got it to work for myself
> but would be good to know...

This may be due to different versions of Django; the "apps" directory
is no longer automatically created (though you can create it
yourself); instead, apps live directly under the project: where with
older revisions of Django you'd get 'myproject.apps.myapp', now you
get 'myproject.myapp'.


--
"May the forces of evil become confused on the way to your house."
  -- George Carlin

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Jaanus]

hmm.. and just as I wrote this, I noticed the Django demo page on that
Linux host says...

"Start your first app by running trmproject/manage.py startapp
[appname]."

After I did it, the new app showed up right in the project's directory,
without "apps". So in one host it is with "apps" and in another it's
not. What's the logic behind that? At least I got it to work for myself
but would be good to know...


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Jaanus]

This "no module named apps" is driving me nuts. Anyone, please help. I
took the settings from my Windows laptop where it worked, and am trying
to install in a Linux host. Here's the dump of "sqlreset", so this
happens even before I ever get around to getting anything to run on the
server. The Django versions are the same (0.91 - also tried with SVN
trunk - getting the same) and I've double-and triple-checked all the
paths and settings.

[hostname]$ django-admin.py sqlreset appname
Traceback (most recent call last):
  File "/home/jaanus/django/django_src/django/bin/django-admin.py",
line 5, in ?
management.execute_from_command_line()
  File "/home/jaanus/django/django_src/django/core/management.py", line
903, in execute_from_command_line
translation.activate('en-us')
  File "/home/jaanus/django/django_src/django/utils/translation.py",
line 192, in activate
_active[currentThread()] = translation(language)
  File "/home/jaanus/django/django_src/django/utils/translation.py",
line 181, in translation
default_translation = _fetch(settings.LANGUAGE_CODE)
  File "/home/jaanus/django/django_src/django/utils/translation.py",
line 164, in _fetch
app = getattr(__import__(appname[:p], {}, {}, [appname[p+1:]]),
appname[p+1:])
ImportError: No module named apps


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Jeremy Jones]

On Sat, 25 Feb 2006 15:32:42 -0800
"Bryant" <[EMAIL PROTECTED]> wrote:

> 
> I have what I think is a similar problem - first time posting here so
> please, be gentle.
> 
> I followed the instructions on the Django on Dreamhost wiki and
> correctly installed django. Everything seems to work fine... database
> tables are as expected... then I try to access mydomain.com/admin or
> mydomain.com/django.fcgi.
> 
> After trying for several minutes, I get a 500: the error says "comm
> with (dynamic) server aborted" and "incomplete headers (0 bytes)
> received from server." However, when I run the sample hello.fcgi to
> verify that FastCGI is running, it works fine.

Welcome to the fastcgi club.  This is one thing that just drives me
absolutely nuts about fastcgi.  I had the same problem with my
TurboGears app and I occasionally have the problem with Django.
Assuming everything really is setup right, just try killing all of your
fastcgi processes, wait 15 minutes, and try again.  It appears that
Dreamhost has something setup to not allow too many fastcgi processes
to spawn too quickly, so if you kill everything and wait a little bit,
you'll be starting with a clean slate.  I hope this works for you.

> 
> Is there something wrong with the latest Django WSGI handler (I
> installed via svn) or is it something in my configuration that's
> causing this (to me) inexplicable error? Is this a Dreamhost only
> issue?

It could possibly be your configuration.  I doubt it's Django
specifically.  I'm running 0.91 (not SVN).  It may or may not be
Dreamhost.  I suspect fastcgi, but that's just me and my male
intuition.  

- jmj

> 
> Bryant Cutler
> bryantcutler.com
> 
> 
> 

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Bryant]

I have what I think is a similar problem - first time posting here so
please, be gentle.

I followed the instructions on the Django on Dreamhost wiki and
correctly installed django. Everything seems to work fine... database
tables are as expected... then I try to access mydomain.com/admin or
mydomain.com/django.fcgi.

After trying for several minutes, I get a 500: the error says "comm
with (dynamic) server aborted" and "incomplete headers (0 bytes)
received from server." However, when I run the sample hello.fcgi to
verify that FastCGI is running, it works fine.

Is there something wrong with the latest Django WSGI handler (I
installed via svn) or is it something in my configuration that's
causing this (to me) inexplicable error? Is this a Dreamhost only
issue?

Bryant Cutler
bryantcutler.com


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[MC]

I too have had issues with dreamhost concerning core files and
performance. Every week I'll find a build up of 4-5 core.* dumped
files. And most of the time my site gutata.com performs very slowly on
gower.dreamhost.com. Granted I'm using the cheapest package and perhaps
I have a slow implementation, but even for simpler apps where I'm just
doing get_list, such as whitenoise.gutata.org or its admin page, 7 out
of 10 times, it's very slow.

I get 500 server errors but almost never. Nevertheless, these issues
are unacceptable. I think I'll be switching to a new host soon.

Jeremy Jones wrote:
> On Mon, 20 Feb 2006 02:37:20 +0530
> "Amit Upadhyay" <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I am facing a weird issue with dream host, day before yesterday my
> > django application stopped serving requests, I have not done
> > anything, and its been working since about a month, and now it waits
> > for minutes before give me 500 interneral server error. Also I get
> > lots of core files in my domain folder. Has anyone seen something
> > like this happening with their django application hosted on dreamhost?
> >
>
> I've been seeing some weirdness with Dreamhost over the past couple of
> days.  My site appears to be holding up, though.  Shell access is
> painfully slow.  I have some core files in my domain directory as
> well.  Stats from my checker show a slower response time than normal
> with some of my highest response times happening in the past couple of
> days and a bunch of errors - looks like the output from my checker view
> is null.  Guess I'll have to trap HTTP headers as well.  Seems like
> there is always some mention of Dreamhost on this list and the
> TurboGears list - and it's usually not good.  I think each user has a
> potential for a widely varying experience.
> 
> - jmj


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[[EMAIL PROTECTED]]

I'm on Debian, but that's because I have another couple of Debian
servers already.
It's very good, but the stable release won't have the latest versions
of newer software.

I use a stable release, then added other software manually, eg
lighttpd. That caused a few version conflicts with APT (the package
management in Debian) but they were easily fixed.

Rimu now offer Ubuntu, which is Debian based and supposed to be more
up-to-date, but I haven't used it.

Derek


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Spider]

Derek, what Linux distribution are your running at rimuhosting.com? I'm
about to sign up with them myself. Thanks


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[[EMAIL PROTECTED]]

should have said, I don't use Dreamhost, so this has nothing to do with
their setup.

I'm on rimuhosting.com, which is great.

Derek


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[[EMAIL PROTECTED]]

I had this problem recently.  I had built a small project to learn
Django in january, using the latest trunk source.  It worked fine, so
when I started a second project about 2 weeks ago, I used the same
structure with project/apps/myapp1 ...

But I got the same error: 'no module named apps'. I changed all sorts
of stuff, but then noticed that in the latest documentation, the apps
directory has gone.  So I put my apps directly in the project
directory, and it worked.

I've just moved onto the magic-removal branch, and it's the same, but
also the models directory seems to be gone as well :)  I had to put my
models into models.py in the app directory.  Didn't find this in the
docs, but found some mentions in group messages, and in the source.

Otherwise, the magic-removal move was painfree- just a lot of small
changes.

Derek


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Lachlan Cannon]

I've been having 500 errors at Dreamhost too. The week before last I finished 
my 
site, had it up and running and everything was fine. Then checked it on the 
next 
Monday, and having not changed anything I was getting 
 this mess. Dreamhost say they haven't changed 
anything on the server... I've tried redownloading django fresh from svn and 
that hasn't cleared it up. Has anyone else had a problem like this?

Thanks.
-- 
Lach
Personal: http://illuminosity.net/
Business: http://taravar.com/




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Eugene Lazutkin]

Amit Upadhyay wrote:
> 
> How do you get a new machine? Will I have to create a new account?

1) I think it is the right time to contact DreamHost's support: 
https://panel.dreamhost.com/index.cgi?tree=support.msg, and let them 
know about your problems.

2) W.r.t. RoR's #5. If you use flup or its derivatives, you may try 
asking Allan Saddi (the creator of flup) how to implement #5 suggestion. 
It should be possible.

Thanks,

Eugene


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Amit Upadhyay]

On 2/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I have had this exact same experience.  I do not know what causes it tohappen or what makes it fix itself.  I thought the problem was relatedto the new svn feature.  Have you started using that?
I do not use the new svn feature, but I have used command line svn since before they started the new feature. 
I have a few domains hosted at dreamhost (on different machines).  Onemachine has had problems (squirm) while another machine has been fine.How do you get a new machine? Will I have to create a new account? 
-- Amit UpadhyayBlog: http://www.rootshell.be/~upadhyay+91-9867-359-701
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django users" group.  To post to this group, send email to django-users@googlegroups.com  To unsubscribe from this group, send email to [EMAIL PROTECTED]  For more options, visit this group at http://groups.google.com/group/django-users  -~--~~~~--~~--~--~---

Re: django problem at dreamhost

[[EMAIL PROTECTED]]

I have had this exact same experience.  I do not know what causes it to
happen or what makes it fix itself.  I thought the problem was related
to the new svn feature.  Have you started using that?

I have a few domains hosted at dreamhost (on different machines).  One
machine has had problems (squirm) while another machine has been fine.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Jeremy Jones]

On Mon, 20 Feb 2006 02:37:20 +0530
"Amit Upadhyay" <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> I am facing a weird issue with dream host, day before yesterday my
> django application stopped serving requests, I have not done
> anything, and its been working since about a month, and now it waits
> for minutes before give me 500 interneral server error. Also I get
> lots of core files in my domain folder. Has anyone seen something
> like this happening with their django application hosted on dreamhost?
>

I've been seeing some weirdness with Dreamhost over the past couple of
days.  My site appears to be holding up, though.  Shell access is
painfully slow.  I have some core files in my domain directory as
well.  Stats from my checker show a slower response time than normal
with some of my highest response times happening in the past couple of
days and a bunch of errors - looks like the output from my checker view
is null.  Guess I'll have to trap HTTP headers as well.  Seems like
there is always some mention of Dreamhost on this list and the
TurboGears list - and it's usually not good.  I think each user has a
potential for a widely varying experience.

- jmj

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Amit Upadhyay]

On 2/20/06, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
Nope, never seen it. I suggest to verify .htaccess file and test fcgiwithout Django trying to reproduce the problem. If you didn't modifyDjango (like svn-up it), you may have some problems with disk space(unlikely) or database (unlikely too), but it makes sense to check it too.
The problem is it happens intermittently, only twice with me so far, that too for not more than an hour, in that one hour, whatever I do does not fixes it, while it will fix itself after a while. Its got fixed just now, and I got a core file.
Now my problem is I am serving some _javascript_ that is embedded in the head of tens of blogs and firefox(atleast) will not render anything till before it has either got a 404 for _javascript_s in head or have timed out. Two minute delay will kill my service if it stops my clients blog from loading. 
-- Amit UpadhyayBlog: http://www.rootshell.be/~upadhyay+91-9867-359-701
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django users" group.  To post to this group, send email to django-users@googlegroups.com  To unsubscribe from this group, send email to [EMAIL PROTECTED]  For more options, visit this group at http://groups.google.com/group/django-users  -~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Nathan Clayton]

On Feb 19, 2006, at 1:07 PM, Amit Upadhyay wrote:Hi,I am facing a weird issue with dream host, day before yesterday my django application stopped serving requests, I have not done anything, and its been working since about a month, and now it waits for minutes before give me 500 interneral server error. Also I get lots of core files in my domain folder. Has anyone seen something like this happening with their django application hosted on dreamhost? I'd suggest that you make sure that you've followed the directions on the dreamhost wiki for Django (http://wiki.dreamhost.com/index.php/Django), and then check that you're not getting the same issue that some of the ROR guys have experienced (http://wiki.dreamhost.com/index.php/Ruby_on_Rails#QuickStart_Guide) - check out point 5.Nathan-- This is my haiku.It ends all my messages.It's not very good. 
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django users" group.  To post to this group, send email to django-users@googlegroups.com  To unsubscribe from this group, send email to [EMAIL PROTECTED]  For more options, visit this group at http://groups.google.com/group/django-users  -~--~~~~--~~--~--~---

Re: django problem at dreamhost

[Eugene Lazutkin]

Amit Upadhyay wrote:
> 
> I am facing a weird issue with dream host, day before yesterday my 
> django application stopped serving requests, I have not done anything, 
> and its been working since about a month, and now it waits for minutes 
> before give me 500 interneral server error. Also I get lots of core 
> files in my domain folder. Has anyone seen something like this happening 
> with their django application hosted on dreamhost?

Nope, never seen it. I suggest to verify .htaccess file and test fcgi 
without Django trying to reproduce the problem. If you didn't modify 
Django (like svn-up it), you may have some problems with disk space 
(unlikely) or database (unlikely too), but it makes sense to check it too.

Thanks,

Eugene


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---