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.

-Chris

On Thu, Oct 8, 2009 at 11:20 AM, rajeev j sebastian <
[email protected]> wrote:

>
>
>
> On Oct 7, 7:59 pm, Chris Moffitt <[email protected]> wrote:
> > What database backend are you using? I've seen these sorts of things when
> > I'm using sqlite and don't have appropriate permissions on the db file.
>
> Hi,
>
> I'm having the same problem as Michail. I'm using PG backend.
> Actually, I was using sqlite for weeks on the same setup and it was
> working fine. This afternoon, I switched to PG and this problem
> started occurring.
>
> Regards
> Rajeev J Sebastian
>
>
> > On Tue, Oct 6, 2009 at 11:30 PM, Michail <[email protected]>
> wrote:
> >
> > > Hello. I try to start my Satchmo shop server in prefork mode on nginx
> > > +fcgi. nginx.conf:
> > > server {
> > >        listen 0.0.0.0:80;
> > >        server_name example.testwww.example.test;
> >
> > >        error_log /var/log/customers/httpd/example_test/example.test/
> > > error.log;
> > >        access_log /var/log/customers/httpd/example_test/example.test/
> > > access.log main;
> >
> > >        #proxy_buffering on;
> > >        location / {
> > >              root   html;
> > >              index  index.html index.htm;
> > >              fastcgi_pass 127.0.0.1:8882;
> > >              fastcgi_param PATH_INFO $fastcgi_script_name;
> > >              fastcgi_param REQUEST_METHOD $request_method;
> > >              fastcgi_param QUERY_STRING $query_string;
> > >              fastcgi_param CONTENT_TYPE $content_type;
> > >              fastcgi_param CONTENT_LENGTH $content_length;
> > >              fastcgi_param REMOTE_ADDR $remote_addr;
> > >              fastcgi_param REMOTE_PORT $remote_port;
> > >              fastcgi_param SERVER_PORT $server_port;
> > >              fastcgi_param SERVER_NAME $server_name;
> > >              fastcgi_param SERVER_PROTOCOL $server_protocol;
> > >              fastcgi_pass_header Authorization;
> > >              fastcgi_intercept_errors off;
> > >        }
> > > }
> >
> > > satchmo start as:
> > > ./manage.py runfcgi method=prefork daemonize=false host=127.0.0.1
> > > port=8882
> >
> > > after run I can see in nginx log:
> > > File "/var/www/vhosts/server_name/python/lib64/python2.5/site-packages/
> > > flup/server/fcgi_base.py", line 558, in run
> > >    protocolStatus, appStatus = self.server.handler(self)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/flup/server/fcgi_base.py", line 1112, in handler
> > >    result = self.application(environ, start_response)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/core/handlers/wsgi.py", line 239, in __call__
> > >    response = self.get_response(request)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/core/handlers/base.py", line 67, in get_response
> > >    response = middleware_method(request)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/middleware/locale.py", line 16, in process_request
> > >    language = translation.get_language_from_request(request)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/utils/translation/__init__.py", line 97, in
> > > get_language_from_request
> > >    return real_get_language_from_request(request)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/utils/translation/trans_real.py", line 353, in
> > > get_language_from_request
> > >    lang_code = request.session.get('django_language', None)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/contrib/sessions/backends/base.py", line 63, in get
> > >    return self._session.get(key, default)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/contrib/sessions/backends/base.py", line 172, in
> > > _get_session
> > >    self._session_cache = self.load()
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/contrib/sessions/backends/db.py", line 16, in load
> > >    expire_date__gt=datetime.datetime.now()
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/db/models/manager.py", line 93, in get
> > >    return self.get_query_set().get(*args, **kwargs)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/db/models/query.py", line 304, in get
> > >    num = len(clone)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/db/models/query.py", line 160, in __len__
> > >    self._result_cache = list(self.iterator())
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/db/models/query.py", line 275, in iterator
> > >    for row in self.query.results_iter():
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/db/models/sql/query.py", line 206, in results_iter
> > >    for rows in self.execute_sql(MULTI):
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/db/models/sql/query.py", line 1734, in execute_sql
> > >    cursor.execute(sql, params)
> > >  File "/var/www/vhosts/server_name/python/lib64/python2.5/site-
> > > packages/django/db/backends/util.py", line 19, in execute
> > >    return self.cursor.execute(sql, params)
> > > OperationalError: server closed the connection unexpectedly
> > >        This probably means the server terminated abnormally
> > >        before or while processing the request.
> >
> > > when I try to start "Hello would" project - all works properly.
> >
> > > How I can correct it? There can be I have forgotten something to
> > > install or to set up any customization? Please help me...
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to