Oh the email spam :P I did another reboot test to validate the error. It does exist; it does not spam munmap error like it did with the aptitude install.
I then marked the log file, shutdown (1 munmap during), marked it again and then started it (1 munmap during). MARK PRE-SHUTDOWN 2016-10-11 20:02:45 UTC [1656-2] LOG: received fast shutdown request 2016-10-11 20:02:45 UTC [1656-3] LOG: aborting any active transactions 2016-10-11 20:02:45 UTC [1707-2] LOG: autovacuum launcher shutting down 2016-10-11 20:02:45 UTC [1704-1] LOG: shutting down 2016-10-11 20:02:45 UTC [1704-2] LOG: database system is shut down 2016-10-11 20:02:45 UTC [1656-4] LOG: munmap(0x7fff80000000) failed: Invalid argument MARK PRE-START 2016-10-11 20:03:02 UTC [9894-1] LOG: database system was shut down at 2016-10-11 20:02:45 UTC 2016-10-11 20:03:02 UTC [9894-2] LOG: MultiXact member wraparound protections are now enabled 2016-10-11 20:03:02 UTC [9893-1] LOG: database system is ready to accept connections 2016-10-11 20:03:02 UTC [9898-1] LOG: autovacuum launcher started 2016-10-11 20:03:02 UTC [9899-1] LOG: munmap(0x7fff80000000) failed: Invalid argument 2016-10-11 20:03:02 UTC [9900-1] [unknown]@[unknown] LOG: incomplete startup packet On Mon, Oct 10, 2016 at 5:21 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Chris Richards <ch...@infinite.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 >
