Re: [GENERAL] Unable to connect to Postgresql

2017-04-11 Thread John Iliffe
On Monday 10 April 2017 19:37:43 Adrian Klaver wrote: > On 04/10/2017 01:23 PM, John Iliffe wrote: > > On Monday 10 April 2017 11:53:35 Daniel Verite wrote: > >>John Iliffe wrote: > >>> So, the problem is resolved, although I have no idea why it was > >>> necessary. > >> > >> The key seems to

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Adrian Klaver
On 04/10/2017 01:23 PM, John Iliffe wrote: On Monday 10 April 2017 11:53:35 Daniel Verite wrote: John Iliffe wrote: So, the problem is resolved, although I have no idea why it was necessary. The key seems to be the PrivateTmp=true in the systemd service. Apache is not chrooted as demo

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Adrian Klaver
On 04/10/2017 01:23 PM, John Iliffe wrote: On Monday 10 April 2017 11:53:35 Daniel Verite wrote: John Iliffe wrote: So, the problem is resolved, although I have no idea why it was necessary. The key seems to be the PrivateTmp=true in the systemd service. Apache is not chrooted as demo

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread John Iliffe
Thanks for the idea Rick. It hadn't occurred to me; might have at about the 200th page :-( John = On Monday 10 April 2017 16:46:14 Rick Widmer wrote: > On 4/10/2017 2:23 PM, John Iliffe wrote: > > On Monday 10 April 2017 11:53:35 Daniel Verite wrote: > >>J

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread rob stone
Hello John, On Mon, 2017-04-10 at 16:23 -0400, John Iliffe wrote: > On Monday 10 April 2017 11:53:35 Daniel Verite wrote: > >   John Iliffe wrote: > > > So, the problem is resolved, although I have no idea why it was > > > necessary. > >  > Good to hear. > >  > > Yes, I will do that, but t

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Daniel Verite
John Iliffe wrote: > Yes, I will do that, but there are several hundred PHP web page scripts to > be updated. Presumably if one script opens two different databases then > both of the pg_connect() instances will need to be updated. If you have many calls to pg_connect() without a host

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Adrian Klaver
On 04/10/2017 01:23 PM, John Iliffe wrote: On Monday 10 April 2017 11:53:35 Daniel Verite wrote: John Iliffe wrote: So, the problem is resolved, although I have no idea why it was necessary. The key seems to be the PrivateTmp=true in the systemd service. Apache is not chrooted as demo

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Rick Widmer
On 4/10/2017 2:23 PM, John Iliffe wrote: On Monday 10 April 2017 11:53:35 Daniel Verite wrote: John Iliffe wrote: Given that you set two directories: /tmp and /var/pgsql, I would think you can let the other apps use /tmp as before and have only Apache use /var/pgsql ? Yes, I will do

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread John Iliffe
On Monday 10 April 2017 11:53:35 Daniel Verite wrote: > John Iliffe wrote: > > So, the problem is resolved, although I have no idea why it was > > necessary. > > The key seems to be the PrivateTmp=true in the systemd service. > Apache is not chrooted as demonstrated upthread, but that > sett

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Daniel Verite
John Iliffe wrote: > So, the problem is resolved, although I have no idea why it was necessary. The key seems to be the PrivateTmp=true in the systemd service. Apache is not chrooted as demonstrated upthread, but that setting alone makes the normal, system-wide /tmp inaccessible to its

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread John Iliffe
On Monday 10 April 2017 09:46:54 Daniel Verite wrote: > John Iliffe wrote: > > Based on the reference that Joe sent earlier, I do have a second > > domain socket on /var/pgsql but the problem is how do I get PHP to > > look there? > > pg_connect("host=/var/pgsql [...other parameters...]")

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread John Iliffe
On Monday 10 April 2017 09:46:54 Daniel Verite wrote: > John Iliffe wrote: > > Based on the reference that Joe sent earlier, I do have a second > > domain socket on /var/pgsql but the problem is how do I get PHP to > > look there? > > pg_connect("host=/var/pgsql [...other parameters...]")

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread John Iliffe
On Sunday 09 April 2017 23:21:58 Adrian Klaver wrote: > On 04/09/2017 05:30 PM, John Iliffe wrote: > > On Sunday 09 April 2017 20:01:32 Adrian Klaver wrote: > >> So the issue is in PHP via Apache using the socket, because if I > >> remember right you used localhost in the Apache/PHP combination and

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread John Iliffe
On Sunday 09 April 2017 22:07:12 rob stone wrote: > On Sun, 2017-04-09 at 20:09 -0400, John Iliffe wrote: > > > > > > > > > You have Apache, PHP, and Postgres all running on your LAN at > > > 192.168.1.6. > > > > > > > > > > > > > > > You are on 192.168.1.10. > > > > > > > > > > > > Your NOT do

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Daniel Verite
John Iliffe wrote: > Based on the reference that Joe sent earlier, I do have a second domain > socket on /var/pgsql but the problem is how do I get PHP to look there? pg_connect("host=/var/pgsql [...other parameters...]") The fact that the value for host starts with a slash indicate

Re: [GENERAL] Unable to connect to Postgresql

2017-04-10 Thread Daniel Verite
John Iliffe wrote: > > > > > Basically, nothing. > > If I include it in an Apache script exactly as suggested, then the script > puts out a blank screen, no error messages. So from the point of view of the Apache process, that file does not exist. That's consistent with the error y

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Adrian Klaver
On 04/09/2017 05:30 PM, John Iliffe wrote: On Sunday 09 April 2017 20:01:32 Adrian Klaver wrote: So the issue is in PHP via Apache using the socket, because if I remember right you used localhost in the Apache/PHP combination and it worked, correct? Yes. I think there is some confusion here

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread rob stone
On Sun, 2017-04-09 at 20:09 -0400, John Iliffe wrote: > > >  > > You have Apache, PHP, and Postgres all running on your LAN at > > 192.168.1.6. > >  > >  > > You are on 192.168.1.10. > >  > > Your NOT doing "php -f testfcgi.php", so how does Apache "know" to > run > > that script? > > testfcgi.

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 20:07:01 Adrian Klaver wrote: > On 04/09/2017 03:27 PM, rob stone wrote: > > Hello John, > > > > Just saw this message. > > > >> Still set to the default: > >> > >> #listen_addresses = 'localhost' # what IP address(es) to > >> listen on; > >> > >>

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 20:01:32 Adrian Klaver wrote: > On 04/09/2017 02:35 PM, John Iliffe wrote: > > On Sunday 09 April 2017 17:02:47 Adrian Klaver wrote: > >> On 04/09/2017 02:00 PM, John Iliffe wrote: > >>> On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote: > Remember host != local > >>

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 18:27:49 rob stone wrote: Hi Rob: Thanks for chiming in. > Hello John, > > Just saw this message. > > > Still set to the default: > > > > #listen_addresses = 'localhost' # what IP address(es) to > > listen on; > > # comma-

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Adrian Klaver
On 04/09/2017 03:27 PM, rob stone wrote: Hello John, Just saw this message. Still set to the default: #listen_addresses = 'localhost' # what IP address(es) to listen on; # comma-separated list of addresses;

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Adrian Klaver
On 04/09/2017 02:35 PM, John Iliffe wrote: On Sunday 09 April 2017 17:02:47 Adrian Klaver wrote: On 04/09/2017 02:00 PM, John Iliffe wrote: On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote: Remember host != local host is for IP connections local is for socket connections Yes, I had for

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 17:39:30 rob stone wrote: > Hello John, > > > > > > > > > > > PHP and Postgresql are both running on same box. It does have > > > > two > > > > > > interfaces, 192.168.1.6 and 192.168.1.7, and the test programme > > > > is > > > > > > available on either. The referen

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread rob stone
Hello John, Just saw this message. > > Still set to the default: > > #listen_addresses = 'localhost' # what IP address(es) to > listen on; >     # comma-separated list of  > addresses; >     # defaults to 'localhos

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread rob stone
Hello John, > >  > > > PHP and Postgresql are both running on same box.  It does have > two > > > interfaces, 192.168.1.6 and 192.168.1.7, and the test programme > is > > > available on either.  The reference to 192.168.1.10 is the client > > > machine, in this case my workstation, which is 192.1

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 17:02:47 Adrian Klaver wrote: > On 04/09/2017 02:00 PM, John Iliffe wrote: > > On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote: > >> Remember host != local > >> > >> host is for IP connections > >> > >> local is for socket connections > > > > Yes, I had forgotten tha

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Adrian Klaver
On 04/09/2017 02:00 PM, John Iliffe wrote: On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote: Remember host != local host is for IP connections local is for socket connections Yes, I had forgotten that for the moment. I have the following line in the 'local' section of the pg_hba.conf

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 15:38:10 Adrian Klaver wrote: > On 04/09/2017 12:37 PM, John Iliffe wrote: > > On Sunday 09 April 2017 14:34:01 Joe Conway wrote: > >> On 04/09/2017 11:33 AM, John Iliffe wrote: > >>> On Saturday 08 April 2017 18:10:35 Joe Conway wrote: > On 04/08/2017 01:23 PM, John Il

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 15:41:12 Joe Conway wrote: > On 04/09/2017 12:37 PM, John Iliffe wrote: > >> > Thanks Joe. I Changed the pg_connect line in the script to: > >> > $db_handle = pg_connect('dbname=yrarc host=192.168.1.6 port=5432 > >> > > >> > user= password=xx'); > > > > If I may

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Joe Conway
On 04/09/2017 12:37 PM, John Iliffe wrote: >> > Thanks Joe. I Changed the pg_connect line in the script to: >> > $db_handle = pg_connect('dbname=yrarc host=192.168.1.6 port=5432 >> > user= password=xx'); > If I may be permitted a rant at this point, the Fedora documentation is > almost

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Adrian Klaver
On 04/09/2017 12:37 PM, John Iliffe wrote: On Sunday 09 April 2017 14:34:01 Joe Conway wrote: On 04/09/2017 11:33 AM, John Iliffe wrote: On Saturday 08 April 2017 18:10:35 Joe Conway wrote: On 04/08/2017 01:23 PM, John Iliffe wrote: On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: So

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 15:05:18 Adrian Klaver wrote: > On 04/09/2017 11:33 AM, John Iliffe wrote: > > On Saturday 08 April 2017 18:10:35 Joe Conway wrote: > >> On 04/08/2017 01:23 PM, John Iliffe wrote: > >>> On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: > So what if you change the

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Sunday 09 April 2017 14:34:01 Joe Conway wrote: > On 04/09/2017 11:33 AM, John Iliffe wrote: > > On Saturday 08 April 2017 18:10:35 Joe Conway wrote: > >> On 04/08/2017 01:23 PM, John Iliffe wrote: > >> > On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: > >> >> So what if you change the c

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Saturday 08 April 2017 11:20:29 Joe Conway wrote: > On 04/08/2017 06:31 AM, John Iliffe wrote: > > On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote: > >> On 04/07/2017 07:45 PM, Joe Conway wrote: > >> > On 04/07/2017 05:35 PM, Adrian Klaver wrote: > >> >> On 04/07/2017 05:03 PM, John Iliff

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Adrian Klaver
On 04/09/2017 11:33 AM, John Iliffe wrote: On Saturday 08 April 2017 18:10:35 Joe Conway wrote: On 04/08/2017 01:23 PM, John Iliffe wrote: On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: So what if you change the connection to use -h localhost? Can you please expand on that request?

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread Joe Conway
On 04/09/2017 11:33 AM, John Iliffe wrote: > On Saturday 08 April 2017 18:10:35 Joe Conway wrote: >> On 04/08/2017 01:23 PM, John Iliffe wrote: >> > On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: >> >> So what if you change the connection to use -h localhost? >> > >> > Can you please expa

Re: [GENERAL] Unable to connect to Postgresql

2017-04-09 Thread John Iliffe
On Saturday 08 April 2017 18:10:35 Joe Conway wrote: > On 04/08/2017 01:23 PM, John Iliffe wrote: > > On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: > >> So what if you change the connection to use -h localhost? > > > > Can you please expand on that request? I'm not sure where you want m

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread Joe Conway
On 04/08/2017 01:23 PM, John Iliffe wrote: > On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: >> So what if you change the connection to use -h localhost? > > Can you please expand on that request? I'm not sure where you want me to > put that directive. I'm using the mod_php module in Ap

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread John Iliffe
On Saturday 08 April 2017 09:38:07 Adrian Klaver wrote: > On 04/08/2017 06:26 AM, John Iliffe wrote: > > On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote: > >> On 04/07/2017 07:45 PM, Joe Conway wrote: > >>> On 04/07/2017 05:35 PM, Adrian Klaver wrote: > On 04/07/2017 05:03 PM, John Ilif

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread John Iliffe
On Saturday 08 April 2017 09:20:46 Daniel Verite wrote: > John Iliffe wrote: > > The proper socket does exist: > > > > - > > ls -al /tmp | grep PGSQL > > srwxrwxrwx. 1 postgres postgres0 Apr 7 16:53 .s.PGSQL.5432 > > -rw---. 1 postgres postgres

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread Joe Conway
On 04/08/2017 06:31 AM, John Iliffe wrote: > On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote: >> On 04/07/2017 07:45 PM, Joe Conway wrote: >> > On 04/07/2017 05:35 PM, Adrian Klaver wrote: >> >> On 04/07/2017 05:03 PM, John Iliffe wrote: >> > Running on Fedora 25 with SELinux in PERMISSI

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread Adrian Klaver
On 04/08/2017 06:26 AM, John Iliffe wrote: On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote: On 04/07/2017 07:45 PM, Joe Conway wrote: On 04/07/2017 05:35 PM, Adrian Klaver wrote: On 04/07/2017 05:03 PM, John Iliffe wrote: Running on Fedora 25 with SELinux in PERMISSIVE mode. The audit

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread John Iliffe
On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote: > On 04/07/2017 07:45 PM, Joe Conway wrote: > > On 04/07/2017 05:35 PM, Adrian Klaver wrote: > >> On 04/07/2017 05:03 PM, John Iliffe wrote: > > Running on Fedora 25 with SELinux in PERMISSIVE mode. The audit > > log shows no hits on

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread Daniel Verite
John Iliffe wrote: > The proper socket does exist: > > - > ls -al /tmp | grep PGSQL > srwxrwxrwx. 1 postgres postgres0 Apr 7 16:53 .s.PGSQL.5432 > -rw---. 1 postgres postgres 49 Apr 7 16:53 .s.PGSQL.5432.lock Maybe the httpd service live

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread John Iliffe
On Saturday 08 April 2017 00:10:14 Adrian Klaver wrote: > On 04/07/2017 07:45 PM, Joe Conway wrote: > > On 04/07/2017 05:35 PM, Adrian Klaver wrote: > >> On 04/07/2017 05:03 PM, John Iliffe wrote: > > Running on Fedora 25 with SELinux in PERMISSIVE mode. The audit > > log shows no hits on

Re: [GENERAL] Unable to connect to Postgresql

2017-04-08 Thread John Iliffe
On Friday 07 April 2017 22:45:16 Joe Conway wrote: > On 04/07/2017 05:35 PM, Adrian Klaver wrote: > > On 04/07/2017 05:03 PM, John Iliffe wrote: > Running on Fedora 25 with SELinux in PERMISSIVE mode. The audit > log shows no hits on Postgresql. > >> > >> My going in position was/still

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread Adrian Klaver
On 04/07/2017 07:45 PM, Joe Conway wrote: On 04/07/2017 05:35 PM, Adrian Klaver wrote: On 04/07/2017 05:03 PM, John Iliffe wrote: Running on Fedora 25 with SELinux in PERMISSIVE mode. The audit log shows no hits on Postgresql. My going in position was/still is, that this is a SELinux secu

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread Joe Conway
On 04/07/2017 05:35 PM, Adrian Klaver wrote: > On 04/07/2017 05:03 PM, John Iliffe wrote: Running on Fedora 25 with SELinux in PERMISSIVE mode. The audit log shows no hits on Postgresql. >> My going in position was/still is, that this is a SELinux security >> problem >> but I am findin

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread John Iliffe
On Friday 07 April 2017 20:39:55 Adrian Klaver wrote: > On 04/07/2017 05:10 PM, John Iliffe wrote: > Actually Ccing list this time > > > On Friday 07 April 2017 19:51:57 you wrote: > >> On 04/07/2017 04:57 PM, John Iliffe wrote: > >>> Hi Adrian: > > Well, it ain't that simple! I am trying to take

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread John Iliffe
On Friday 07 April 2017 20:35:40 Adrian Klaver wrote: > On 04/07/2017 05:03 PM, John Iliffe wrote: > > Please reply to list also Yes, sorry about that. > Ccing list. > > > On Friday 07 April 2017 18:58:15 you wrote: > >> On 04/07/2017 02:38 PM, John Iliffe wrote: > >>> When I attempt to run any

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread Adrian Klaver
On 04/07/2017 05:10 PM, John Iliffe wrote: Actually Ccing list this time On Friday 07 April 2017 19:51:57 you wrote: On 04/07/2017 04:57 PM, John Iliffe wrote: Hi Adrian: Well, it ain't that simple! I am trying to take advantage of having a new server that doesn't have to be in productio

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread Adrian Klaver
On 04/07/2017 05:03 PM, John Iliffe wrote: Please reply to list also Ccing list. On Friday 07 April 2017 18:58:15 you wrote: On 04/07/2017 02:38 PM, John Iliffe wrote: When I attempt to run any web application php cannot open a database because of failure to connect. (Please disregard the pro

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread Adrian Klaver
On 04/07/2017 04:57 PM, John Iliffe wrote: Hi Adrian: Not the same problem. Last time I couldn't get postgresql running at all. This time it is running and I can't connect to it. I did check for something else holding the socket, but as far as I can see nothing else has it. So when was the

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread John Iliffe
Hi Adrian: Not the same problem. Last time I couldn't get postgresql running at all. This time it is running and I can't connect to it. I did check for something else holding the socket, but as far as I can see nothing else has it. Regards, John === On Frid

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread Adrian Klaver
On 04/07/2017 02:38 PM, John Iliffe wrote: When I attempt to run any web application php cannot open a database because of failure to connect. (Please disregard the programme name, it is running in mod_php, not as an fcgi module). The (php) message is: -- [Fri Apr 07 17

Re: [GENERAL] Unable to connect to Postgresql

2017-04-07 Thread Adrian Klaver
On 04/07/2017 02:38 PM, John Iliffe wrote: When I attempt to run any web application php cannot open a database because of failure to connect. (Please disregard the programme name, it is running in mod_php, not as an fcgi module). The (php) message is: -- [Fri Apr 07 17

[GENERAL] Unable to connect to Postgresql

2017-04-07 Thread John Iliffe
When I attempt to run any web application php cannot open a database because of failure to connect. (Please disregard the programme name, it is running in mod_php, not as an fcgi module). The (php) message is: -- [Fri Apr 07 17:03:28.597101 2017] [php7:warn] [pid 1797:t

Re: [GENERAL] Unable to connect to PostgreSQL server : Could not get socket error status

2011-12-22 Thread John R Pierce
On 12/22/11 1:31 AM, Shankar Palaniappan wrote: I am getting the following error when I try to connect from PHP with PostgreSQL server. Operating System is HP-UX and I was able to connect through PostgreSQL server from psql, what postgres connection parameters are you passing to the php connec

[GENERAL] Unable to connect to PostgreSQL server : Could not get socket error status

2011-12-22 Thread Shankar Palaniappan
Hi, Unable to connect to PostgreSQL server : Could not get socket error status: No such file or directory in index.php on line 5 Can any one help me on this ? I am getting the following error when I try to connect from PHP with PostgreSQL server. Operating System is HP-UX and I was able to conne

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-15 Thread John Coulthard
onnection. Thanks for the help. From: "John Coulthard" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Unable to connect to PostgreSQL server via PHP Date: Mon, 13 Aug 2007 15:34:19 + From: Tom Lane <[EMAIL PROTECTE

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-13 Thread John Coulthard
From: Tom Lane <[EMAIL PROTECTED]> To: "John Coulthard" <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Unable to connect to PostgreSQL server via PHP Date: Mon, 13 Aug 2007 10:09:15 -0400 "John Coulthard" <[EMAIL PROTECTE

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-13 Thread Tom Lane
"John Coulthard" <[EMAIL PROTECTED]> writes: > That's not my problem though this is "could not connect to server: > Permission denied" If it's denying permission I must have the permissions > set wrong but where to I start looking for them? "Permission denied" is a pretty strange error for a TC

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-13 Thread John Coulthard
From: "Lim Berger" <[EMAIL PROTECTED]> To: "John Coulthard" <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Unable to connect to PostgreSQL server via PHP Date: Mon, 13 Aug 2007 18:51:37 +0800 On 8/13/07, John Coulthard <[EMAIL P

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-13 Thread John Coulthard
CTED]> To: John Coulthard <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Unable to connect to PostgreSQL server via PHP Date: Fri, 10 Aug 2007 22:50:47 -0500 El jue, 09-08-2007 a las 14:51 +, John Coulthard escribió: > Hi > > I'm trying to set up a

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-13 Thread Lim Berger
On 8/13/07, John Coulthard <[EMAIL PROTECTED]> wrote: > The part of the php code for the connection is > > > $dbconn=pg_connect( "dbname=lumbribase host=localhost port=5432 > user=postgres password=$PG_PASS" ); > if ( ! $dbconn ) { > echo "Error connecting to the database ! " ; > printf("%s

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-13 Thread John Coulthard
CTED]> To: John Coulthard <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Unable to connect to PostgreSQL server via PHP Date: Fri, 10 Aug 2007 22:50:47 -0500 El jue, 09-08-2007 a las 14:51 +, John Coulthard escribió: > Hi > > I'm trying to set up a

Re: [GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-10 Thread Julio Cesar Sánchez González
El jue, 09-08-2007 a las 14:51 +, John Coulthard escribió: > Hi > > I'm trying to set up a new webserver running php and pgsql. PHP was > connecting to postgres but I needed to install the php-gd module and now I > get the error... > > "PHP Warning: pg_connect() [ href='function.pg-connec

[GENERAL] Unable to connect to PostgreSQL server via PHP

2007-08-09 Thread John Coulthard
Hi I'm trying to set up a new webserver running php and pgsql. PHP was connecting to postgres but I needed to install the php-gd module and now I get the error... "PHP Warning: pg_connect() [href='function.pg-connect'>function.pg-connect]: Unable to connect to PostgreSQL server: could not

Re: [GENERAL] Unable to connect to PostgreSQL server

2006-04-20 Thread Shane Ambler
You may also want to look into your php.ini settings. pgsql.max_persistent pgsql.max_links pgsql.auto_reset_persistent and PGSQL_CONNECT_FORCE_NEW are options you would want to check into. > Look in data/postgres.conf > > You will find a line there such as max_connections = 50 you will also nee

Re: [GENERAL] Unable to connect to PostgreSQL server

2006-04-20 Thread Shane Ambler
Look in data/postgres.conf You will find a line there such as max_connections = 50 you will also need to check that shared_buffers is at least twice the max_connections. You can also start Postmaster with -B nBuffers -N maxbackends On 20/4/2006 17:41, "Martin Kuria" <[EMAIL PROTECTED]> wrote:

Re: [GENERAL] Unable to connect to PostgreSQL server

2006-04-20 Thread Harald Armin Massa
Martin,please check out the server configuration documentation athttp://www.postgresql.org/docs/8.1/interactive/runtime-config-connection.html#RUNTIME-CONFIG-CONNECTION-SETTINGS your configuration file of choice is postgresql.conf within the data directory.(btw: because the default is rather big, i

[GENERAL] Unable to connect to PostgreSQL server

2006-04-20 Thread Martin Kuria
hi, I have a problem with my postgresql database it always gives me an error: Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: FATAL: sorry, too many clients already in ~/includes/DbConnector.php on line 27 Please advice how I can manage my database to han