You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are using ag version of 2.12 and we have restored the databases using pg_dumpall backup. after restore when we run write command, server process was terminating by singal 11. Could you please check on this. Below are the details.
postgres=# merge (p:account {'ResInternalID':'xxxx'});
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>
!>
alert log details.
2024-01-03 12:16:41 UTC [2757]: [32-1] 65954af9.ac5 0 LOG: server process (PID 10106) was terminated by signal 11: Segmentation fault
2024-01-03 12:16:41 UTC [2757]: [33-1] 65954af9.ac5 0 DETAIL: Failed process was running: merge (p:account {'ResInternalID':'xxxx'});
2024-01-03 12:16:41 UTC [2757]: [34-1] 65954af9.ac5 0 LOG: terminating any other active server processes
2024-01-03 12:16:41 UTC [2757]: [35-1] 65954af9.ac5 0 LOG: archiver process (PID 10092) exited with exit code 2
2024-01-03 12:16:41 UTC [10145]: [1-1] 65955029.27a1 0 postgres admin [unknown] [local]FATAL: the database system is in recovery mode
2024-01-03 12:16:41 UTC [2757]: [36-1] 65954af9.ac5 0 LOG: all server processes terminated; reinitializing
2024-01-03 12:16:41 UTC [10146]: [1-1] 65955029.27a2 0 LOG: database system was interrupted; last known up at 2024-01-03 12:16:04 UTC
2024-01-03 12:16:41 UTC [10147]: [1-1] 65955029.27a3 0 postgres admin[unknown] 240.1.69.195FATAL: the database system is in recovery mode
2024-01-03 12:16:42 UTC [10149]: [1-1] 6595502a.27a5 0 postgres admin [unknown] 240.1.72.135FATAL: the database system is in recovery mode
2024-01-03 12:16:42 UTC [10146]: [2-1] 65955029.27a2 0 LOG: database system was not properly shut down; automatic recovery in progress
2024-01-03 12:16:42 UTC [10146]: [3-1] 65955029.27a2 0 LOG: redo starts at 1/2C854C80
2024-01-03 12:16:42 UTC [10146]: [4-1] 65955029.27a2 0 LOG: invalid record length at 1/2C85A9C8: wanted 24, got 0
2024-01-03 12:16:42 UTC [10146]: [5-1] 65955029.27a2 0 LOG: redo done at 1/2C85A990
2024-01-03 12:16:42 UTC [10146]: [6-1] 65955029.27a2 0 LOG: checkpoint starting: end-of-recovery immediate
The text was updated successfully, but these errors were encountered:
we are using ag version of 2.12 and we have restored the databases using pg_dumpall backup. after restore when we run write command, server process was terminating by singal 11. Could you please check on this. Below are the details.
postgres=# merge (p:account {'ResInternalID':'xxxx'});
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>
!>
alert log details.
2024-01-03 12:16:41 UTC [2757]: [32-1] 65954af9.ac5 0 LOG: server process (PID 10106) was terminated by signal 11: Segmentation fault
2024-01-03 12:16:41 UTC [2757]: [33-1] 65954af9.ac5 0 DETAIL: Failed process was running: merge (p:account {'ResInternalID':'xxxx'});
2024-01-03 12:16:41 UTC [2757]: [34-1] 65954af9.ac5 0 LOG: terminating any other active server processes
2024-01-03 12:16:41 UTC [2757]: [35-1] 65954af9.ac5 0 LOG: archiver process (PID 10092) exited with exit code 2
2024-01-03 12:16:41 UTC [10145]: [1-1] 65955029.27a1 0 postgres admin [unknown] [local]FATAL: the database system is in recovery mode
2024-01-03 12:16:41 UTC [2757]: [36-1] 65954af9.ac5 0 LOG: all server processes terminated; reinitializing
2024-01-03 12:16:41 UTC [10146]: [1-1] 65955029.27a2 0 LOG: database system was interrupted; last known up at 2024-01-03 12:16:04 UTC
2024-01-03 12:16:41 UTC [10147]: [1-1] 65955029.27a3 0 postgres admin[unknown] 240.1.69.195FATAL: the database system is in recovery mode
2024-01-03 12:16:42 UTC [10149]: [1-1] 6595502a.27a5 0 postgres admin [unknown] 240.1.72.135FATAL: the database system is in recovery mode
2024-01-03 12:16:42 UTC [10146]: [2-1] 65955029.27a2 0 LOG: database system was not properly shut down; automatic recovery in progress
2024-01-03 12:16:42 UTC [10146]: [3-1] 65955029.27a2 0 LOG: redo starts at 1/2C854C80
2024-01-03 12:16:42 UTC [10146]: [4-1] 65955029.27a2 0 LOG: invalid record length at 1/2C85A9C8: wanted 24, got 0
2024-01-03 12:16:42 UTC [10146]: [5-1] 65955029.27a2 0 LOG: redo done at 1/2C85A990
2024-01-03 12:16:42 UTC [10146]: [6-1] 65955029.27a2 0 LOG: checkpoint starting: end-of-recovery immediate
The text was updated successfully, but these errors were encountered: