Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
Hell, Robert wrote: I just found a bug report for that issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=121423cat= Try asking on current@ - I think there were some patches available some time ago. -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 10. Dezember 2008 18:30 To: Hell, Robert Cc: freebsd-questions@freebsd.org Subject: Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
I just found a bug report for that issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=121423cat= Thanks, Robert -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 10. Dezember 2008 18:30 To: Hell, Robert Cc: freebsd-questions@freebsd.org Subject: Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, 2005-06-14 at 10:05 -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. Is there anything that needs to be set in /etc/inetd.conf or /etc/hosts.allow? I have postgresql_enable=YES in my /etc/rc.conf file, but have not rebooted since I added that. If that's the problem, is there a good way to load that value without rebooting? Is it just an environmental variable? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- see pg_hba.conf in $PGDATA directory. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. Is there anything that needs to be set in /etc/inetd.conf or /etc/hosts.allow? I have postgresql_enable=YES in my /etc/rc.conf file, but have not rebooted since I added that. If that's the problem, is there a good way to load that value without rebooting? Is it just an environmental variable? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- see pg_hba.conf in $PGDATA directory. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I guess I should have specified that I have already added the appropriate entries into pg_hba.conf. I thought that the error message would be enough to indicate it was not an authentication problem, as that generates an error stating there is not an entry in pg_hba for that host. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, 2005-06-14 at 10:05 -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. Is there anything that needs to be set in /etc/inetd.conf or /etc/hosts.allow? I have postgresql_enable=YES in my /etc/rc.conf file, but have not rebooted since I added that. If that's the problem, is there a good way to load that value without rebooting? Is it just an environmental variable? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] also check how database is started. example: pg_ctl start -D $PGDATA -o -i Options -i listen tcp connection. -- Kalashnikov Ilya [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. -- Jonathan Chen [EMAIL PROTECTED] -- When all else fails, RTFM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tuesday 14 June 2005 03:14 pm, Joseph Koenig (jWeb) wrote: On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 Have you checked the firewall settings on both computers to ensure that port 5432 is open? Andrew Gould ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tuesday 14 June 2005 03:14 pm, Joseph Koenig (jWeb) wrote: On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 Have you checked the firewall settings on both computers to ensure that port 5432 is open? Andrew Gould I'm guessing that opening the port is part of what placing postgresql_enable=YES in the rc.conf file does, correct? If so, that's probably the problem as I have not rebooted since adding that. Is there a way to safely force that to run without rebooting? There is a hardware firewall in front of the server that I have ensured is allowing that port through. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Jun 14, 2005, at 4:46 PM, Joseph Koenig (jWeb) wrote: I'm guessing that opening the port is part of what placing postgresql_enable=YES in the rc.conf file does, correct? If so, that's probably the problem as I have not rebooted since adding that. Is there a way to safely force that to run without rebooting? There is a hardware firewall in front of the server that I have ensured is allowing that port through. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] !DSPAM:42af4251253444259514897! Hi Joe, You can confirm whether or not port 5432 is opened by typing netstat -na | grep 5432 on your database server. You should not have to reboot for the port to be opened. When PostgreSQL starts, (either by starting it manually, or then the machine boots) it will open the port. IIt definitely sounds like the firewall could be your problem. I'd try connecting to the database server's port 5432 via telnet from an outside location, so that your packets have to pass thru the firewall in question. Thanks, Ken Ebling Ideal Internet, Inc. 561-963-4501 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tuesday 14 June 2005 15:14, Joseph Koenig (jWeb) wrote: On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 What do you get when you telnet localhost 5432 verses telnet otherserver 5432 ? Try this to rule out any sort of firewall/tunnelling issues If it hangs and you get no prompt, but drops after you type 2 or 3 letters then it means postmaster is doing the negotiation (so then you check the postmaster log). Otherwise you've got gnats in your firewall (or some other kind of bug) to deal with. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP (Solved)
On Jun 14, 2005, at 4:46 PM, Joseph Koenig (jWeb) wrote: I'm guessing that opening the port is part of what placing postgresql_enable=YES in the rc.conf file does, correct? If so, that's probably the problem as I have not rebooted since adding that. Is there a way to safely force that to run without rebooting? There is a hardware firewall in front of the server that I have ensured is allowing that port through. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] !DSPAM:42af4251253444259514897! Hi Joe, You can confirm whether or not port 5432 is opened by typing netstat -na | grep 5432 on your database server. You should not have to reboot for the port to be opened. When PostgreSQL starts, (either by starting it manually, or then the machine boots) it will open the port. IIt definitely sounds like the firewall could be your problem. I'd try connecting to the database server's port 5432 via telnet from an outside location, so that your packets have to pass thru the firewall in question. Thanks, Ken Ebling Ideal Internet, Inc. 561-963-4501 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks to Ken and everyone who sent in recommendations - looks like it was an issue of a network admin who assured me the firewall was open when it really wasn't... Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
On Mon, Oct 27, 2003 at 04:04:28PM -0500, Lowell Gilbert wrote: Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. Allow me to expand on that then... I put the options in /etc/sysctl.conf as follows: kern.ipc.somaxconn=512 kern.ipc.shmmax=268435456 kern.ipc.shmall=65536 kern.ipc.shmmni=128 kern.ipc.semmns=256 When I reboot, sysctl -a | grep kern.ipc.semmns returns kern.ipc.semmns: 60 -- Wayne Pascoe The time for action is passed. Now is the time for senseless bickering. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
On Tue, 28 Oct 2003, Wayne Pascoe wrote: On Mon, Oct 27, 2003 at 04:04:28PM -0500, Lowell Gilbert wrote: Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. Allow me to expand on that then... I put the options in /etc/sysctl.conf as follows: kern.ipc.somaxconn=512 kern.ipc.shmmax=268435456 kern.ipc.shmall=65536 kern.ipc.shmmni=128 kern.ipc.semmns=256 When I reboot, sysctl -a | grep kern.ipc.semmns returns kern.ipc.semmns: 60 I believe -current now has code to pull values for these out of the kernel environment; that's missing in -stable (IIRC; not checked, but I have a vague recollection of trying to figure out how the hell the values were supposed to get into the sysctl value until I looked at the -current tree). -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ I like oranges more than apples!? - that's like comparing apples and oranges! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
Wayne Pascoe [EMAIL PROTECTED] writes: On Mon, Oct 27, 2003 at 04:04:28PM -0500, Lowell Gilbert wrote: Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. Allow me to expand on that then... I put the options in /etc/sysctl.conf as follows: kern.ipc.somaxconn=512 kern.ipc.shmmax=268435456 kern.ipc.shmall=65536 kern.ipc.shmmni=128 kern.ipc.semmns=256 When I reboot, sysctl -a | grep kern.ipc.semmns returns kern.ipc.semmns: 60 Hmm. I just checked, and it's working fine for me under yesterday's -STABLE. Are you getting any error messages at boot when sysctl.conf is evaluated? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
I'm trying to configure and tune postgresql on FreeBSD 4.9. We want to allow at least 128 concurrent connections but preferably 256. My memory is that there was some extensive discussion of this on the freebsd-databases mailing list, and a search of the archives at lists.freebsd.org should turn them up. Mike Squires ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
I haven't used that software since it was called postgres, but I'll wade in anyway... Wayne Pascoe [EMAIL PROTECTED] writes: Hi all, I'm trying to configure and tune postgresql on FreeBSD 4.9. We want to allow at least 128 concurrent connections but preferably 256. Looking at the documentation, we should be okay if we set the following in our kernel to achieve this: kern.ipc.somaxconn = 512 kern.ipc.shmall = 65536 kern.ipc.shmmni = 128 kern.ipc.semmni = 8 kern.ipc.semmns = 256 Now, I have three questions... 1. Why do we have to set these in the kernel ? You don't. Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. 2. Is there a recommended list of settings that we should use in our kernel to allow 128 connections and 256 connections ? A single recommendation, no. It's been discussed. You started with tuning(7), I assume. and lastly, 3. What is the impact on the rest of the system likely to be by setting aside this memory as shared memory ? Is it then no longer available to other applications like Apache and Exim ? Are there any other performance issues that we should be aware of ? Yes, the memory is pulled out of the general pool, and no, I don't think there will be any other noticeable effects at those settings. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
