Vous n'êtes pas identifié(e).
Pages : 1
Bonjour,
En utilisant, postgresql 9.6 dans un environnement linux.
Suite d'une coupure d'electricité, postgresql ne veut plus se démarrer actuellement, le log suivant subsiste:
FATAL: the database system is shutting down
2017-09-09 23:02:04 EAT [P:4690][S:59b448bc.1252][T:0][A:[unknown]] ([unknown]@192.168.180.15(56690)): [1-1] LOG: connection received: host=192.168.180.15 port=56690
2017-09-09 23:02:04 EAT [P:4690][S:59b448bc.1252][T:0][A:[unknown]] (rep@192.168.180.15(56690)): [2-1] FATAL: the database system is shutting down
2017-09-09 23:02:09 EAT [P:4691][S:59b448c1.1253][T:0][A:[unknown]] ([unknown]@192.168.180.15(56692)): [1-1] LOG: connection received: host=192.168.180.15 port=56692
2017-09-09 23:02:09 EAT [P:4691][S:59b448c1.1253][T:0][A:[unknown]] (rep@192.168.180.15(56692)): [2-1] FATAL: the database system is shutting down
2017-09-09 23:02:14 EAT [P:4692][S:59b448c6.1254][T:0][A:[unknown]] ([unknown]@192.168.180.15(56694)): [1-1] LOG: connection received: host=192.168.180.15 port=56694
2017-09-09 23:02:14 EAT [P:4692][S:59b448c6.1254][T:0][A:[unknown]] (rep@192.168.180.15(56694)): [2-1] FATAL: the database system is shutting down
2017-09-09 23:10:06 EAT [P:4741][S:59b44a9e.1285][T:0][A:] (@): [1-1] LOG: database system was interrupted; last known up at 2017-09-09 16:56:31 EAT
2017-09-09 23:10:10 EAT [P:4742][S:59b44aa2.1286][T:0][A:[unknown]] ([unknown]@192.168.180.15(56884)): [1-1] LOG: connection received: host=192.168.180.15 port=56884
2017-09-09 23:10:10 EAT [P:4742][S:59b44aa2.1286][T:0][A:[unknown]] (rep@192.168.180.15(56884)): [2-1] FATAL: the database system is starting up
2017-09-09 23:10:15 EAT [P:4744][S:59b44aa7.1288][T:0][A:[unknown]] ([unknown]@192.168.180.15(56886)): [1-1] LOG: connection received: host=192.168.180.15 port=56886
2017-09-09 23:10:15 EAT [P:4744][S:59b44aa7.1288][T:0][A:[unknown]] (rep@192.168.180.15(56886)): [2-1] FATAL: the database system is starting up
2017-09-09 23:10:20 EAT [P:4745][S:59b44aac.1289][T:0][A:[unknown]] ([unknown]@192.168.180.15(56888)): [1-1] LOG: connection received: host=192.168.180.15 port=56888
2017-09-09 23:10:20 EAT [P:4745][S:59b44aac.1289][T:0][A:[unknown]] (rep@192.168.180.15(56888)): [2-1] FATAL: the database system is starting up
2017-09-09 23:10:25 EAT [P:4746][S:59b44ab1.128a][T:0][A:[unknown]] ([unknown]@192.168.180.15(56890)): [1-1] LOG: connection received: host=192.168.180.15 port=56890
2017-09-09 23:10:25 EAT [P:4746][S:59b44ab1.128a][T:0][A:[unknown]] (rep@192.168.180.15(56890)): [2-1] FATAL: the database system is starting up
2017-09-09 23:10:30 EAT [P:4747][S:59b44ab6.128b][T:0][A:[unknown]] ([unknown]@192.168.180.15(56892)): [1-1] LOG: connection received: host=192.168.180.15 port=56892
2017-09-09 23:10:30 EAT [P:4747][S:59b44ab6.128b][T:0][A:[unknown]] (rep@192.168.180.15(56892)): [2-1] FATAL: the database system is starting up
2017-09-09 23:10:35 EAT [P:4748][S:59b44abb.128c][T:0][A:[unknown]] ([unknown]@192.168.180.15(56894)): [1-1] LOG: connection received: host=192.168.180.15 port=56894
2017-09-09 23:10:35 EAT [P:4748][S:59b44abb.128c][T:0][A:[unknown]] (rep@192.168.180.15(56894)): [2-1] FATAL: the database system is starting up
2017-09-09 23:10:40 EAT [P:4749][S:59b44ac0.128d][T:0][A:[unknown]] ([unknown]@192.168.180.15(56896)): [1-1] LOG: connection received: host=192.168.180.15 port=56896
2017-09-09 23:10:40 EAT [P:4749][S:59b44ac0.128d][T:0][A:[unknown]] (rep@192.168.180.15(56896)): [2-1] FATAL: the database system is starting up
Par ailleurs, en faisant :systemctl status postgresql-9.6.service, on obtient:
postgresql-9.6.service - PostgreSQL 9.6 database server
Loaded: loaded (/usr/lib/systemd/system/postgresql-9.6.service; enabled; vendor preset: disabled)
Active: failed (Result: signal) since Sat 2017-09-09 22:50:14 EAT; 1min 3s ago
Process: 4210 ExecStart=/usr/pgsql-9.6/bin/postmaster -D ${PGDATA} (code=killed, signal=KILL)
Process: 4204 ExecStartPre=/usr/pgsql-9.6/bin/postgresql96-check-db-dir ${PGDATA} (code=exited, status=0/SUCCESS)
Main PID: 4210 (code=killed, signal=KILL)
Sep 09 22:40:13 SRVINPI.numen.mg systemd[1]: Starting PostgreSQL 9.6 database server...
Sep 09 22:40:14 SRVINPI.numen.mg postmaster[4210]: 2017-09-09 22:40:14 EAT [P:4210][S:59b4439d.1072][T:0][A:] (@): [1-1] LOG: redirecting log output to log...r process
Sep 09 22:40:14 SRVINPI.numen.mg postmaster[4210]: 2017-09-09 22:40:14 EAT [P:4210][S:59b4439d.1072][T:0][A:] (@): [2-1] HINT: Future log output will appea...rncs_hb".
Sep 09 22:45:13 SRVINPI.numen.mg systemd[1]: postgresql-9.6.service start operation timed out. Terminating.
Sep 09 22:50:14 SRVINPI.numen.mg systemd[1]: postgresql-9.6.service stop-final-sigterm timed out. Killing.
Sep 09 22:50:14 SRVINPI.numen.mg systemd[1]: postgresql-9.6.service: main process exited, code=killed, status=9/KILL
Sep 09 22:50:14 SRVINPI.numen.mg systemd[1]: Failed to start PostgreSQL 9.6 database server.
Sep 09 22:50:14 SRVINPI.numen.mg systemd[1]: Unit postgresql-9.6.service entered failed state.
Sep 09 22:50:14 SRVINPI.numen.mg systemd[1]: postgresql-9.6.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
Auriez vous une solution pour démarrer à nouveau postgresql svp ?
Hors ligne
Les messages affichés par PostgreSQL sont normaux après un redémarrage brutal. Peut-être que systemd lui fait un mauvais coup vu qu'il semble penser que PostgreSQL ne démarre pas (c'est juste qu'il met du temps à démarrer du fait du rejeu des journaux). Pour éviter ça, j'utiliserais pg_ctl pour le lancer et voir ce que cela donne.
Guillaume.
Hors ligne
Je ne comprend pas, pourquoi il metterai beaucoup de temps pour jouer les journaux alors qu'on l'a arrêté proprement avant la coupure ?
Hors ligne
"database system was interrupted" indique qu'il n'a pas été arrêté proprement. Vous n'avez peut-être pass attendu assez longtemps pour qu'il s'arrête proprement.
Guillaume.
Hors ligne
Pages : 1
