Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZTDM-001Ek4-No for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 10:39:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sZTDL-007SyE-7V for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 10:39:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZTDK-007Sy6-PI for pgsql-general@lists.postgresql.org; Thu, 01 Aug 2024 10:39:18 +0000 Received: from mail-yw1-x1136.google.com ([2607:f8b0:4864:20::1136]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sZTDH-002alt-H5 for pgsql-general@postgresql.org; Thu, 01 Aug 2024 10:39:18 +0000 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-661369ff30aso53569997b3.2 for ; Thu, 01 Aug 2024 03:39:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722508753; x=1723113553; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VFQQMKggLJ3Ua9yVXY8c/ddmAxtR3arZjhOyD9ouHT4=; b=manHJawzNle+p2kOP1O5cSOnbgnwvejTb5KuMCDC/eb0lngFuAfmNOjOAXrzRihQ0Y 6ll9S/smOE+5DCfUs1ozD2DbSf2RWLTfWQ7S0SZIUi7Qa38od3hmScfoETN1JbEaLqTG Jc+N9JRf9qR5ICjPoCb33FdPhJ6KwA39y7DfkUSbAVUu4MbpxpoEw2tTemjqAmR4F/g+ RA9Nof20TGWR5Mq46hd3ajjgCDKR7SQ5+Ef0u/HdmZivYIoAID2bGMfNP8mZS9yQzgb+ 5ARr9nINmMyrnVRHFwDtBm9qSp5zeBGZ4cB44x7ePSg45+aXs45vNyZNAlQfCP/7CfS6 I7Hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722508753; x=1723113553; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=VFQQMKggLJ3Ua9yVXY8c/ddmAxtR3arZjhOyD9ouHT4=; b=Z35k2Mzi4Ca46Rl0g0UCBp+xHy1DcyEPtMCTBG4XiIz4Em7XlaDWGWLab/m2Vi5FNN Uy9aqAgB2dgV4XCUcYFSxYicD1VqdWivSVnVL0eLYByEtm4H+b5kRbAyajiYLyftzXat Y+TWDvNRavQbsZFwM9vEUsLLkXi8uWkM/uDmxh7oTyunk0phPQYH7GJoCKhyurSwdvlf kKsJYy7XucykWixRmvBtZdhgz1ftyzyx4R0hbt0qBfEvSHdKTDYWayVLngo6TOC7vib5 59hVDcpOZITPINjCpFOHDcIV4OF3fajvczEtXW5bj5TWa7sgXXXPxE58rFCTd8OBi5ec dP2Q== X-Gm-Message-State: AOJu0YzcfCa2PK72o9adwMOthS4LfL+9yVBi64Eu03Xan8XwiTs2t9Ux MiWCIFf0sqaGoNpT15YKD0+ySNKhfQqr363wnbRTXCxYyiNqIOp0Il6RIerXfM1fDuLRrZEB++X GbWgL1+ywbbX+m9AFihNuNg+lDekg84K+ X-Google-Smtp-Source: AGHT+IEiapZI+DYazJzshk+EA8B/gwa7kLNbtYPPDP5KUnZJXD7ecRjlQXn/jAJabcRCleIdv8Aj6Izn2Tg0YoCGzow= X-Received: by 2002:a0d:c301:0:b0:686:1240:621a with SMTP id 00721157ae682-6874f13312cmr287667b3.31.1722508753413; Thu, 01 Aug 2024 03:39:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Thu, 1 Aug 2024 16:18:04 +0530 Message-ID: Subject: Re: PgBackRest PTR recovery: After table drop to get dropped state To: Kashif Zeeshan Cc: pgsql-general Content-Type: multipart/alternative; boundary="0000000000005eb19f061e9cd287" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005eb19f061e9cd287 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable sorry ignore the previous paste , was in complete Here the full one. https://pastecode.io/s/hya0fyvo On Thu, Aug 1, 2024 at 4:02=E2=80=AFPM KK CHN wrote: > The logs are here. > > https://pastecode.io/s/s5dp8ur1 > > > > On Thu, Aug 1, 2024 at 3:30=E2=80=AFPM Kashif Zeeshan > wrote: > >> Hi >> >> On Thu, Aug 1, 2024 at 2:54=E2=80=AFPM KK CHN wrote= : >> >>> List, >>> >>> *Not working (start EPAS server always fails):* >>> >>> 1. Testing PTR using PgBackRest(2.52.1) on RHEL9 EPAS-16, and RHEL9 = ( >>> Repo Server) >>> >>> When I do a PTR >>> >>> 1. After doing a table drop and then >>> 2. Noting down the time stamp and then >>> 3. Taking an incremental backup in hope that If I do a restore from thi= s >>> incr Backup, that won't contain the dropped table. >>> 4. Correct me if I am conceptually wrong here. >>> 5. I am *never *successful in restoring the EPAS server in this >>> scenario. >>> >>> >>> *I know the following will work for me, w*hy not the above one if I >>> really want that state of cluster also ? >>> >>> *This is Working. * >>> 1. Create table >>> 2. Noting down the timestamp >>> 3. Taking incremental backup on RepoServer. >>> 4. drop the created table . >>> 5. Then stop the EPAS server and do a PTR, by the --set=3Dstep 3 incr >>> backup and target=3D step 2 time stamp .. It finished the pgaback rest= ore >>> and promote command >>> 6. I am able to start back the EPAS server and see the dropped table >>> recovered there. >>> >>> But If I want a PTR as in the first section it fails.. Why ? >>> >>> Thank you, >>> Krishane >>> >>> >>> >>> >>> >>> *What I have done and results obtained: * >>> >>> Created a table important_table4 in my EPAS and note down the time afte= r >>> creation of this table it is ( t1 : "01-AUG-24 14:08:32.447796+05:30"= ) >>> >>> Then I performed an Incremental backup (incr backup: >>> 20240729-160137F_20240801-141148I ) >>> timestamp start/stop: 2024-08-01 14:11:48+05:30 / 2024-08-01 >>> 14:11:52+05:30 >>> >>> >>> Now I dropped the table table4 from the EPAS and noted down the time >>> >>> >>> I want to restore the table4,, so I stopped EPAS and executed >>> >>> $ sudo -u enterprisedb pgbackrest --stanza=3DDemo_Repo --delta >>> --set=3D20240729-160137F_20240801-141148I --target-timeline=3Dcurrent >>> --type=3Dtime --target=3D"01-AUG-24 14:08:32.447796+05:30" >>> --target-action=3Dpromote restore >>> >>> IT WORKS AS EXPECTED .. after restarting the EPAS I am able to get the >>> important_table4 back. >>> >>> root@service01 ~]# sudo -u enterprisedb psql edb >>> psql (16.3.0) >>> Type "help" for help. >>> >>> edb=3D# \dt >>> List of relations >>> Schema | Name | Type | Owner >>> --------+------------------+-------+-------------- >>> public | important_table | table | enterprisedb >>> public | important_table2 | table | enterprisedb >>> public | important_table3 | table | enterprisedb >>> public | important_table4 | table | enterprisedb >>> (4 rows) >>> >>> SO all works fine !!!! . >>> >>> >>> *But Now the PROBLEM Statement. * >>> >>> *1. I am dropping the table table 4 again * >>> edb=3D# \q >>> [root@service01 ~]# sudo -u enterprisedb psql -c "begin; drop table >>> important_table4; commit;" edb >>> BEGIN >>> DROP TABLE >>> COMMIT >>> *2 . [root@service01 ~]#* sudo -u enterprisedb psql -Atc "select >>> current_timestamp" edb 01-AUG-24 14:23:22.085076 +05:30 >>> Noting the time as : (01-AUG-24 14:23:22.085076 +05:30 ) >>> >>> 3. Now I am performing an incremental backup after step 2 on REPO >>> SErver ( Hoping that this latest INCR Backup is without dropped >>> important_table4, so that a recovery of the cluster shouldn't show the >>> table4 again. ) >>> >>> incr backup details. : 20240729-160137F_20240801-142433I >>> timestamp start/stop*: 2024-08-01 14:24:33+05:30 / >>> 2024-08-01 14:24:36+05:30* >>> >>> 4. Now I want to test the database recovery after dropping the table4 >>> in step1 to verify that my EPAS restores from the backup in step 3 and = time >>> stamp (01-AUG-24 14:23:22.085076 +05:30, so that the restored EPAS >>> cluster doesn't contain the important_table4. >>> >>> 5. $ sudo -u enterprisedb pgbackrest --stanza=3DDemo_Repo --delta >>> --set=3D20240729-160137F_20240801-142433I --target-timeline=3Dcurrent >>> --type=3Dtime --target=3D"01-AUG-24 14:23:22.085076+05:30" >>> --target-action=3Dpromote restore >>> ------------ >>> ------------- >>> INFO: restore command end: completed successfully (1035ms) >>> >>> *ISSUE: I am unable to get the EPAS Server* in running state after >>> step 5 >>> >>> *What am I doing wrong ? OR am I conceptually wrong ?* >>> >>> >>> >>> >>> OUTPUT on executing step 5. >>> >>> [root@service01 ~]# sudo -u enterprisedb pgbackrest --stanza=3DDemo_Rep= o >>> --delta --set=3D20240729-160137F_20240801-142433I --target-timeline=3D= current >>> --type=3Dtime --target=3D"01-AUG-24 14:23:22.085076+05:30" >>> --target-action=3Dpromote restore >>> >>> 2024-08-01 14:30:03.535 P00 INFO: restore command begin 2.52.1: >>> --delta --exec-id=3D82738-b5fe7415 --log-level-console=3Dinfo >>> --log-level-file=3Ddebug --pg1-path=3D/var/lib/edb/as16/data >>> --pg-version-force=3D16 --repo1-host=3D10.10.20.7 --repo1-host-user=3Dp= ostgres >>> --set=3D20240729-160137F_20240801-142433I --stanza=3DDemo_Repo >>> --target=3D"01-AUG-24 14:23:22.085076+05:30" --target-action=3Dpromote >>> --target-timeline=3Dcurrent --type=3Dtime >>> 2024-08-01 14:30:03.880 P00 INFO: repo1: restore backup set >>> 20240729-160137F_20240801-142433I, recovery will start at 2024-08-01 >>> 14:24:33 >>> 2024-08-01 14:30:03.881 P00 INFO: remove invalid files/links/paths >>> from '/var/lib/edb/as16/data' >>> 2024-08-01 14:30:04.567 P00 INFO: write updated >>> /var/lib/edb/as16/data/postgresql.auto.conf >>> 2024-08-01 14:30:04.569 P00 INFO: restore global/pg_control (performe= d >>> last to ensure aborted restores cannot be started) >>> 2024-08-01 14:30:04.569 P00 INFO: restore size =3D 75.9MB, file total= =3D >>> 2171 >>> 2024-08-01 14:30:04.569 P00 INFO: restore command end: completed >>> successfully (1035ms) >>> *[root@service01 ~]# systemctl start edb-as-16.service* >>> >>> *Now If I check the server status : Its dead * >>> >>> [root@service01 ~]# systemctl status edb-as-16.service >>> =C3=97 edb-as-16.service - EDB Postgres Advanced Server 16 >>> Loaded: loaded (/etc/systemd/system/edb-as-16.service; disabled; >>> preset: disabled) >>> *Active: failed* (Result: exit-code) since Thu 2024-08-01 14:30:58 >>> IST; 4s ago >>> Duration: 228ms >>> Process: 82752 ExecStartPre=3D/usr/edb/as16/bin/edb-as-16-check-db-= dir >>> ${PGDATA} (code=3Dexited, status=3D0/SUCCESS) >>> Process: 82757 ExecStart=3D/usr/edb/as16/bin/edb-postgres -D ${PGDA= TA} >>> (code=3Dexited, status=3D1/FAILURE) >>> Main PID: 82757 (code=3Dexited, status=3D1/FAILURE) >>> CPU: 325ms >>> >>> Aug 01 14:30:56 service01 systemd[1]: Starting EDB Postgres Advanced >>> Server 16... >>> Aug 01 14:30:56 service01 edb-postgres[82757]: 2024-08-01 14:30:56 IST >>> LOG: redirecting log output to logging collector process >>> Aug 01 14:30:56 rservice01 edb-postgres[82757]: 2024-08-01 14:30:56 IST >>> HINT: Future log output will appear in directory "log". >>> Aug 01 14:30:58 service01 systemd[1]: Started EDB Postgres Advanced >>> Server 16. >>> Aug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Main process >>> exited, code=3Dexited, status=3D1/FAILURE >>> Aug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Killing proces= s >>> 82758 (edb-postgres) with signal SIGKILL. >>> A*ug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Failed with >>> result 'exit-code'.* >>> [root@service01 ~]# >>> >>> Any hints/guidance most welcome. >>> >>> Can you please share the DB Server log as it contains the exact error >> which is causing the server not to start. >> >> Thanks >> > --0000000000005eb19f061e9cd287 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
sorry ignore the previous paste , was in complete

=
Here the full one.=C2=A0 =C2=A0https://pastecode.io/s/hya0fyvo


On Thu, Aug 1, 2024 at 4:02=E2=80=AFPM KK CHN= <kkchn.in@gmail.com> wrote= :
The logs are here.=C2=A0=C2=A0


On Thu, Aug 1, 2024 at 3:30=E2=80=AFPM Kashif Zeeshan <kashi.zeeshan@gmail.c= om> wrote:
Hi

=
On Thu, Aug 1, 2024 at 2:54=E2=80=AFP= M KK CHN <kkchn.= in@gmail.com> wrote:
List,

Not wor= king (start EPAS server always fails):=C2=A0

1= . Testing PTR using=C2=A0 PgBackRest(2.52.1)=C2=A0 on RHEL9=C2=A0 EPAS-16, = and RHEL9 ( Repo=C2=A0 =C2=A0 =C2=A0 =C2=A0Server)=C2=A0

=C2=A0 When I do a PTR

1.=C2=A0 After doing= a table drop and then
2. Noting down the time stamp and then=C2= =A0
3. Taking an incremental=C2=A0backup in hope that If I do a r= estore=C2=A0from this incr Backup, that won't=C2=A0 contain the=C2=A0 d= ropped table.=C2=A0
4.=C2=A0Correct me=C2=A0 if I=C2=A0am=C2=A0 c= onceptually wrong here.=C2=A0=C2=A0
5.=C2=A0 I am never su= ccessful in restoring the EPAS server in this scenario.


I know the following=C2=A0will work for me, = why not the above one if I really want=C2=A0that state of cluster also= =C2=A0 ?=C2=A0

This is Working.=C2=A0
=C2=A01. Create table=C2=A0
2. Noting down the timestamp=
3.=C2=A0 Taking incremental backup on RepoServer.
4. d= rop the created table .
5. Then stop the EPAS server and do a=C2= =A0 PTR, by the=C2=A0 --set=3Dstep 3 incr backup=C2=A0 and target=3D step 2= time stamp .. It finished the pgaback=C2=A0restore and promote=C2=A0comman= d
6. I am able to start back the=C2=A0 EPAS server and see the dr= opped table recovered there.

But If I want a PTR a= s in the first section it fails.. Why ?=C2=A0

Than= k you,
Krishane





What I have done and results obtaine= d:=C2=A0

Created a table important_table4 in m= y EPAS and note down the time after creation of this table it is=C2=A0 ( t1= :=C2=A0 "01-AUG-24 14:08:32.447796+05:30" )

=
Then I performed an Incremental backup=C2=A0 =C2=A0(incr backup: 20240= 729-160137F_20240801-141148I )
timestamp start/stop: 2024-08-01 1= 4:11:48+05:30 / 2024-08-01 14:11:52+05:30


=
Now I dropped the table table4 from the EPAS and noted down the = time=C2=A0


I want to=C2=A0 restore = the table4,, so I stopped EPAS and executed=C2=A0

= $ sudo -u enterprisedb pgbackrest --stanza=3DDemo_Repo --delta --set=3D2024= 0729-160137F_20240801-141148I =C2=A0--target-timeline=3Dcurrent --type=3Dti= me =C2=A0--target=3D"01-AUG-24 14:08:32.447796+05:30" --target-ac= tion=3Dpromote restore

IT WORKS AS EXPECTED ..= after restarting the EPAS I am able to get the important_table4 back.=C2= =A0

root@service01 ~]# sudo -u enterprisedb psql e= db
psql (16.3.0)
Type "help" for help.

edb=3D# \dt=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 List of relations=
=C2=A0Schema | =C2=A0 =C2=A0 =C2=A0 Name =C2=A0 =C2=A0 =C2=A0 | Type = =C2=A0| =C2=A0 =C2=A0Owner
--------+------------------+-------+---------= -----
=C2=A0public | important_table =C2=A0| table | enterprisedb
=C2= =A0public | important_table2 | table | enterprisedb
=C2=A0public | impor= tant_table3 | table | enterprisedb
=C2=A0public | important_table4 | tab= le | enterprisedb
(4 rows)

SO all works fine !!!! .=C2= =A0


But Now the PROBLEM State= ment.=C2=A0

1. I am dropping the table = table 4=C2=A0again=C2=A0
edb=3D# \q
[root@service01 ~]# su= do -u enterprisedb psql -c "begin; drop table important_table4; commit= ;" edb
BEGIN
DROP TABLE
COMMIT
2 .=C2=A0 [root@service0= 1 ~]# sudo -u enterprisedb psql -Atc "select current_timestamp&quo= t; edb=C2=A0 01-AUG-24 14:23:22.085076 +05:30
Noting the time= as :=C2=A0 =C2=A0(01-AUG-24 14:23:22.085076 +05:30 )

3. Now=C2=A0 I am performing an incremental backup after step 2=C2= =A0 on REPO SErver ( Hoping that this latest INCR Backup is without dropped= important_table4, so that a recovery of the cluster=C2=A0 shouldn't sh= ow the table4 again. )=C2=A0

=C2=A0 =C2=A0 =C2=A0 = =C2=A0 incr backup details. : 20240729-160137F_20240801-142433I
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 timestamp start/stop: 2024-08-01 14:2= 4:33+05:30 / 2024-08-01 14:24:36+05:30

4. = Now I want to test the database recovery=C2=A0 after dropping the table4 in= step1 to verify that my EPAS restores from the backup in step 3 and time s= tamp (01-AUG-24 14:23:22.085076 +05:30,=C2=A0 =C2=A0so that=C2=A0 the resto= red EPAS cluster doesn't contain the important_table4.

5.=C2=A0 $ sudo -u enterprisedb pgbackrest --stanza=3DDemo_Repo --= delta=C2=A0 =C2=A0--set=3D20240729-160137F_20240801-142433I =C2=A0--target-= timeline=3Dcurrent --type=3Dtime =C2=A0--target=3D"01-AUG-24 14:23:22.= 085076+05:30" --target-action=3Dpromote restore
=C2=A0------= ------
-------------
INFO: restore command end: complet= ed successfully (1035ms)

ISSUE:=C2=A0 =C2= =A0 I am unable to get the EPAS Server in running state after step 5=C2= =A0

=C2=A0What am I doing=C2=A0wrong ?=C2=A0 OR= am I conceptually wrong ?



=

OUTPUT on executing step 5.=C2=A0

<= /div>
[root@service01 ~]# sudo -u enterprisedb pgbackrest --stanza=3DDe= mo_Repo --delta --set=3D20240729-160137F_20240801-142433I =C2=A0--target-ti= meline=3Dcurrent --type=3Dtime =C2=A0--target=3D"01-AUG-24 14:23:22.08= 5076+05:30" --target-action=3Dpromote restore

2024-08-01= 14:30:03.535 P00 =C2=A0 INFO: restore command begin 2.52.1: --delta --exec= -id=3D82738-b5fe7415 --log-level-console=3Dinfo --log-level-file=3Ddebug --= pg1-path=3D/var/lib/edb/as16/data --pg-version-force=3D16 --repo1-host=3D10= .10.20.7 --repo1-host-user=3Dpostgres --set=3D20240729-160137F_20240801-142= 433I --stanza=3DDemo_Repo --target=3D"01-AUG-24 14:23:22.085076+05:30&= quot; --target-action=3Dpromote --target-timeline=3Dcurrent --type=3Dtime2024-08-01 14:30:03.880 P00 =C2=A0 INFO: repo1: restore backup set 202407= 29-160137F_20240801-142433I, recovery will start at 2024-08-01 14:24:33
= 2024-08-01 14:30:03.881 P00 =C2=A0 INFO: remove invalid files/links/paths f= rom '/var/lib/edb/as16/data'
2024-08-01 14:30:04.567 P00 =C2=A0 = INFO: write updated /var/lib/edb/as16/data/postgresql.auto.conf
2024-08-= 01 14:30:04.569 P00 =C2=A0 INFO: restore global/pg_control (performed last = to ensure aborted restores cannot be started)
2024-08-01 14:30:04.569 P0= 0 =C2=A0 INFO: restore size =3D 75.9MB, file total =3D 2171
2024-08-01 1= 4:30:04.569 P00 =C2=A0 INFO: restore command end: completed successfully (1= 035ms)
[root@service01 ~]# systemctl =C2=A0start edb-as-16.service

Now=C2=A0 If I check the server=C2=A0 sta= tus=C2=A0 :=C2=A0 =C2=A0Its dead=C2=A0

[ro= ot@service01 ~]# systemctl =C2=A0status edb-as-16.service
=C3=97 edb-as-= 16.service - EDB Postgres Advanced Server 16
=C2=A0 =C2=A0 =C2=A0Loaded:= loaded (/etc/systemd/system/edb-as-16.service; disabled; preset: disabled)=
=C2=A0 =C2=A0 =C2=A0Active: failed (Result: exit-code) since Thu= 2024-08-01 14:30:58 IST; 4s ago
=C2=A0 =C2=A0Duration: 228ms
=C2=A0 = =C2=A0 Process: 82752 ExecStartPre=3D/usr/edb/as16/bin/edb-as-16-check-db-d= ir ${PGDATA} (code=3Dexited, status=3D0/SUCCESS)
=C2=A0 =C2=A0 Process: = 82757 ExecStart=3D/usr/edb/as16/bin/edb-postgres -D ${PGDATA} (code=3Dexite= d, status=3D1/FAILURE)
=C2=A0 =C2=A0Main PID: 82757 (code=3Dexited, stat= us=3D1/FAILURE)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 CPU: 325ms

Aug 01 14:= 30:56 service01 systemd[1]: Starting EDB Postgres Advanced Server 16...
= Aug 01 14:30:56 service01 edb-postgres[82757]: 2024-08-01 14:30:56 IST LOG:= =C2=A0redirecting log output to logging collector process
Aug 01 14:30:= 56 rservice01 edb-postgres[82757]: 2024-08-01 14:30:56 IST HINT: =C2=A0Futu= re log output will appear in directory "log".
Aug 01 14:30:58 = service01 systemd[1]: Started EDB Postgres Advanced Server 16.
Aug 01 14= :30:58 service01 systemd[1]: edb-as-16.service: Main process exited, code= =3Dexited, status=3D1/FAILURE
Aug 01 14:30:58 service01 systemd[1]: edb-= as-16.service: Killing process 82758 (edb-postgres) with signal SIGKILL.Aug 01 14:30:58 service01 systemd[1]: edb-as-16.service: Failed with re= sult 'exit-code'.
[root@service01 ~]#

Any hints/guidance most welcome.=C2=A0

Can you please share the DB Server log as it contains the ex= act error which is causing the server not to start.

Thanks=C2=A0
--0000000000005eb19f061e9cd287--