Re: Win 32 'could not attach to proper memory at fixed address'
От | Bryan Roberts |
---|---|
Тема | Re: Win 32 'could not attach to proper memory at fixed address' |
Дата | |
Msg-id | 1102969581.41bdfaed435f8@mail.thinktomorrow.com обсуждение исходный текст |
Ответ на | Re: Win 32 'could not attach to proper memory at fixed address' ("Magnus Hagander" <mha@sollentuna.net>) |
Список | pgsql-bugs |
> > shmget(key=5432001, addr=00DB0000) failed: Invalid argument > > 2004-12-13 13:01:11 FATAL: could not attach to proper memory > > at fixed address: > > shmget(key=5432001, addr=00DB0000) failed: Invalid argument > > 2004-12-13 13:01:11 LOG: background writer process (PID > > 3548) exited with exit code 0 > > 2004-12-13 13:01:11 LOG: terminating any other active server > > processes > > 2004-12-13 13:01:11 LOG: all server processes terminated; > > reinitializing > > > > I noticed that there are a couple of references to this on > > the mailing list however the 'Invalid argument' part of the > > message appears to be different. > > > > The problem can be worked around (if you are running locally) > > by changing the postgresql.conf from: > > listen_addresses = '*' > > to: > > listen_addresses = '127.0.0.1' > > You're saying this only happens if listen_addresses='*'? *very* > interesting. Yes it listens on localhost but not the external IP addresses. > Are you running this off the console or through a RDP session? The installation was done from the console. Restarts and config changes have been done using RDP. Due to the listen address differences I'm inclined to think it may be some OS configuration problem. There isn't any firewall or Anti-Virus S/W installed but I'll try a fresh install and see how I get on. I'll also see if I can log the install to see if that turns anything up. Thanks, Bryan
В списке pgsql-bugs по дате отправления: