SA helped and removed all the lock files, he reconfigured the PAMd and reboot the server. Now nothing is working. Postgresql is not running and can't start. The lock file is not existed any more. Grep the port 5432, not running. How to fix the issue?
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.
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, January 10, 2019 11:04 AM, Pepe TD Vo <pepevo@xxxxxxxxx> wrote:
sorry I was out yesterday.
I stop the services and kill -9 all the postgresql process and run ps aux|grep postgres. Nothing is running and start the service as 'service posgresql start" I still get eh error
'Job for postgresql.service failed because the control process existed with error code. See "systemctl status posgresql.service" and "journalctl -xe" for details
As the systemctl status posgresql.service I get
Loaded:loaded (/usr/lib/systemd/system/postgresql.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2019-091-10 09:18:24 EST; 34s ago
Active: failed (Result: exit-code) since Thu 2019-091-10
09:18:24 EST; 34s ago
Process: 20639 ExecStart=//usr/bin/pg_ctl start –D ${PGDATA} –s
–o –p ${PGPORT} –w –t 300 (code=existed, status=1/FAILURE)
Jan 10 09:18:23 hostname systemd[1]: Starting PosgreSQL database
server…
Jan 10 09:18:23 hostname [pg_ctl[20639]: FATAL: could not remove old lock file “/t…ed
Jan 10 09:18:23 hostname [pg_ctl[20639]: HINT: the file seems
accidentally lef ov …n.
Jan 10 09:18:24 hostname [pg_ctl[20639]: pg_ctl: could not start
server
Jan 10 09:18:24 hostname systemd[1]:postgresql.service: control
process existed, c…=1
Jan 10 09:18:24 hostname systemd[1]:Failed to start PostgreSQL
database server.
Jan 10 09:18:24 hostname systemd[1]:Unit postgresql.service
entered failed state.
Jan 10 09:18:24 hostname systemd[1]:postgresql.service failed
Hint: some lines were ellipsized, use –l to show in full.
From journal-xe, I see:
--Unit session -10325.scope has finished
starting up.
--The start-up result is done
Jan 10 09:20:01 hostname systemd[1]: Starting
session 10325 of user root
--Unit session-10325.scope has begun starting up
Jan 10 09:20:01 hostname systemd[1]: Removed slice
User Slice of root
--Unit user-0.slice has finished shutting down.
Jan 10 09:20:01 hostname systemd[1]: Stopping
User Slice of root
--Unit user-0.slice has begun shutting down.
When I grep postgres from systemctl, it loaded failed
failed
#systemctl list-units|grep posgresql
a postgresql-11.service loaded failed failed
PostgreSQL 11 database server
#pg_ctl start
pg_ctl: cannot be run as root
Please log in (using, e.g., “su) as the
(unprivileged) user that will own the server process.
# su postgres
[postgres@hostname]$ pg_ctl start
Pg_ctl: no database directory specified and
environment variable PGDATA unset
Try “pg_ctl –help” for more information.
I am new to Postgresql and any information provide will be appreciated.
thank you.
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.
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 Wednesday, January 9, 2019 2:16 AM, Shreeyansh Dba <shreeyansh2014@xxxxxxxxx> wrote:
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.
On Wed, Jan 9, 2019 at 12:03 AM Pepe TD Vo <pepevo@xxxxxxxxx> 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 availabeDependencies resolvedTransaction test succeededrunning transactioninstalling: libicu-50.1.2.17.el7.x86_64 1/2Installing: postgresql11-11.1-1PGDG.rhel7.x86_64 2/3failed to link /usr/bin/psql -> /etc/alternative/pgsql-psql: /usr/bin/pgql exists and it's not a a symlinkfailed to link /usr/bin/clusterdb -> /etc/alternatives/pgsql-clusterdb: /usr/bin/clusterdb exist and itis not a symlinkfailed to link /usr/bin/createdb -> /etc/alternatives/pgsql-createdb: /usr/bin/createdb exist and it is not a symlinkfailed to link /usr/bin/createuser -> /etc/alternatives/pgsql-createuser: /usr/bin/createuse exist and it is not a symlinkfailed to link /usr/bin/dropdb -> /etc/alternatives/pgsql-dropdb: /usr/bin/dropdb exist and it is not a symlinkfailed to link /usr/bin/dropuser -> /etc/alternatives/pgsql-dropuser: /usr/bin/dropuser exist and it is not a symlinkfailed to link /usr/bin/pg_basebackup -> /etc/alternatives/pgsql-pg_basebackup: /usr/bin/pg_basebackup exist and itis not a symlinkfailed to link /usr/bin/pg_dump -> /etc/alternatives/pgsql-pg_dump: /usr/bin/pg_dump exist and it is not a symlinkfailed to link /usr/bin/pg_dumpall -> /etc/alternatives/pgsql-pg_dumpall: /usr/bin/pg_dumpall exist and it is not a symlinkfailed to link /usr/bin/pg_restore -> /etc/alternatives/pgsql-pg_restore: /usr/bin/pg_restore exist and it is not a symlinkfailed to link /usr/bin/reindexdbl -> /etc/alternatives/pgsq-reindexdb: /usr/bin/reindexdb exist and it is not a symlinkfailed to link /usr/bin/vacuumdb -> /etc/alternatives/pgsql-vacuumdb: /usr/bin/vacuumdbexist and it is not a symlinkinstalling: postgresql11-server-11.1-1PGDB.rhel7.x86_64 1/3Verifying: postgresql11-11.1-1PGDB.rhel7.x86_64 1/3Verifying: libicu-50.1.2-17.el7.x86_64 2/3Verirying: postgresql11-server-11.1-1PGDB.rhel7.x86_64 3/3Installed:postgresql11-server.x86_64 0:11.1-1PGDG.rhel7Dependency Installed:libicu.x86_64 0:50.1.2-17.el7 postgres11.x86_64 0:11.1-1PGDG.rhel 7Completed!After the server successful install, I initialize the database an# /usr/pgsql-11/bin/postgresql-11-setup initdbInitializing database .....OK# systemctl enable postgres-11created 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-11postgresql-11.service - PostgreSQL 11 database serverLoaded: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 agoand so on ....# service postgresql initdbhint: the perferred way to do this is now "postgresql-set initdb"Initializing database ... OKbut 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.servicejob 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 -lpostgresql.service - PostgreSQL database serverLoaded: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 agoProcess: 6896 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p ${PGPORT} -w -t 300 (code=existed, status=1/FAILUREProcess: 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 ...yJan 08 12:34:42 hostname pg_ctl[6896]:LOG: could not bing IPV6 socket: Addressa ...seJan 08 12:34:42 hostname pg_ctl[6896]:HINT: Is another postmaster alreadying runnin ...yJan 08 12:34:42 hostname pg_ctl[6896]:WARNING: could not create any TCP/IP socketsJan 08 12:34:43 hostname pg_ctl[6896]:pg_ctl: could nto start serverJan 08 12:34:43 hostname pg_ctl[1]: postgresql.service: control process existed, c...=1Jan 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 failedHint: Some lines were ellipsized, use -l to show in fullwhat 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 successOn Thursday, December 20, 2018 4:17 PM, Kris Deugau <kdeugau@xxxxxxxxx> 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
