Just a final note:
Changing shmall did fix the problem. Thanks to everyone for the help.
the final working settings i used are:
kern.sysv.shmmax=4194304
kern.sysv.shmmin=1
kern.sysv.shmmni=32
kern.sysv.shmseg=8
kern.sysv.shmall=4194304
I'm wondering how I managed to get it to work before, witho
On May 7, 2007, at 9:11 AM, Tom Lane wrote:
I believe BTW that you
need to do "sudo ipcs -a" to be sure of seeing everything; otherwise
OS X's ipcs silently doesn't tell you about segments your userid
doesn't
have access to.
Actually, it seems that you don't get anything back when ipcs is ru
Jim Nasby <[EMAIL PROTECTED]> writes:
> I'm guessing the issue here is shmall, which I believe is limiting
> you to 4MB of shared memory. Is there *anything* using shared memory
> in the ipcs report?
Right, it looks like shmall is the problem. I believe BTW that you
need to do "sudo ipcs -a"
When you increase shmmax, you need to increase shmall as well. Max is the
largest single allocation allowed, in bytes. All is the total SysV shared
memory available to all processes, in pages. (I think...)
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303) 722-0567 voice
---
On May 7, 2007, at 6:19 AM, Christopher S Martin wrote:
No .pid files found in the data directory.
The ipcs output doesn't list anything owned by the postgres user,
or by root.
I'm guessing the issue here is shmall, which I believe is limiting
you to 4MB of shared memory. Is there *anything
Bah, evil google interface. My reply was ment for the list.
On 5/7/07, Isak Hansen <[EMAIL PROTECTED]> wrote:
On 5/7/07, Christopher S Martin <[EMAIL PROTECTED]> wrote:
> sysctl -a reveals the following:
> kern.sysv.shmmax: 12582912
Maximum size of shared memory segment (afaik bytes - needs to
Just a note:
Reducing the amount of default connections to 25 and increasing shmmax
to 40 Mb did not fix the problem.
Interestingly, changing the max_connections values to 25 was not
reflected in the HINT output after postmaster failed to launch, it
still reports max connections as 30.
Thanks,
C
The shared_buffers and max_connections values are both set to the
default values (unchanged i the configuration file). For
max_connections this is 50, and for the shared_buffers I believe the
default is 32mb.
Do you suggest setting the shmmax value to 32mb or greater?
Thanks,
Chris
My developm
Hi Chris,
Please let me know your shared_buffers & max_connections .
How much RAM your sstem has.
You have set up your shmmax to 12MB.
I hope these DB parameters have larger in values and stopping the allocating
of shared memory segments during start up of the database.
if your system has enough
No .pid files found in the data directory.
The ipcs output doesn't list anything owned by the postgres user, or by root.
Thanks,
Chris
On 5/7/07, Prashant Ranjalkar <[EMAIL PROTECTED]> wrote:
Hello,
Please check any .pid file exist in your data directory. If it exists then
postmaster is runni
Hello,
Please check any .pid file exist in your data directory. If it exists then
postmaster is running and memory is not freed up.
Also check
ipcs -mp
it will give any shared memory allocated segments if any and consuming the
memory.
regards
Prashant Ranjalkar
On 5/7/07, Christopher S Martin
sysctl -a reveals the following:
kern.sysv.shmmax: 12582912
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 8
kern.sysv.shmall: 1024
kern.sysv.semmni: 87381
kern.sysv.semmns: 87381
kern.sysv.semmnu: 87381
kern.sysv.semmsl: 87381
kern.sysv.semume: 10
I am using the sysctl.conf file in /
Hello,
The previously running postmaster process might not closed properly and
released the kernel's memory.
Check for any process running on the server if it exists then kill the
process.here due to unrelease of kernel's memory and while booting the
process is not releasing shared memory hence l
First off, use sysctl to see what values are actually being set:
sysctl -a | grep kern.sysv.
The if they're not what you think they should be, tell us exactly how you're
trying to set them.
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303) 722-0567 voice
"Christopher S Martin" <[EMAIL PROTECTED]> writes:
> I was previous running postgres 8.2.1 on my OS X 10.4.9 laptop with no
> problems.
> After I sent it to apple care, I found that I can no longer start the
> postmaster daemon. When I try, I receive the standard shmget failed
> error message:
Martin:
They didn't take any memory out of the machine. AS for memory cache
parameters, I'm don't know about that. How would I go checking for
that type of thing?
Thanks,
Chris
On 5/6/07, Martin Gainty <[EMAIL PROTECTED]> wrote:
if you're getting memory errors then a guess would be did they
if you're getting memory errors then a guess would be did they take out any
memory out of your machine or perhaps did they change your memory cache
parameters???
Martin
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom t
17 matches
Mail list logo
