Thanks a lot Jamie. Your stab in the dark is very useful indeed.
The site is in fact hosted at Webfaction too, and it's only there that
I get the error. The model is quite simple - it only has Charfields,
URLFields and Emailfields. There is no inheritance, but there is a
OneToOneField relationship with another model:
class Organisation(models.Model):
....
class OrganisationExtension(models.Model):
organisation = models.OneToOneField(Organisation,
related_name="extension")
latitude = models.CharField(max_length=50, blank=True,
null=False)
longitude = models.CharField(max_length=50, blank=True,
null=False)
There is no custom save method in the models or in the admin options.
The only thing I think is worth mentioning is that
OrganisationExtension model is put in an inline:
class OrganisationExtensionInline(admin.StackedInline):
model = OrganisationExtension
max_num = 1
class OrganisationAdmin(admin.ModelAdmin):
inlines = [OrganisationExtensionInline]
This looks very similar to the issue that you've had. I'm really
unsure what's going on and how to debug this. I'll keep investigating,
but any tips would be very welcome.
Thanks again,
Julien
On Jul 25, 5:56 pm, jamiecURLe <jamie.cu...@designcc.co.uk> wrote:
> Hello Julien,
>
> Without seeing the model and knowing who your hosting provider is and
> what web servers your using to serve up your django app it is
> difficult to say for sure but I have a hunch.
>
> It could be that the save action for that one organisation is creating
> form of memory intensive situation ( possible infinite loop ), this
> could eat away at available memory until the process was killed. In
> this situation the upstream web server would never get it's response
> from the downstream proxy because a process on which it relied had
> been killed.
>
> This would give you the 502 error.
>
> I have encountered this with webfaction before. It was my issue, I had
> a model that had a parent > child relationship, which whilst not being
> totally new to recursion, had failed to spot a real newbie error.
>
> In terms of debugging this one, I'm no expert but I'd start by looking
> at all relationships on the models and scrutinising them until
> something came to light.
>
> I'd like to say I'd then use this exact situation as a test case, but
> being new to testing myself I really can't offer any real assistance
> in this one.
>
> Hope this stab is dark helps.
>
> Cheers,
>
> Jamie.
>
> On Jul 24, 1:08 pm, Julien Phalip <jpha...@gmail.com> wrote:
>
> > Hi,
>
> > I've got a really strange error on one of my sites. There is an
> > Organisation model which has a dozen of fields and 1,300 rows.
>
> > Saving organisation details in the admin usually works fine except for
> > one organisation. When I click 'Save', the page loads for ever and
> > then it fails with a 502 Proxy Error. I can edit the corresponding row
> > in Phpmyadmin without any problem so the database doesn't seem to be
> > damaged. Saving works with all other organisations I've tested.
>
> > It is using Django revision 9975.
>
> > Would you have any tips for debugging this?
>
> > Thanks a lot!
>
> > Regards,
>
> > Julien
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
