Thread: problems installing postgre
Dear Sirs,
I'm installing Verity K2 Dashboard (with postgre integrated) and get error messages during the postgre installation part:
IpcMemoryCreate: shmget failed (Invalid argument) key=5432010, size=144,
permiss
ion=700
This type of error is usually caused by an improper
shared memory or System V IPC semaphore configuration.
For more information, see the FAQ and platform-specific
FAQ's in the source directory pgsql/doc or on our
web site at http://www.postgresql.org.
IpcMemoryIdGet: shmget failed (No such file or directory) key=5432010,
size=144,
permission=0
IpcMemoryAttach: shmat failed (Invalid argument) id=-2
FATAL 1: AttachSLockMemory: could not attach segment
Our shared memory segment size is 4 MB,
our OS Sun/Solaris 5.7
Please can you give me some advice?
Best regards,
Johannes Heinz
I'm installing Verity K2 Dashboard (with postgre integrated) and get error messages during the postgre installation part:
IpcMemoryCreate: shmget failed (Invalid argument) key=5432010, size=144,
permiss
ion=700
This type of error is usually caused by an improper
shared memory or System V IPC semaphore configuration.
For more information, see the FAQ and platform-specific
FAQ's in the source directory pgsql/doc or on our
web site at http://www.postgresql.org.
IpcMemoryIdGet: shmget failed (No such file or directory) key=5432010,
size=144,
permission=0
IpcMemoryAttach: shmat failed (Invalid argument) id=-2
FATAL 1: AttachSLockMemory: could not attach segment
Our shared memory segment size is 4 MB,
our OS Sun/Solaris 5.7
Please can you give me some advice?
Best regards,
Johannes Heinz
Johannes Heinz <j.heinz@sz-sb.de> writes: > I'm installing Verity K2 Dashboard (with postgre integrated) and get > error messages during the postgre installation part: > IpcMemoryCreate: shmget failed (Invalid argument) key=5432010, size=144, > permission=700 It looks to me like you must not have SysV shared memory support enabled at all. I have no idea where to turn that on in Solaris ... there is some info in the PG Admin Guide, which may or may not help: http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/kernel-resources.html#SYSVIPC Also, I'd suggest pestering Verity to adopt a more modern release of Postgres. You appear to be running 7.0 or something even older. regards, tom lane