Thread: postmaster startup segfault: STATUS_ACCESS_VIOLATION at eip=610028AA
Hi all.
I'm running Cygwin 1.5.18-1, PostgreSQL 7.4.5, freshly reinstalled on Windows XP. cygserver is up with semaphore and
sharedmemory limits increased to the max. CYGWIN=server is in the environment, initdb works, but postmaster segfaults
withina second with no messages to the console. At "-d 5", the last line is DEBUG: invoking
IpcMemoryCreate(size=9469952),right after the environment spew.
A postmaster.pid file gets created in the datadir, socket+lock files in /tmp.
IpcMemoryCreate seems to have worked:
$ ipcs -au
Message Queues:
T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID
STIME RTIME CTIME
Message Queue Usage:
msg_ids: 0 (no. of allocated queues)
msg_num: 0 (no. of messages in system)
msg_tot: 0 (size in bytes of messages in system)
Shared Memory:
T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME
DTIME CTIME
m 65536 5432001 --rw------- ebrunar None ebrunar None 0 9469952 3732 3732 23:39:41
23:39:4323:39:41
Shared Memory Usage:
shm_ids: 1 (no. of allocated segments)
shm_tot: 9469952 (size in bytes of allocated segments)
shm_atts: 0 (no. of attached segments in system)
Semaphores:
T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME
s 65536 5432001 --rw------- ebrunar None ebrunar None 17 23:39:41 23:39:41
s 65537 5432002 --rw------- ebrunar None ebrunar None 17 23:39:41 23:39:41
s 65538 5432003 --rw------- ebrunar None ebrunar None 17 23:39:41 23:39:41
Semaphore Usage:
sem_ids: 3 (no. of allocated semaphore sets)
sem_num: 51 (no. of allocated semaphores)
Here's the stackdump:
$ cat postgres.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=610028AA
eax=00000000 ebx=61258F88 ecx=0000004E edx=000001A8 esi=000001A8 edi=61259000
ebp=0022E948 esp=0022E910 program=C:\cygwin\bin\postgres.exe, pid 3732, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022E948 610028AA (00000000, 61258D88, 0022E978, 6101F5E8)
0022E978 6101171C (61156488, 61258D88, 0022E9C8, 61010F4E)
0022E9A8 61011CED (61154A78, 61156448, 611D84D0, 61154A78)
0022E9E8 61011E38 (61154A78, 00000000, 000007B6, 00002000)
0022EA28 6108E3FD (00000000, 00002000, 0022EA68, 1001672C)
0022EA58 610844FF (0022EA78, 0022EA7C, 0022EA88, 0053F2C3)
0022EA88 0055945A (00001538, 00000000, 00001538, 10016648)
0022EEE8 0053D258 (00000005, 100101C0, 0022EF18, 61087959)
0022EF18 00506FFD (00000005, 61157690, 10010090, 7C919AF0)
0022EFD8 61004DD2 (0022EFF0, 00000000, 00000000, 00000000)
0022FF88 6100594F (00000000, 00000000, 00000000, 00000000)
End of stack trace
I don't have anything else of significance running on this machine. Everything was working beautifully until three days
ago(last known access to the postgres server and the one database I really care about). Yesterday, I installed the
OpenSSHutilities via Cygwin setup. I'm not at all sure of a causal relationship, but eventually I reinstalled Cygwin,
creatednew databases, to no avail.
Anybody ever have an experience like this?
Thanks,
Erik
--
Erik Brunar ebrunar voicesignal com
Re: postmaster startup segfault: STATUS_ACCESS_VIOLATION at eip=610028AA
From
Frank-Michael Moser
Date:
Exactly the same here: http://www.cygwin.com/ml/cygwin/2005-07/msg00735.html Frank-Michael Erik Brunar wrote: > Hi all. > > I'm running Cygwin 1.5.18-1, PostgreSQL 7.4.5, freshly reinstalled on > Windows XP. cygserver is up with semaphore and shared memory limits > increased to the max. CYGWIN=server is in the environment, initdb works, > but postmaster segfaults within a second with no messages to the > console. At "-d 5", the last line is DEBUG: invoking > IpcMemoryCreate(size=9469952), right after the environment spew. > > A postmaster.pid file gets created in the datadir, socket+lock files in > /tmp. > > > > IpcMemoryCreate seems to have worked: > > $ ipcs -au > Message Queues: > T ID KEY MODE OWNER GROUP CREATOR > CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME > > Message Queue Usage: > msg_ids: 0 (no. of allocated queues) > msg_num: 0 (no. of messages in system) > msg_tot: 0 (size in bytes of messages in system) > > Shared Memory: > T ID KEY MODE OWNER GROUP CREATOR > CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME > m 65536 5432001 --rw------- ebrunar None ebrunar > None 0 9469952 3732 3732 23:39:41 23:39:43 23:39:41 > > Shared Memory Usage: > shm_ids: 1 (no. of allocated segments) > shm_tot: 9469952 (size in bytes of allocated segments) > shm_atts: 0 (no. of attached segments in system) > > Semaphores: > T ID KEY MODE OWNER GROUP CREATOR > CGROUP NSEMS OTIME CTIME > s 65536 5432001 --rw------- ebrunar None ebrunar > None 17 23:39:41 23:39:41 > s 65537 5432002 --rw------- ebrunar None ebrunar > None 17 23:39:41 23:39:41 > s 65538 5432003 --rw------- ebrunar None ebrunar > None 17 23:39:41 23:39:41 > > Semaphore Usage: > sem_ids: 3 (no. of allocated semaphore sets) > sem_num: 51 (no. of allocated semaphores) > > > > Here's the stackdump: > > $ cat postgres.exe.stackdump > Exception: STATUS_ACCESS_VIOLATION at eip=610028AA > eax=00000000 ebx=61258F88 ecx=0000004E edx=000001A8 esi=000001A8 > edi=61259000 > ebp=0022E948 esp=0022E910 program=C:\cygwin\bin\postgres.exe, pid 3732, > thread main > cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 > Stack trace: > Frame Function Args > 0022E948 610028AA (00000000, 61258D88, 0022E978, 6101F5E8) > 0022E978 6101171C (61156488, 61258D88, 0022E9C8, 61010F4E) > 0022E9A8 61011CED (61154A78, 61156448, 611D84D0, 61154A78) > 0022E9E8 61011E38 (61154A78, 00000000, 000007B6, 00002000) > 0022EA28 6108E3FD (00000000, 00002000, 0022EA68, 1001672C) > 0022EA58 610844FF (0022EA78, 0022EA7C, 0022EA88, 0053F2C3) > 0022EA88 0055945A (00001538, 00000000, 00001538, 10016648) > 0022EEE8 0053D258 (00000005, 100101C0, 0022EF18, 61087959) > 0022EF18 00506FFD (00000005, 61157690, 10010090, 7C919AF0) > 0022EFD8 61004DD2 (0022EFF0, 00000000, 00000000, 00000000) > 0022FF88 6100594F (00000000, 00000000, 00000000, 00000000) > End of stack trace > > > > I don't have anything else of significance running on this machine. > Everything was working beautifully until three days ago (last known > access to the postgres server and the one database I really care about). > Yesterday, I installed the OpenSSH utilities via Cygwin setup. I'm not > at all sure of a causal relationship, but eventually I reinstalled > Cygwin, created new databases, to no avail. > > Anybody ever have an experience like this? > > Thanks, > Erik > > -- > Erik Brunar ebrunar voicesignal com > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings >