Weird upload error (image file is truncated)
Hi Since friday I get this error for EVERY upload on a page. I thought it was my latest change so reverted, but error stayed. This is, the least to be said, irritating: "IOError: image file is truncated (10 bytes not processed)" The miracle continues: when I Reload my apache, the file is actually uploaded. However the custom binding of foreign keys (as you'll be able to see in my view) won't happen since the script crashes before that binding. Very stupid. Also after trying that upload members can't visit that page again (since we 'try' to display that image there again). I hope (really) someone can help me on this one since I try everything already :(. View: http://dpaste.com/81050/ template: http://dpaste.com/81049/ traceback: http://dpaste.com/81051/ Locally on windows I also had the error, I switched to ubuntu saterday, checked out and here everything worked fine (server is ubuntu feisty, laptop hardy). grtz --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Segmentation fault (postgresql - psycopg2)
Just to mention: it's appearantly a psycopg2 error. with psycopg1 everything worked fine. On Aug 25, 10:18 am, kire <[EMAIL PROTECTED]> wrote: > My site works fine locally mysql, sqlite and postgresql. On the server > it worked fine om mysql - myisam (well, as long you can speak about > fine for that database). I'm trying to convert to postgresql, > everything is configured correct and when i execute 'python manage.py > syncdb --noinput' I just nicely receive Segmentation fault. > > Since I have 3 django installations (don't ask, we're converting other > apps right now) I thought it could be manage.py using an outdated > django distribution, so I ran 'python manage.py --version', which > gives me nicely '1.0-beta_1-SVN-8534'. So, no problem there (also > tried with older revisions to make sure). > > I have to say: the database is 'remote' (2 different virtual machines, > one for database, one for apache). But this works since our phppgadmin > is doing it's job. > > Any ideas? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Segmentation fault (postgresql - psycopg2)
My site works fine locally mysql, sqlite and postgresql. On the server it worked fine om mysql - myisam (well, as long you can speak about fine for that database). I'm trying to convert to postgresql, everything is configured correct and when i execute 'python manage.py syncdb --noinput' I just nicely receive Segmentation fault. Since I have 3 django installations (don't ask, we're converting other apps right now) I thought it could be manage.py using an outdated django distribution, so I ran 'python manage.py --version', which gives me nicely '1.0-beta_1-SVN-8534'. So, no problem there (also tried with older revisions to make sure). I have to say: the database is 'remote' (2 different virtual machines, one for database, one for apache). But this works since our phppgadmin is doing it's job. Any ideas? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
