Skip to main content
NetApp Knowledge Base

Private mode classification down after upgrade attempt due to postgres corruption

  1. Last updated
  2. Save as PDF
Views:
5
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
ds_dc
Last Updated:

Applies to

  • Darksite (Private Mode)
  • Netapp Data Classification

Issue

When attempting Data Classification upgrade from 1.51 to 1.53, UI went down and did not recover.
Logs seen from Classification upgrade container:
log v1.0 | 2026-05-08 19:44:51,631 | INFO | ds_logger | waitfor | 344 | 324 | None | waitfor_344 | Checking readiness of [postgresql]
log v1.0 | 2026-05-08 19:44:51,634 | INFO | ds_logger | waitfor | 53 | 324 | None | waitfor_53 | Service [postgresql] is not ready:
 connection to server at "postgres" (x.x.x.x, port xxxx failed: server closed the connection unexpectedly
 This probably means the server terminated abnormally
 before or while processing the request.
PostgreSQL Database directory appears to contain a database; Skipping initialization
2026-05-08 19:58:24.745 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port xxxx
2026-05-08 19:58:24.747 UTC [1] LOG:  could not create IPv6 socket for address "::": Address family not supported by protocol
2026-05-08 19:58:24.748 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-05-08 19:58:24.768 UTC [8] LOG:  database system was shut down at 2026-05-03 15:48:11 UTC
2026-05-08 19:58:24.768 UTC [8] LOG:  invalid primary checkpoint record
2026-05-08 19:58:24.768 UTC [8] LOG:  invalid secondary checkpoint record
2026-05-08 19:58:24.768 UTC [8] PANIC:  could not locate a valid checkpoint record
2026-05-08 19:58:24.782 UTC [9] FATAL:  the database system is starting up
2026-05-08 19:58:24.957 UTC [10] FATAL:  the database system is starting up
2026-05-08 19:58:25.116 UTC [11] FATAL:  the database system is starting up
2026-05-08 19:58:25.188 UTC [12] FATAL:  the database system is starting up
2026-05-08 19:58:25.234 UTC [13] FATAL:  the database system is starting up
2026-05-08 19:58:25.493 UTC [14] FATAL:  the database system is starting up
2026-05-08 19:58:25.505 UTC [15] FATAL:  the database system is starting up
2026-05-08 19:58:25.640 UTC [16] FATAL:  the database system is starting up
2026-05-08 19:58:25.690 UTC [17] FATAL:  the database system is starting up
2026-05-08 19:58:25.787 UTC [18] FATAL:  the database system is starting up
2026-05-08 19:58:25.794 UTC [1] LOG:  startup process (PID 8) was terminated by signal 6: Aborted
2026-05-08 19:58:25.794 UTC [1] LOG:  aborting startup due to startup process failure
2026-05-08 19:58:25.813 UTC [1] LOG:  database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.