Re: PostgreSQL: Bad system call
On Dec 9 23:40, Reini Urban wrote: Corinna just answered to this problem, which I suspected to be a cygserver problem, but she said that the caller is responsible for allocating the msg buffer, so it should be a postgresql problem. I'm still scratching my head also, because I'm not really convinced, because even cygserver ipcs fails, but I'll try to step through this again. That would be helpful. Note that I did *not* say that cygserver/cygwin can't be blamed. I just don't see (so far perhaps) how that could be possibly the case. Just today I tried a message queue testcase(tm) and ipcs successfully with cygwin 1.5.12 + accompanying tools. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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/
PostgreSQL: Bad system call
Hi all, once again I've hosed my PostgreSQL installation. I've more or less accidentally upgraded PostgreSQL to the latest version and it would start no more. I've perused the archives and collected all remedies I've found. Most notably: - I had fixed the / and /bin permissions previously and made sure they're still ok - I made my postgres user account own the binary - I've removed the cygipc and cygipc2 services - I've installed cygserver and made sure it is actually started - Needless to say, I've rebooted the box too No matter what I do, I'm now stuck with the following error. For test purposes I logged in to my postgres account and started postmaster manually with postmaster -d5 -D /usr/share/postgresql/data [lots of DEBUG messages] DEBUG: invoking IpcMemoryCreate(size=10461184) Bad system call As I got stuck here I desperately tried various things, among them removing cygserver and starting cygipc2 again and downgrading to the previous PostgreSQL version. All this does not help a bit. I've not yet tried to downgrade cygwin1.dll to the previous version (1.5.11 vs. 1.5.12). Can anyone throw me a ring here? Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de -- 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/
Re: PostgreSQL: Bad system call
Markus Hoenicka schrieb: once again I've hosed my PostgreSQL installation. I've more or less accidentally upgraded PostgreSQL to the latest version and it would start no more. I've perused the archives and collected all remedies I've found. Most notably: - I had fixed the / and /bin permissions previously and made sure they're still ok - I made my postgres user account own the binary - I've removed the cygipc and cygipc2 services - I've installed cygserver and made sure it is actually started - Needless to say, I've rebooted the box too No matter what I do, I'm now stuck with the following error. For test purposes I logged in to my postgres account and started postmaster manually with postmaster -d5 -D /usr/share/postgresql/data [lots of DEBUG messages] DEBUG: invoking IpcMemoryCreate(size=10461184) Bad system call As I got stuck here I desperately tried various things, among them removing cygserver and starting cygipc2 again and downgrading to the previous PostgreSQL version. All this does not help a bit. I've not yet tried to downgrade cygwin1.dll to the previous version (1.5.11 vs. 1.5.12). Can anyone throw me a ring here? So finally someone else got the same cygserver problem as me! The cause is that the internal cygserver msg buffer is allocated read-only. (IsBadWritePtr() fails) Reason unknown. gcc? cygwin? Solution pending. Szteps to reproduce: cygserver ipcs = Bad system call -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ -- 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/
Re: PostgreSQL: Bad system call
Reini Urban [EMAIL PROTECTED] was heard to say: The cause is that the internal cygserver msg buffer is allocated read-only. (IsBadWritePtr() fails) Reason unknown. gcc? cygwin? Solution pending. Szteps to reproduce: cygserver ipcs = Bad system call Oh great. I'm afraid fixing this is above my head. But at least I'd like to help track down the culprit. The interesting fact is that I've downgraded all relevant packages that I can think of (PostgreSQL, cygwin1.dll), rebooted the box, stopped cygserver, but still get the error. How can I hose a Cygwin installation that not even downgrading helps? What is it that I did not downgrade that causes the problem? Does setup.exe keep a log of what I precisely up/downgraded? I do like PostgreSQL on Unix a lot, but I really hate to ever touch setup.exe because more often than not I'm left with a broken database engine. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de -- 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/
Re: PostgreSQL: Bad system call
Markus Hoenicka schrieb: Reini Urban [EMAIL PROTECTED] was heard to say: The cause is that the internal cygserver msg buffer is allocated read-only. (IsBadWritePtr() fails) Reason unknown. gcc? cygwin? Solution pending. Szteps to reproduce: cygserver ipcs = Bad system call Oh great. I'm afraid fixing this is above my head. But at least I'd like to help track down the culprit. The interesting fact is that I've downgraded all relevant packages that I can think of (PostgreSQL, cygwin1.dll), rebooted the box, stopped cygserver, but still get the error. How can I hose a Cygwin installation that not even downgrading helps? What is it that I did not downgrade that causes the problem? Does setup.exe keep a log of what I precisely up/downgraded? I do like PostgreSQL on Unix a lot, but I really hate to ever touch setup.exe because more often than not I'm left with a broken database engine. Corinna just answered to this problem, which I suspected to be a cygserver problem, but she said that the caller is responsible for allocating the msg buffer, so it should be a postgresql problem. I'm still scratching my head also, because I'm not really convinced, because even cygserver ipcs fails, but I'll try to step through this again. Several people could successfully compile and run the latest postgresql See e.g. the postgresql buildfarm with gcc-3.3.3. http://www.pgbuildfarm.org/cgi-bin/show_status.pl (Gibbon) -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ -- 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/
