On Oct 8, 10:23 pm, Chris Moffitt <[email protected]> wrote:
> Do you see anything in your postgres logs that might point to the issue?
>
> Do other Postgres databases work fine? I might start a very simple django
> project and try to connect. I'm inclined to believe it's not a
> Satchmo-specific problem.
Maybe it is, maybe it isnt. Can't be sure whether its Satchmo or not.
These are the things I can see:
1) works on sqlite+flup+nginx (for many weeks)
2) does not work on PG+flup+nginx
3) *does* work on PG+devserver
It seems that for some reason, some db access is done after the db
connection is closed. This is why the exception happens. As for why it
happens, I'm not quite sure. I use runfcgi with prefork,
maxrequests=1, debug=true and maxchildren=1 for testing. Flup
traceback is either not very interesting or very hard to parse :)
Others have posted the same issue over the months. See another example
here:
http://osdir.com/ml/DjangoUsers/2009-04/msg01647.html
See also Malcolm Tredinnick's comment.
He was suggesting to go through the entire reqeust-response cycle to
figure out where this happens. So far, I'm not sure how I could do
that.
I found some places in satchmo code where livesettings were being
queried for building url patterns (e.g., the product and category base
slugs). I removed them for testing.
Same thing for a couple of the Middlewares provided by satchmo.
Still no luck.
Any pointers ?
Regards
Rajeev J Sebastian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/satchmo-users?hl=en
-~----------~----~----~----~------~----~------~--~---
