X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id CE896D1C9C8 for ; Tue, 5 Aug 2003 12:42:37 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 02365-09 for ; Tue, 5 Aug 2003 09:41:22 -0300 (ADT) Received: from druid.net (druid.net [216.126.72.98]) by svr1.postgresql.org (Postfix) with ESMTP id 10358D1C9D9 for ; Tue, 5 Aug 2003 09:42:27 -0300 (ADT) Received: by druid.net (Postfix, from userid 1000) id 9CE8B1A32; Tue, 5 Aug 2003 08:42:33 -0400 (EDT) From: "D'Arcy J.M. Cain" Reply-To: darcy@PyGreSQL.org Organization: PyGreSQL Development Group To: "Alastair G. Hogge" , pgsql-interfaces@postgresql.org Subject: Re: Seeking PyGreSQL help Date: Tue, 5 Aug 2003 08:42:32 -0400 User-Agent: KMail/1.5.2 References: <200308051816.06256.agh@tpg.com.au> <200308050510.39725.darcy@PyGreSQL.org> <200308052009.47746.agh@tpg.com.au> In-Reply-To: <200308052009.47746.agh@tpg.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200308050842.32937.darcy@PyGreSQL.org> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/22 X-Sequence-Number: 4376 On Tuesday 05 August 2003 06:09, Alastair G. Hogge wrote: > Thanks for help. The problem was in pgsql/data/postgresql.conf. I needed = to > change "#tcpip_socket =3D false" to "tcpip_socket =3D true" > I know am able to access my database from within Python, hwover when I try > the python an cgi script I get an internet server error. Is there more > options I should know about? I assume that you mean "Internal Server Error" or ISE. Whenever your web= =20 server gives an ISE there is something in the error log that tells you what= =20 the problem is. With Python you will get the exact line with the problem.= =20=20 =46rom there it is simpy a matter of debugging your code. If you can't get access to the error logs for whatever reason you can add t= he=20 following line to your Python script to see the error in your browser. import sys sys.stderr =3D sys.stdout You may have to view the source to see the error properly as your browser w= ill=20 try to "format" it for you. --=20 D'Arcy J.M. Cain PyGreSQL Development Group http://www.PyGreSQL.org