Re: LOG: munmap(0x7fff80000000) failed: Invalid argument

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Richards <chris(at)infinite(dot)io>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: LOG: munmap(0x7fff80000000) failed: Invalid argument
Date: 2016-10-10 22:21:48
Message-ID: 17878.1476138108@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Richards <chris(at)infinite(dot)io> writes:
> Setting up postgresql-9.5 (9.5.4-1.pgdg14.04+2) ...
> Creating new cluster 9.5/main ...
> config /etc/postgresql/9.5/main
> data /var/lib/postgresql/9.5/main
> locale en_US.UTF-8
> LOG: munmap(0x7fff80000000) failed: Invalid argument
> [... snip 14 or so repeats ...]
> LOG: munmap(0x7fff80000000) failed: Invalid argument
> socket /var/run/postgresql
> port 5433
> update-alternatives: using
> /usr/share/postgresql/9.5/man/man1/postmaster.1.gz to provide
> /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
> * Starting PostgreSQL 9.5 database server
> [ OK ]
> Processing triggers for libc-bin (2.19-0ubuntu6.6) ...

> I'm able to connect and I dumped a few default relations.

> Is the munmap error of concern? It remains upon rebooting / restarting the
> server.

Seems pretty fishy to me; I don't know what would be causing it.

[ digs in code... ] One theory is that PGSharedMemoryDetach is getting
called more than once, but I'm not sure how that would happen. Can you
characterize where this happens more precisely? What nondefault settings
have you got in postgresql.conf?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Mead 2016-10-10 22:28:46 Re: [SPAM] psql 9.3 automatic recovery in progress
Previous Message Tom Lane 2016-10-10 22:15:10 Re: [SPAM] psql 9.3 automatic recovery in progress