Обсуждение: IpcMemoryDetach
I'm using a servlet-engine and the PostgreSQL JDBC driver to connect to a Cygwin version of PostgreSQL 7.0.3 that I havecompiled ... using also ipc-daemon 1.8 i think the version is ... whatever the latest is .. anyways i've been havingthis problem today and I can't figure out why .. it happens when i shut down the servlet-engine and abruptly kill connections.. and it has never happened before /usr/local/pgsql/bin/postmaster: ServerLoop: select failed: No children proc_exit(1) shmem_exit(1) NOTICE: IpcMemoryDetach: shmdt(0x0x7190000): Invalid argument NOTICE: IpcMemoryDetach: shmdt(0x0x7060000): Invalid argument NOTICE: IpcMemoryDetach: shmdt(0x0x7050000): Invalid argument exit(1) anyone have any ideas what this might be? i'm running a win2000 box -a
Hi, On Thu, 18 Jan 2001 00:31:06 -0800 Andrew Lombardi <andrew.lombardi@home.com> wrote: > I'm using a servlet-engine and the PostgreSQL JDBC driver to connect to a Cygwin version of PostgreSQL 7.0.3 that I havecompiled ... using also ipc-daemon 1.8 i think the version is ... whatever the latest is .. anyways i've been havingthis problem today and I can't figure out why .. it happens when i shut down the servlet-engine and abruptly kill connections.. > > and it has never happened before > > /usr/local/pgsql/bin/postmaster: ServerLoop: select failed: No children > proc_exit(1) > shmem_exit(1) > NOTICE: IpcMemoryDetach: shmdt(0x0x7190000): Invalid argument > NOTICE: IpcMemoryDetach: shmdt(0x0x7060000): Invalid argument > NOTICE: IpcMemoryDetach: shmdt(0x0x7050000): Invalid argument > exit(1) > > anyone have any ideas what this might be? It's a harmless bug of cygipc . Please use this patch against cygipc 1.08. -- Yutaka tanida <yutaka@hi-net.zaq.ne.jp>
Вложения
Andrew,
On Thu, Jan 18, 2001 at 12:31:06AM -0800, Andrew Lombardi wrote:
> I'm using a servlet-engine and the PostgreSQL JDBC driver to connect
> to a Cygwin version of PostgreSQL 7.0.3 that I have compiled ... using
> also ipc-daemon 1.8 i think the version is ... whatever the latest is
> .. anyways i've been having this problem today and I can't figure out
> why .. it happens when i shut down the servlet-engine and abruptly kill
> connections ..
>
> and it has never happened before
>
> /usr/local/pgsql/bin/postmaster: ServerLoop: select failed: No children
The above problem is discussed in the thread that begins with:
http://www.postgresql.org/mhonarc/pgsql-ports/2000-12/msg00046.html
It has been fixed and is available in 7.1 Beta 3:
ftp://postgresql.readysetnet.com/pub/postgresql/dev/postgresql-7.1beta3.tar.gz
or from CVS:
http://www.postgresql.org/devel-corner/docs/postgres/anoncvs.htm
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Yutaka,
On Thu, Jan 18, 2001 at 06:27:47PM +0900, Yutaka tanida wrote:
> > anyone have any ideas what this might be?
>
> It's a harmless bug of cygipc . Please use this patch against cygipc
> 1.08.
Thanks for another patch. Have you been submitting these patches to:
Charles Wilson <cwilson@ece.gatech.edu>
Thanks,
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Andrew Lombardi <andrew.lombardi@home.com> writes:
> /usr/local/pgsql/bin/postmaster: ServerLoop: select failed: No children
This is a known bug --- the postmaster's SIGCHLD signal handler needs to
save and restore errno. Fixed in 7.1, and a patch for 7.0.* has been
described on the lists a couple of times ...
regards, tom lane
Yutaka, On Thu, Jan 18, 2001 at 06:27:47PM +0900, Yutaka tanida wrote: > It's a harmless bug of cygipc . Please use this patch against cygipc 1.08. It appears that this patch is no longer necessary when running against the latest Cygwin CVS. Do you think that Chris Faylor's recent signal handling work fixed this problem too? Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Jason, On Tue, 6 Feb 2001 09:45:49 -0500 Jason Tishler <Jason.Tishler@dothill.com> wrote: > It appears that this patch is no longer necessary when running against > the latest Cygwin CVS. No. It fixes a bug that is not related on this one. > Do you think that Chris Faylor's recent signal > handling work fixed this problem too? I agree it was fixed. But I think there's more bugs not related PostgreSQL.... --- Yutaka tanida<yutaka@hi-net.zaq.ne.jp>
On Tue, Feb 06, 2001 at 09:45:49AM -0500, Jason Tishler wrote: > On Thu, Jan 18, 2001 at 06:27:47PM +0900, Yutaka tanida wrote: > > It's a harmless bug of cygipc . Please use this patch against cygipc 1.08. > > It appears that this patch is no longer necessary when running against > the latest Cygwin CVS. Do you think that Chris Faylor's recent signal > handling work fixed this problem too? Yutaka's patch *is* still needed to eliminated this annoying cygipc error message. I thought that I was using an unmodified cygipc-1.08 when I wrote this email. Unfortunately, I was wrong -- I was still using the patched version. Sorry, for the noise... Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com