On 6/25/07, Francis Lavoie <[EMAIL PROTECTED]> wrote: > > I have a problem with my 400.html when I put the site in production > (another server). > > Both desktop and server are running ubuntu 7.04. > The Desktop use the builtin webserver and the server is running apache with > mod_python > > On my localhost with debug = True and debug = False, everything is working > as expected. But when I sync the code with the production web server and I > corrected the static path, the server cannot handle 400 error and throw a > database error instead. (I don't use the database, I just have it configured > for future use with the default django services) > > The apache user has read/write permission on the database file. > > here is the error : > > [ ugly traceback snipped] > > File > "/var/lib/python-support/python2.5/django/db/backends/sqlite3/base.py", > line 45, in cursor > detect_types=Database.PARSE_DECLTYPES | Database.PARSE_COLNAMES) > > OperationalError: unable to open database file >
Could be related to this: http://code.djangoproject.com/wiki/NewbieMistakes#DjangosaysUnabletoOpenDatabaseFilewhenusingSQLite3 Regards, -- Ramiro Morales --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
