You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudberry.apache.org by "jsung11 (via GitHub)" <gi...@apache.org> on 2026/10/09 14:50:51 UTC
[I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
jsung11 opened a new issue, #2101:
URL: https://github.com/apache/cloudberry/issues/2101
### Apache Cloudberry version
Apache Cloudberry 2.1.0-incubating build bdf90c5518f
### What happened
We were attempting to initialize a new Cloudberry cluster and the gpinitsystem failed,
In the gpdb logs we are observing the following
background worker ""dtx recovery process"" (PID 2371538) was terminated by signal 11
gpAdmin logs
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: the database system is in recovery mode
DETAIL: last replayed record at 0/0
var log messages
general protection fault ip:e1d282 sp:7ffed4b01c60 error:0 in postgres[6e6000+a69000]
postgres[2374077]: segfault at 4 ip 0000000000e1d282 sp 00007ffed4b01e10 error 4 in postgres[6e6000+a69000] likely on CPU 28 (core 4, socket 0)
And continous coredump files being created until we terminate postgres proces
### What you think should happen instead
Should be a clean install. gpinitsystem was successful 3 other CB clusters (2 physical hardware and 1 VM)
### How to reproduce
We can only reproduce on this one set of hardware, Any help would be appreciated on what is causing the failure
### Operating System
NAME="Red Hat Enterprise Linux" VERSION="9.7 (Plow)"
### Anything else
gpinitsystem_20261002.log
20261002:22:27:16:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-Start Function ERROR_CHK
20261002:22:27:16:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-Successfully completed failed to register mirror for contentid=91
20261002:22:27:16:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-End Function ERROR_CHK
20261002:22:27:16:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-Start Function ERROR_CHK
20261002:22:27:16:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-Successfully completed failed to register mirror for contentid=92
20261002:22:27:16:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-End Function ERROR_CHK
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: the database system is in recovery mode
DETAIL: last replayed record at 0/0
20261002:22:27:17:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-Start Function ERROR_CHK
20261002:22:27:17:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-End Function ERROR_CHK
20261002:22:27:17:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[INFO]:-Start Function ERROR_EXIT
20261002:22:27:17:2201694 gpinitsystem:pe1uaer5gpm01:gpadmin-[FATAL]:-Failed to complete failed to register mirror for contentid=93 Script Exiting!
coordinator log
2026-10-02 22:27:16.737883 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","background worker ""dtx recovery process"" (PID 2371538) was terminated by signal 11: Segmentation fault",,,,,,,0,,"postmaster.c",4285,
2026-10-02 22:27:16.738047 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","terminating any other active server processes",,,,,,,0,,"postmaster.c",4000,
2026-10-02 22:27:16.738063 PDT,,,p2371541,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","ic-proxy: received signal 3",,,,,,,0,,"ic_proxy_main.c",484,
2026-10-02 22:27:16.738071 PDT,,,p2371541,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","ic-proxy: server closing",,,,,,,0,,"ic_proxy_main.c",585,
2026-10-02 22:27:16.738078 PDT,,,p2371541,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","ic-proxy: server closed with code 1",,,,,,,0,,"ic_proxy_main.c",599,
2026-10-02 22:27:16.739198 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","background worker ""ic proxy process"" (PID 2371541) exited with exit code 1",,,,,,,0,,"postmaster.c",4264,
2026-10-02 22:27:16.739446 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","all server processes terminated; reinitializing",,,,,,,0,,"postmaster.c",4576,
2026-10-02 22:27:16.775137 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system was interrupted; last known up at 2026-10-02 22:27:11 PDT",,,,,,,0,,"xlog.c",6887,
2026-10-02 22:27:16.775166 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","Synchronization of the wal directory starts.",,,,,,,0,,"fd.c",3453,
2026-10-02 22:27:16.775207 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","synchronization of the wal directory finishes.",,,,,,,0,,"fd.c",3455,
2026-10-02 22:27:16.775475 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system was not properly shut down; automatic recovery in progress",,,,,,,0,,"xlog.c",7456,
2026-10-02 22:27:16.775842 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","redo starts at 0/4972CD0",,,,,,,0,,"xlog.c",7736,
2026-10-02 22:27:16.776497 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","invalid record length at 0/497D068: wanted 24, got 0",,,,,,,0,,"xlog.c",4496,
2026-10-02 22:27:16.776504 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","redo done at 0/497D038 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s",,,,,,,0,,"xlog.c",8033,
2026-10-02 22:27:16.776762 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","end of transaction log location is 0/497D068",,,,,,,0,,"xlog.c",8122,
2026-10-02 22:27:16.777350 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","checkpoint starting: end-of-recovery immediate",,,,,,,0,,"xlog.c",9315,
2026-10-02 22:27:16.778146 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","checkpoint complete: wrote 10 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.002 s; sync files=9, longest=0.001 s, average=0.001 s; distance=40 kB, estimate=40 kB",,,,,,,0,,"xlog.c",9396,
2026-10-02 22:27:16.778157 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","latest completed transaction id is 1138 and next transaction id is 1139",,,,,,,0,,"xlog.c",8432,
2026-10-02 22:27:16.778221 PDT,,,p2374065,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system is ready",,,,,,,0,,"xlog.c",8564,
2026-10-02 22:27:16.781696 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","PostgreSQL 14.4 (Apache Cloudberry 2.1.0-incubating build bdf90c5518f) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11), 64-bit compiled on Apr 26 2026 20:17:15",,,,,,,0,,"postmaster.c",3569,
2026-10-02 22:27:16.781707 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system is ready to accept connections","PostgreSQL 14.4 (Apache Cloudberry 2.1.0-incubating build bdf90c5518f) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11), 64-bit compiled on Apr 26 2026 20:17:15",,,,,,0,,"postmaster.c",3571,
2026-10-02 22:27:16.787863 PDT,,,p2374078,th-270645056,,,,0,con4,,seg-1,,,,sx1,"LOG","00000","initialized 1 resource queues",,,,,,,0,,"resscheduler.c",267,
2026-10-02 22:27:16.797428 PDT,"gpadmin","template1",p2374081,th-270645056,"[local]",,2026-10-02 22:27:16 PDT,0,con5,cmd1,seg-1,,,,sx1,"LOG","00000","statement: select pg_catalog.gp_add_segment_mirror(90::int2, 'pe1uaer5gps33.res.prod.global', 'pe1uaer5gps33.res.prod.global', 7002, '/data1/cb/mirror/gpseg90');",,,,,,,0,,"postgres.c",1715,
2026-10-02 22:27:16.855311 PDT,"gpadmin","template1",p2374119,th-270645056,"[local]",,2026-10-02 22:27:16 PDT,0,con6,cmd1,seg-1,,,,sx1,"LOG","00000","statement: select pg_catalog.gp_add_segment_mirror(91::int2, 'pe1uaer5gps34.res.prod.global', 'pe1uaer5gps34.res.prod.global', 7003, '/data1/cb/mirror/gpseg91');",,,,,,,0,,"postgres.c",1715,
2026-10-02 22:27:16.910881 PDT,"gpadmin","template1",p2374155,th-270645056,"[local]",,2026-10-02 22:27:16 PDT,0,con7,cmd1,seg-1,,,,sx1,"LOG","00000","statement: select pg_catalog.gp_add_segment_mirror(92::int2, 'pe1uaer5gps35.res.prod.global', 'pe1uaer5gps35.res.prod.global', 7004, '/data2/cb/mirror/gpseg92');",,,,,,,0,,"postgres.c",1715,
2026-10-02 22:27:16.960131 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","background worker ""dtx recovery process"" (PID 2374077) was terminated by signal 11: Segmentation fault",,,,,,,0,,"postmaster.c",4285,
2026-10-02 22:27:16.960156 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","terminating any other active server processes",,,,,,,0,,"postmaster.c",4000,
2026-10-02 22:27:16.961508 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","all server processes terminated; reinitializing",,,,,,,0,,"postmaster.c",4576,
2026-10-02 22:27:16.996475 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system was interrupted; last known up at 2026-10-02 22:27:16 PDT",,,,,,,0,,"xlog.c",6887,
2026-10-02 22:27:16.996503 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","Synchronization of the wal directory starts.",,,,,,,0,,"fd.c",3453,
2026-10-02 22:27:16.996543 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","synchronization of the wal directory finishes.",,,,,,,0,,"fd.c",3455,
2026-10-02 22:27:16.996658 PDT,"gpadmin","template1",p2374197,th-270645056,"[local]",,2026-10-02 22:27:16 PDT,0,,,seg-1,,,,,"FATAL","57P03","the database system is in recovery mode","last replayed record at 0/0",,,,,,0,,"postmaster.c",2786,
2026-10-02 22:27:16.996779 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system was not properly shut down; automatic recovery in progress",,,,,,,0,,"xlog.c",7456,
2026-10-02 22:27:16.997141 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","redo starts at 0/497D0F0",,,,,,,0,,"xlog.c",7736,
2026-10-02 22:27:16.997715 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","invalid record length at 0/4982190: wanted 24, got 0",,,,,,,0,,"xlog.c",4496,
2026-10-02 22:27:16.997722 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","redo done at 0/4982160 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s",,,,,,,0,,"xlog.c",8033,
2026-10-02 22:27:16.997985 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","end of transaction log location is 0/4982190",,,,,,,0,,"xlog.c",8122,
2026-10-02 22:27:16.998173 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","checkpoint starting: end-of-recovery immediate",,,,,,,0,,"xlog.c",9315,
2026-10-02 22:27:16.998927 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","checkpoint complete: wrote 8 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.001 s; sync files=7, longest=0.001 s, average=0.001 s; distance=20 kB, estimate=20 kB",,,,,,,0,,"xlog.c",9396,
2026-10-02 22:27:16.998939 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","latest completed transaction id is 1141 and next transaction id is 1142",,,,,,,0,,"xlog.c",8432,
2026-10-02 22:27:16.999000 PDT,,,p2374196,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system is ready",,,,,,,0,,"xlog.c",8564,
2026-10-02 22:27:17.002717 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","PostgreSQL 14.4 (Apache Cloudberry 2.1.0-incubating build bdf90c5518f) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11), 64-bit compiled on Apr 26 2026 20:17:15",,,,,,,0,,"postmaster.c",3569,
2026-10-02 22:27:17.002730 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","database system is ready to accept connections","PostgreSQL 14.4 (Apache Cloudberry 2.1.0-incubating build bdf90c5518f) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11), 64-bit compiled on Apr 26 2026 20:17:15",,,,,,0,,"postmaster.c",3571,
2026-10-02 22:27:17.008125 PDT,,,p2374208,th-270645056,,,,0,con4,,seg-1,,,,sx1,"LOG","00000","initialized 1 resource queues",,,,,,,0,,"resscheduler.c",267,
2026-10-02 22:27:17.205450 PDT,,,p2371526,th-270645056,,,,0,,,seg-1,,,,,"LOG","00000","background worker ""dtx recovery process"" (PID 2374207) was terminated by signal 11: Segmentation fault",,,,,,,0,,"postmaster.c",4285,
from /var/log/messages
Oct 2 22:27:16 pe1uaer5gpm01 kernel: traps: postgres[2371538] general protection fault ip:e1d282 sp:7ffed4b01c60 error:0 in postgres[6e6000+a69000]
Oct 2 22:27:16 pe1uaer5gpm01 kernel: postgres[2374077]: segfault at 4 ip 0000000000e1d282 sp 00007ffed4b01e10 error 4 in postgres[6e6000+a69000] likely on CPU 28 (core 4, socket 0)
Oct 2 22:27:16 pe1uaer5gpm01 kernel: Code: 84 00 00 00 01 ed 49 c7 c5 1b c0 66 01 48 63 cd 48 8d 04 cd 00 00 00 00 48 29 c8 41 80 7d 00 00 4c 8d 24 c2 75 32 49 8b 04 24 <80> 78 04 70 74 18 83 c5 01 48 8b 13 48 63 ed 48 8d 04 ed 00 00 00
Coredump files
-rw------- 1 gpadmin gpadmin 218914816 Oct 2 22:27 core.postgres.2371538.1791005236.11.500.500
-rw------- 1 gpadmin gpadmin 206233600 Oct 2 22:27 core.postgres.2374077.1791005236.11.500.500
-rw------- 1 gpadmin gpadmin 206176256 Oct 2 22:27 core.postgres.2374207.1791005237.11.500.500
-rw------- 1 gpadmin gpadmin 206172160 Oct 2 22:27 core.postgres.2374232.1791005237.11.500.500
-rw------- 1 gpadmin gpadmin 206176256 Oct 2 22:27 core.postgres.2374241.1791005237.11.500.500
-rw------- 1 gpadmin gpadmin 206176256 Oct 2 22:27 core.postgres.2374250.1791005237.11.500.500
-rw------- 1 gpadmin gpadmin 206176256 Oct 2 22:27 core.postgres.2374260.1791005237.11.500.500
-rw------- 1 gpadmin gpadmin 206180352 Oct 2 22:27 core.postgres.2374272.1791005238.11.500.500
### Are you willing to submit PR?
- [ ] Yes, I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/cloudberry/blob/main/CODE_OF_CONDUCT.md).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "yjhjstz (via GitHub)" <gi...@apache.org>.
yjhjstz commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6128833766
yes， fixed by https://github.com/apache/cloudberry/pull/2119
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "yjhjstz (via GitHub)" <gi...@apache.org>.
yjhjstz commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6090942077
can you open `core.postgres.2374272.1791005238.11.500.500` with gdb to get the stack ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "yjhjstz (via GitHub)" <gi...@apache.org>.
yjhjstz closed issue #2101: [Issues] When Initializing a new Cloudberry cluster we are encountering issues
URL: https://github.com/apache/cloudberry/issues/2101
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "yjhjstz (via GitHub)" <gi...@apache.org>.
yjhjstz commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6127669522
help to use gdb print value: cdbs->total_entry_dbs, contentId.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "jsung11 (via GitHub)" <gi...@apache.org>.
jsung11 commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6131177909
That would be helpful
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "yjhjstz (via GitHub)" <gi...@apache.org>.
yjhjstz commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6131073865
we can backport to https://github.com/apache/cloudberry/tree/2.1.0-incubating, then release new 2.1.0 ? @tuhaihe
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "jsung11 (via GitHub)" <gi...@apache.org>.
jsung11 commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6126385069
#0 0x0000000000e1d282 in cdbcomponent_getComponentInfo ()
#1 0x0000000000e1d399 in cdbcomponent_allocateIdleQE ()
#2 0x0000000000df0979 in buildGangDefinition ()
#3 0x0000000000df1236 in cdbgang_createGang_async ()
#4 0x0000000000def56d in AllocateGang ()
#5 0x0000000000ded82a in cdbdisp_dispatchCommandInternal ()
#6 0x0000000000e1f94d in TerminateMppBackends ()
#7 0x0000000000e20be5 in DtxRecoveryMain ()
#8 0x0000000000b66cf2 in StartBackgroundWorker ()
#9 0x0000000000b74cba in do_start_bgworker ()
#10 0x0000000000b74e18 in maybe_start_bgworkers ()
#11 0x0000000000b75dcd in reaper ()
#12 0x00007f51f023fc30 in ?? ()
#13 0x0000000000000007 in ?? ()
#14 0x0000000000000000 in ?? ()
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "jsung11 (via GitHub)" <gi...@apache.org>.
jsung11 commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6130641769
Since the change is in c code, and once the PR is completed and merged, How do we go about getting the fix? We are using the rpm package install not compiling. Thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org
Re: [I] [Issues] When Initializing a new Cloudberry cluster we are encountering issues [cloudberry]
Posted by "jsung11 (via GitHub)" <gi...@apache.org>.
jsung11 commented on issue #2101:
URL: https://github.com/apache/cloudberry/issues/2101#issuecomment-6126505999
Did we provide the correct information. When running gdb the following messages were observed
Core was generated by `/usr/local/cloudberry-db-2.1.0/bin/postgres '' '' '' '' '' '''.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000e1d282 in cdbcomponent_getComponentInfo ()
Missing rpms, try: dnf --enablerepo='*debug*' install apache-cloudberry-db-incubating-debuginfo-2.1.0-1.el9.x86_64 zlib-debuginfo-1.2.11-40.el9.x86_64 lz4-libs-debuginfo-1.9.3-5.el9.x86_64 libzstd-debuginfo-1.5.5-1.el9.x86_64 greenplum-db-7-debuginfo-7.5.4-1.el9.x86_64 xz-libs-debuginfo-5.2.5-8.el9_0.x86_64 libcom_err-debuginfo-1.46.5-8.el9.x86_64 keyutils-libs-debuginfo-1.6.3-1.el9.x86_64 libidn2-debuginfo-2.3.0-7.el9.x86_64 libpsl-debuginfo-0.21.1-5.el9.x86_64 libbrotli-debuginfo-1.0.9-9.el9_7.x86_64 libevent-debuginfo-2.1.12-8.el9_4.x86_64 cyrus-sasl-lib-debuginfo-2.1.27-22.el9.x86_64 libcap-ng-debuginfo-0.8.2-7.el9.x86_64 libselinux-debuginfo-3.6-3.el9.x86_64 libunistring-debuginfo-0.9.10-15.el9.x86_64 libxcrypt-debuginfo-4.4.18-3.el9.x86_64 pcre2-debuginfo-10.40-6.el9.x86_64 libuv-debuginfo-1.42.0-2.el9_4.x86_64 protobuf-debuginfo-3.14.0-17.el9_7.x86_64 liburing-debuginfo-2.12-1.el9.x86_64
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/22/0534fdbd9916b09d9585ed4865cc8d69d6a951 /usr/lib/debug/.build-id/22/0534fdbd9916b09d9585ed4865cc8d69d6a951.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/ed/e8a5646fe3c81b6ca3c539513666dd0812d390 /usr/lib/debug/.build-id/ed/e8a5646fe3c81b6ca3c539513666dd0812d390.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/9f/c1490e62b94b1b46bffc368f1f51848743093e /usr/lib/debug/.build-id/9f/c1490e62b94b1b46bffc368f1f51848743093e.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/1f/1ae20fd0e3df21ca3f96bb50e7d607e8b9254a /usr/lib/debug/.build-id/1f/1ae20fd0e3df21ca3f96bb50e7d607e8b9254a.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/20/77fb1f7ad1594458172276b93a09e8a89c29a6 /usr/lib/debug/.build-id/20/77fb1f7ad1594458172276b93a09e8a89c29a6.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/5a/a1f85b6c0b1ed9ef17c254f4430845b7e65b04 /usr/lib/debug/.build-id/5a/a1f85b6c0b1ed9ef17c254f4430845b7e65b04.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/63/82814da5927d356561eceb738266cfc2a4b0bb /usr/lib/debug/.build-id/63/82814da5927d356561eceb738266cfc2a4b0bb.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/9a/cff27a8f772911e21392eb956fed7a1a40f6f9 /usr/lib/debug/.build-id/9a/cff27a8f772911e21392eb956fed7a1a40f6f9.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/82/8914dc8c7f5b2b66517df043be77ab739fbc22 /usr/lib/debug/.build-id/82/8914dc8c7f5b2b66517df043be77ab739fbc22.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/73/2303a00b10700cac568b320be5ec9b1c3a9666 /usr/lib/debug/.build-id/73/2303a00b10700cac568b320be5ec9b1c3a9666.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/13/6ea20518fbb81a2f0909fdb338971ee638351b /usr/lib/debug/.build-id/13/6ea20518fbb81a2f0909fdb338971ee638351b.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/bc/995af1c7722691ca92b24ea8a48d74609fbe74 /usr/lib/debug/.build-id/bc/995af1c7722691ca92b24ea8a48d74609fbe74.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/f4/01784c57b0be5d4012d002c380d69e07fbf0d7 /usr/lib/debug/.build-id/f4/01784c57b0be5d4012d002c380d69e07fbf0d7.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/7d/e5d81d96b55c2813cc19dc5b034587ee0dd32b /usr/lib/debug/.build-id/7d/e5d81d96b55c2813cc19dc5b034587ee0dd32b.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/12/39e197c0bf3870b4530017d100ad94db68e715 /usr/lib/debug/.build-id/12/39e197c0bf3870b4530017d100ad94db68e715.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/c0/657d12f77deec8b9d573bec5f7daae5a548033 /usr/lib/debug/.build-id/c0/657d12f77deec8b9d573bec5f7daae5a548033.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/6e/ded9daba30af8034bf45c5d1e33342c5ad74c9 /usr/lib/debug/.build-id/6e/ded9daba30af8034bf45c5d1e33342c5ad74c9.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/10/58cfb0232cbd4ea55d986b3a588217d0881385 /usr/lib/debug/.build-id/10/58cfb0232cbd4ea55d986b3a588217d0881385.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/cf/344e02d747293b050137b5af99f702a0b37c97 /usr/lib/debug/.build-id/cf/344e02d747293b050137b5af99f702a0b37c97.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/3c/c18b6cc8c3e22d5e630ab414926bc92440c068 /usr/lib/debug/.build-id/3c/c18b6cc8c3e22d5e630ab414926bc92440c068.debug
Missing file(s), try: dnf --enablerepo='*debug*' install /usr/lib/.build-id/a0/6b3a7a41ae8ad1cab2a0efc4d57e353867c8c7 /usr/lib/debug/.build-id/a0/6b3a7a41ae8ad1cab2a0efc4d57e353867c8c7.debug
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cloudberry.apache.org
For additional commands, e-mail: commits-help@cloudberry.apache.org