Re: [GENERAL] Unable to start postgresql

See embedded.

On Wednesday 08 March 2017 00:09:56 Adrian Klaver wrote:
> On 03/07/2017 08:17 PM, John Iliffe wrote:
> > I was unable to get postgres started so I did a very basic
> > compile/install to test it.  The configuration line was:
> >
> > ./configure --prefix=/usr/postgres-9.6.2
> >
> > --------------------------------
> > Then I ran make which completed as expected:
> >
> > make[1]: Leaving directory '/tmp/postgresql-9.6.2/config'
> > All of PostgreSQL successfully made. Ready to install.
> >
> > --------------------------------------
> > Then make check
> >
> > make check
> >
> > =======================
> >
> >  All 167 tests passed.
> >
> > =======================
> >
> > make[1]: Leaving directory '/tmp/postgresql-9.6.2/src/test/regress'
> > ----------------------------------------
> >
> > Then make install as user root because of directory permissions.  I
> > have the expected files in /usr/postgres_9.6.2
> >
> > Now, running as user postgres I try and start as stated in the manual
> >
> > postgres -D /usr/pgsql_tablespaces
> >
> > initdb has already been run and the directory pgsql_tablespaces has a
> > number of files as expected.  As yet no database has been defined
> > because psql won't start.
>
> Just to be clear you installed in:
>
> /usr/postgres-9.6.2

yes, and the expected directories /usr/postgres-9.6.2/bin, /include, /lib,
and /share are all there.
>
> but created the data directory in:
>
/usr/pgsql_tablespaces

Yes, I did that to separate the data from the software in case I decide to
update postgresql in the future.  That way I can always revert if
necessary.

> Also above you say:
>
> "I was unable to get postgres started so I did a very basic
> compile/install to test it. "
>

Yes, with no changes except the --prefix in the config file I was assured that
I wasn't causing this problem with a badly chosen parameter.

> To me that implies there is another instance of Postgres on the system,
> is that the case?
>
No other instances of Postgres on the system.  Since it wasn't working I
deleted the original installation by deleting the install directory.

> If not could you explain what you meant?
>
> > The result is:
> > [postgres@prod04 postgresql-9.6.2]$ postgres -D /usr/pgsql_tablespaces
> > LOG:  could not bind IPv4 socket: Cannot assign requested address
> > HINT:  Is another postmaster already running on port 5432? If not,
> > wait a few seconds and retry.
> > LOG:  database system was shut down at 2017-03-07 22:22:57 EST
> > LOG:  MultiXact member wraparound protections are now enabled
> > LOG:  database system is ready to accept connections
> > LOG:  autovacuum launcher started
> >
> > Same results if I use pg_ctl to start the process.
> >
> > I checked with lsof and there is no process bound to socket 5432.
> > There is no entry in /var/run for a socket related to postgresql.
> >
> > I thought it might be a security issue so I put SELinux in permissive
> > mode but the result is the same.  The SELinux journal does not show
> > any warnings on this process.
> >
> > [root@prod04 postgresql-9.6.2]# sestatus
> > SELinux status:                 enabled
> > SELinuxfs mount:                /sys/fs/selinux
> > SELinux root directory:         /etc/selinux
> > Loaded policy name:             targeted
> > Current mode:                   permissive  <------permissive mode**
> > Mode from config file:          permissive
> > Policy MLS status:              enabled
> > Policy deny_unknown status:     allowed
> > Max kernel policy version:      30
> > -----------------------------------------------------------------
> >
> > One thing that I haven't been able to find any the log files.  Where
> > are they normally stored?
> >
> > So, any ideas as to where to go next to debug this would be
> > appreciated! This is a brand new server that I am trying to configure
> > so I have a fair amount of security clearance to chase things.
> >
> > Thanks in advance.
> >
> > John
> > =====================================