Re: install Postgres on RHED 7

Try to specify the exact name for the PostgreSQL service, which you can
find under the list of services, using systemctl.

systemctl list-units|grep postgresql

Then you can use the service or systemctl command.
Or
Better to use pg_ctl to start/stop PostgreSQL server.

Thanks & Regards,
*Shreeyansh DBA Team*
www.shreeyansh.com

On Wed, Jan 9, 2019 at 12:03 AM Pepe TD Vo <pepevo(at)yahoo(dot)com> wrote:

> sorry, my fingers split before I can finish all typing:
>
>
>
>
> finally the SA installed the OS libraries and I installed the server
> packages successful but not postgres11-contrib.
> #yum install postgresql11-server postgresql11-contrib --> I see no
> package postgresql11-contrib availabe
> Dependencies resolved
> Transaction test succeeded
> running transaction
> installing: libicu-50.1.2.17.el7.x86_64 1/2
> Installing: postgresql11-11.1-1PGDG.rhel7.x86_64 2/3
> failed to link /usr/bin/psql -> /etc/alternative/pgsql-psql: /usr/bin/pgql
> exists and it's not a a symlink
> failed to link /usr/bin/clusterdb -> /etc/alternatives/pgsql-clusterdb:
> /usr/bin/clusterdb exist and itis not a symlink
>
> failed to link /usr/bin/createdb -> /etc/alternatives/pgsql-createdb:
> /usr/bin/createdb exist and it is not a symlink
> failed to link /usr/bin/createuser -> /etc/alternatives/pgsql-createuser:
> /usr/bin/createuse exist and it is not a symlink
> failed to link /usr/bin/dropdb -> /etc/alternatives/pgsql-dropdb:
> /usr/bin/dropdb exist and it is not a symlink
> failed to link /usr/bin/dropuser -> /etc/alternatives/pgsql-dropuser:
> /usr/bin/dropuser exist and it is not a symlink
> failed to link /usr/bin/pg_basebackup ->
> /etc/alternatives/pgsql-pg_basebackup: /usr/bin/pg_basebackup exist and
> itis not a symlink
> failed to link /usr/bin/pg_dump -> /etc/alternatives/pgsql-pg_dump:
> /usr/bin/pg_dump exist and it is not a symlink
> failed to link /usr/bin/pg_dumpall -> /etc/alternatives/pgsql-pg_dumpall:
> /usr/bin/pg_dumpall exist and it is not a symlink
> failed to link /usr/bin/pg_restore -> /etc/alternatives/pgsql-pg_restore:
> /usr/bin/pg_restore exist and it is not a symlink
> failed to link /usr/bin/reindexdbl -> /etc/alternatives/pgsq-reindexdb:
> /usr/bin/reindexdb exist and it is not a symlink
> failed to link /usr/bin/vacuumdb -> /etc/alternatives/pgsql-vacuumdb:
> /usr/bin/vacuumdbexist and it is not a symlink
>
> installing: postgresql11-server-11.1-1PGDB.rhel7.x86_64 1/3
>
> Verifying: postgresql11-11.1-1PGDB.rhel7.x86_64 1/3
> Verifying: libicu-50.1.2-17.el7.x86_64 2/3
> Verirying: postgresql11-server-11.1-1PGDB.rhel7.x86_64 3/3
>
> Installed:
> postgresql11-server.x86_64 0:11.1-1PGDG.rhel7
> Dependency Installed:
> libicu.x86_64 0:50.1.2-17.el7 postgres11.x86_64 0:11.1-1PGDG.rhel 7
>
> Completed!
>
> After the server successful install, I initialize the database an
>
> # /usr/pgsql-11/bin/postgresql-11-setup initdb
> Initializing database .....OK
>
> # systemctl enable postgres-11
> created symlink from
> /etc/systemd/system/multi-user.target.wants/postgresql-11.service to
> /usr/lib/systemd/system/postgeresql-11.service.
>
> # systemctl start postgresql-11
> # systemctl status postgresql-11
> postgresql-11.service - PostgreSQL 11 database server
> Loaded:loaded (/usr/lib/systemd/system/postgresql-11.service; enabled;
> vendor preset: disabled)
> Active: active (running) since Tues 2019-01-08 12:02:05 EST; 12s ago
> and so on ....
>
> # service postgresql initdb
> hint: the perferred way to do this is now "postgresql-set initdb"
> Initializing database ... OK
>
> but when I tried to correct the postgres.conf with the listen_addresses =
> '*' and port=5432. Restart the postgresql server I get an error.
>
> redirecting to /bin/systemctl start postgresql.service
>
> job for postgresql.service failed because the control proces exited with
> error code. See "systemctl status postgresql.service" and "jouralctl -xe"
> for details.
>
> I run:
> #systemctl status postgresql.service -l
> postgresql.service - PostgreSQL database server
> Loaded:loaded (/usr/lib/systemd/system/postgresql.service; diabled; vendor
> preset: disabled)
> Active: failed (result: exit-code) since Tues 2019-01-08 12:34:43 EST;
> 2min 22s ago
> Process: 6896 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> ${PGPORT} -w -t 300 (code=existed, status=1/FAILURE
> Process: 688 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
> (code=existed, status=0/SUCCESS)
>
> Jan 08 12:34:42 hostname pg_ctl[6896]:HINT: Is another postmaster
> alreadying runnin ...y
> Jan 08 12:34:42 hostname pg_ctl[6896]:LOG: could not bing IPV6 socket:
> Addressa ...se
> Jan 08 12:34:42 hostname pg_ctl[6896]:HINT: Is another postmaster
> alreadying runnin ...y
> Jan 08 12:34:42 hostname pg_ctl[6896]:WARNING: could not create any TCP/IP
> sockets
> Jan 08 12:34:43 hostname pg_ctl[6896]:pg_ctl: could nto start server
> Jan 08 12:34:43 hostname pg_ctl[1]: postgresql.service: control process
> existed, c...=1
> Jan 08 12:34:43 hostname pg_ctl[1]: Failed to start PostgreSQL database
> server.
> Jan 08 12:34:43 hostname pg_ctl[1]: Unit postgresql.service entered failed
> state.
> Jan 08 12:34:43 hostname pg_ctl[1]: postgresql.service failed
>
> Hint: Some lines were ellipsized, use -l to show in full
>
> what I did wrong here? Do I need to add listen_addresses = '*' and port =
> 5432 on both /var/lib/pgsql/data/postgres.conf and
> /var/lib/pgsql/11/data/postgres.conf ?
>
> thank you for all your help.
>
> v/r,
>
>
>
> *Bach-Nga*No one in this world is pure and perfect. If you avoid people
> for their mistakes you will be alone. So judge less, love and forgive more.
> To call him a dog hardly seems to do him justice though in as much as he
> had four legs, a tail, and barked, I admit he was, to all outward
> appearances. But to those who knew him well, he was a perfect gentleman
> (Hermione Gingold)
>
> **Live simply **Love generously **Care deeply **Speak kindly.
> *** Genuinely rich *** Faithful talent *** Sharing success
>
>
> On Thursday, December 20, 2018 4:17 PM, Kris Deugau <kdeugau(at)vianet(dot)ca>
> wrote:
>
>
> Pepe TD Vo wrote:
> > May you suggest me exactly repositories packages needed for install
> > PostgreSQL? Seem to me this link,
> > https://download.postgresql.org/pub/repos/yum/11/redhat/rhel-7-x86_64/
> > all rpm files needed another dependencies. Total more than 300 files
> > and only a few allow me to install the rest of them needed another
> > dependencies and didn't give me exactly what they are.
>
> Some of them will be from the stock Red Hat repositories, and some will
> be from the PGDG repository. I haven't used that repository, and I
> haven't done much on an RPM-based system for a while so I can't give you
> any more specific information.
>
> It's possible - but very tedious and difficult - to install a package
> with a large dependency tree entirely by hand. I *have* done this
> myself in the past, and I recall a few cases where it literally took two
> or three hours to get everything installed to support the specific
> package I started out trying to install. This is why tools like yum
> were developed; they do the work of checking through the list to see
> what's required, and where it can be installed from.
>
> This isn't specific to Postgres; it's how the underlying OS package
> system works. You may want to see if someone in your office has more
> experience installing packages on RHEL with yum and ask them to give you
> a hand. You've got several issues around yum's basic operation that you
> need to fix, and local network/systems admins should know enough about
> your setup to help a lot faster.
>
>
> -kgd
>
>
>
>
>
>