-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[YSQL] Cloud - postgres crash during fork() #13091
Labels
Comments
vmallepalli
added
area/ysql
Yugabyte SQL (YSQL)
status/awaiting-triage
Issue awaiting triage
labels
Jun 28, 2022
yugabyte-ci
added
kind/bug
This issue is a bug
priority/medium
Medium priority issue
labels
Jun 28, 2022
Here are the postgres logs that include the timestamp when the core files were created. |
I googled the last line above - there were some entries from 2017 which I don't think are relevant. |
|
sushantrmishra
changed the title
[YSQL] Cloud - postgres - two core files generated - pls rename this issue based on backtrace content
[YSQL] Cloud - postgres crash during fork()
Oct 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Jira Link: DB-2802
Description
We saw two core files get generated around the same time in a cluster created using Yugabyte Managed. Please TAL in case it helps mitigate any future crashes !
Cluster-id: e0dd2601-6008-4674-90b7-792e0ab09f08
Db-version: 2.12.5.1-b2
PagerDuty generated alert - https://yugabyte.pagerduty.com/incidents/Q2XLOVQ1E5BT77
First Core File Backtrace
Core was generated by `/home/yugabyte/yb-software/yugabyte-2.12.5.1-b2-centos-x86_64/postgres/bin/post'.
Program terminated with signal 11, Segmentation fault.
#0 __GI_abort () at abort.c:125
Thread 1 (LWP 5006):
#0 __GI_abort () at abort.c:125
#1 0x00007fa4a1e681f6 in __assert_fail_base (fmt=0x7fa4a1fa1198 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fa4a1fa2f40 "THREAD_GETMEM (self, tid) != ppid", file=file@entry=0x7fa4a1f9f00f "../sysdeps/nptl/fork.c", line=line@entry=136, function=function@entry=0x7fa4a1f9f026 <PRETTY_FUNCTION.12124> "__libc_fork") at assert.c:92
#2 0x00007fa4a1e682a2 in __GI___assert_fail (assertion=0x7fa4a1fa2f40 "THREAD_GETMEM (self, tid) != ppid", file=0x7fa4a1f9f00f "../sysdeps/nptl/fork.c", line=136, function=0x7fa4a1f9f026 <PRETTY_FUNCTION.12124> "__libc_fork") at assert.c:101
#3 0x00007fa4a1ef2335 in __libc_fork () at ../sysdeps/nptl/fork.c:136
#4 0x00000000007dbe70 in fork_process () at ../../../../../../src/postgres/src/backend/postmaster/fork_process.c:61
#5 0x000000000049df59 in BackendStartup (port=0x1fc0960) at ../../../../../../src/postgres/src/backend/postmaster/postmaster.c:4121
#6 ServerLoop () at ../../../../../../src/postgres/src/backend/postmaster/postmaster.c:1754
#7 0x00000000007ebb8f in PostmasterMain (argc=argc@entry=23, argv=argv@entry=0x1e9a300) at ../../../../../../src/postgres/src/backend/postmaster/postmaster.c:1417
#8 0x00000000007372aa in PostgresServerProcessMain (argc=23, argv=0x1e9a300) at ../../../../../../src/postgres/src/backend/main/main.c:234
#9 0x00000000007374a9 in main ()
Second Core File Backtrace
Core was generated by `/home/yugabyte/yb-software/yugabyte-2.12.5.1-b2-centos-x86_64/postgres/bin/post'.
Program terminated with signal 6, Aborted.
#0 0x00007fa4a1f1b253 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:84
Thread 1 (LWP 18730):
#0 0x00007fa4a1f1b253 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:84
#1 0x000000000049d83a in ServerLoop () at ../../../../../../src/postgres/src/backend/postmaster/postmaster.c:1711
#2 0x00000000007ebb8f in PostmasterMain (argc=argc@entry=23, argv=argv@entry=0x1e9a300) at ../../../../../../src/postgres/src/backend/postmaster/postmaster.c:1417
#3 0x00000000007372aa in PostgresServerProcessMain (argc=23, argv=0x1e9a300) at ../../../../../../src/postgres/src/backend/main/main.c:234
#4 0x00000000007374a9 in main ()
The text was updated successfully, but these errors were encountered: