Hi,
I am using EDB(Postgres) in AWS Platform.
I am trying to start the DB using systemctl start edb-as-12.
But I am getting the below error: Not sure about it. can anyone help to fix the issue ?
[root@ip-10-130-5-65 ~]# journalctl -xe
-- Unit systemd-coredump@8-1900775-0.service has finished starting up.
--
-- The start-up result is done.
Jul 26 07:24:34 ip-10-130-5-65.eu-north-1.compute.internal systemd-coredump[1900786]: Core file was truncated to 2147483648 bytes.
-- Subject: Core file was truncated to 2147483648 bytes.
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Documentation: man:coredump.conf(5)
--
-- The process had more memory mapped than the configured maximum for processing
-- and storage by systemd-coredump(8). Only the first 2147483648 bytes were
-- saved. This core might still be usable, but various tools like gdb(1) will warn
-- about the file being truncated.
Jul 26 07:24:34 ip-10-130-5-65.eu-north-1.compute.internal systemd-coredump[1900786]: Removed old coredump core.edb-postmaster.990.4857b7d39b1a4786a45675e7e7b2ea67.1899312.1690356232000000.lz4.
Jul 26 07:24:34 ip-10-130-5-65.eu-north-1.compute.internal systemd-coredump[1900786]: Process 1900770 (edb-postmaster) of user 990 dumped core.
Stack trace of thread 1900770:
#0 0x00007fc8f177d37f n/a (n/a)
-- Subject: Process 1900770 (edb-postmaster) dumped core
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Documentation: man:core(5)
--
-- Process 1900770 (edb-postmaster) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Jul 26 07:24:35 ip-10-130-5-65.eu-north-1.compute.internal systemd[1]: systemd-coredump@8-1900775-0.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit systemd-coredump@8-1900775-0.service has successfully entered the 'dead' state.
Jul 26 07:24:35 ip-10-130-5-65.eu-north-1.compute.internal systemd[1]: edb-as-12.service: Main process exited, code=exited, status=1/FAILURE
Jul 26 07:24:35 ip-10-130-5-65.eu-north-1.compute.internal systemd[1]: edb-as-12.service: Killing process 1900769 (edb-postmaster) with signal SIGKILL.
Jul 26 07:24:35 ip-10-130-5-65.eu-north-1.compute.internal systemd[1]: edb-as-12.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit edb-as-12.service has entered the 'failed' state with result 'exit-code'.
Jul 26 07:24:35 ip-10-130-5-65.eu-north-1.compute.internal systemd[1]: Failed to start EDB Postgres Advanced Server 12.
-- Subject: Unit edb-as-12.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit edb-as-12.service has failed.
--
-- The result is failed.
Jul 26 07:24:39 ip-10-130-5-65.eu-north-1.compute.internal agent[1480]: 2023-07-26 07:24:39 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:125 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:135)>
Jul 26 07:24:51 ip-10-130-5-65.eu-north-1.compute.internal trace-agent[2411]: 2023-07-26 07:24:51 UTC | TRACE | INFO | (run.go:251 in Info) | No data received