One extra bit, if this helps: chrisr@ff1:~$ cat /proc/meminfo MemTotal: 8163104 kB MemFree: 2183692 kB MemAvailable: 3648680 kB Buffers: 170080 kB Cached: 1231708 kB SwapCached: 0 kB Active: 1083596 kB Inactive: 442312 kB Active(anon): 125128 kB Inactive(anon): 3584 kB Active(file): 958468 kB Inactive(file): 438728 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 499708 kB SwapFree: 499708 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 124124 kB Mapped: 42472 kB Shmem: 4596 kB Slab: 144788 kB SReclaimable: 97612 kB SUnreclaim: 47176 kB KernelStack: 10672 kB PageTables: 6332 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 2484108 kB Committed_AS: 900632 kB VmallocTotal: 34359738367 kB VmallocUsed: 202276 kB VmallocChunk: 34359464540 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB HugePages_Total: 4 HugePages_Free: 3 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 1048576 kB DirectMap4k: 83776 kB DirectMap2M: 4110336 kB DirectMap1G: 6291456 kB
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 >
