Mail Archives: cygwin/2004/06/17/17:58:00
At 05:45 PM 6/17/2004, you wrote:
>--- Larry Hall <cygwin-lh AT cygwin DOT com> wrote:
>> At 12:27 PM 6/17/2004, you wrote
>> >--- Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu> wrote:
>> >> On Thu, 17 Jun 2004, Natalie Menk wrote:
>> >>
<snip>
>> >
>> >Now I get nearly the same fork errror message under postgresql 7.4.2
>> >while starting postmaster.
>> >It looks like this:
>> >--------------------------
>> >n AT n ~
>> >$ CYGWIN=server postmaster -D edge_inline -h localhost -i
>> >WARNING: dup(0) failed after 3195 successes: Bad file descriptor
>> >C:\cygwin\bin\postgres.exe (2164): *** fork: can't reserve memory
>> for
>> >stack 0x30
>> >000 - 0x230000, Win32 error 487
>> > 5 [main] postmaster 3336 proc_subproc: Couldn't duplicate my
>> >handle<0x7F4>
>> > for pid 2164, Win32 error 5
>> > 396 [main] postmaster 3336 sync_with_child: child 2164(0x668)
>> died
>> >before in
>> >itialization with status code 0x1
>> > 517 [main] postmaster 3336 sync_with_child: *** child state
>> waiting
>> >for long
>> >jmp
>> >LOG: could not fork statistics buffer: Resource temporarily
>> >unavailable
>> > 27885 [main] postmaster 3336 fork_copy: linked dll data/bss pass 0
>> >failed, 0x7
>> >7B000..0x787880, done 0, windows pid 3780, Win32 error 487
>> >LOG: could not fork startup process: Resource temporarily
>> unavailable
<snip>
>> >I coulnd't find something helpful with Google, googling for the
>> exact
>> >error message or parts from it. Because of that I'm asking here.
>>
>>
>> Really? I found tons of hits with just "Win32 error 487". I'll
>> admit
>> that you'd probably find it more comforting to have something that
>> mentions PostgreSQL. But that's easy:
>>
>>
><http://www.google.com/search?as_q=PostgreSQL&num=10&hl=en&ie=UTF-8&btnG=Google+Search&as_epq=Win32+error+487&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_nlo=&as_nhi=&as_occt=any&as_dt=i&as_sitesearch=cygwin.com&safe=images>
>>
>> That's close enough right? If you need more of a hint, think
>> 'rebaseall'.
>>
>>
>
>I tried 'rebaseall' and get still the same error message.
>I would use rebase but i don't know which options (especially which
>BaseAdress)I should use.(So I tried 'rebase -b 0x30000 -o
>0x230000'without success.)
No, don't fool around with 'rebase' if you don't know what you're doing.
Stick with 'rebaseall'. You might want to reinstall any package that you
attempted a 'rebase' on (as opposed to 'rebaseall'). Are you sure it's not a
Windows problem? Previously reports indicated if 'rebaseall' didn't solve
it, a Windows update would. As always, YMMV.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -