On 02/17/2018 03:59 PM, Rich Shepard wrote:
On Sat, 17 Feb 2018, Adrian Klaver wrote:
Did pg_upgrade spit out any warnings/errors?
Adrian,
Yes. The uid and gid were mis-matched and, because of that, the
data/directory and all its files were owned by group user, not group
postgres.
In your previous post you showed:
# /etc/rc.postgresql reload
yet below shows:
/etc/rc.d/rc.postgresql
No, the first left off the rc.d/ directory.
Cut and paste error or not?
So are env variables set correctly?
Your ps ax output showed a Postgres instance running:
postgres -D /var/lib/pgsql/10.2/data
Well, I had 'killall postgres' and the server shut down. Don't know why
that was displayed.
Do you know what port it is using and try to connect to it?
The default: /tmp/.s.PGSQL.5432. Everything's shut down now. So I try:
[root@salmo /etc/rc.d]# killall postgres
[root@salmo /etc/rc.d]# ./rc.postgresql start
Could not find 'postgres' binary. Maybe PostgreSQL is not installed
properly?
Yet,
# ll /usr/bin/postgres lrwxrwxrwx 1 root root 35 Feb 17 09:30
/usr/bin/postgres -> ../lib/postgresql/10.2/bin/postgres*
From a previous post:
POSTGRES=/usr/lib${LIBDIRSUFFIX}/@PRGNAM@/$PG_VERSION/bin/postgres
From here:
http://slackbuilds.org/slackbuilds/14.1/system/postgresql/postgresql.SlackBuild
if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686 -DLINUX_OOM_SCORE_ADJ=0"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS="-O2 -march=i686 -mtune=i686 -DLINUX_OOM_SCORE_ADJ=0"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC -DLINUX_OOM_SCORE_ADJ=0"
LIBDIRSUFFIX="64"
else
SLKCFLAGS="-O2 -DLINUX_OOM_SCORE_ADJ=0"
LIBDIRSUFFIX=""
fi
So are you on 64bit system? Because then?:
/usr/bin/postgres -> ../lib/postgresql/10.2/bin/postgres*
would be:
/usr/bin/postgres -> ../lib64/postgresql/10.2/bin/postgres*
You could also try using pg_ctl to start the server directly:
https://www.postgresql.org/docs/10/static/app-pg-ctl.html
Just to prove that the install is good.
Hence, my confustion.
Rich
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
