PowerFlex 4.0.1 - PSQL database stalls on startup causing UI delays
Summary: PSQL database stalls on startup periodically, which causes intermittent UI delays.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Ex. 1: REST Request fails with "Service unavailable. Retry in a few minutes"
SDNASGW logs
Alert service log:
New events will not reach the service while ActiveMQ is down, but existing events should be available for query.
SDNASGW logs
2022-11-22T03:15:10.277603831Z stdout F 127.0.0.1 - - [22/Nov/2022:03:15:10 +0000] "GET /nas-servers?select=count HTTP/1.1" 503 - "" "Vert.x-WebClient/4.1.1"
2022-11-22T03:15:10.277641733Z stdout F 22/Nov/2022:03:15:10 +0000: Attempting to connect to the database...
2022-11-22T03:15:10.278168308Z stdout F 2022-11-22 03:15:10.277 [ERROR] [emc.bedrock.external.rest.PostgRestHttpModule|vert.x-eventloop-thread-1] Request ID: 8e57c553-e13b-4946-985f-03aaab529b31. postgrest service responded it's not ready yet : {"details":"could not translate host name \"postgresql-ha-pgpool.powerflex.svc.cluster.local\" to address: Try again\n","code":"","message":"Database connection error. Retrying the connection."}
2022-11-22T03:15:10.278194846Z stdout F 2022-11-22 03:15:10.278 [WARN ] [com.emc.bedrock.http.HttpVerticle|vert.x-eventloop-thread-1] Request ID: 8e57c553-e13b-4946-985f-03aaab529b31. Client IP: 10.42.0.178. Server IP: 10.42.1.224 Application type: curl/7.66.0. Method: GET. Processing route: /rest/v1/nas-servers?select=count. Request failed. Execution time: 5011 ms. HTTP status code = 503
Ex. 2: Inability to raise/clear alerts.
Alert service log:
{"level":"debug","id":"0000000000000272","code":"2222f000","lifecycleChange":"RAISED","time":1661952719,"message":"Publish message"}
{"level":"debug","topic":"/topic/pfxm_events","time":1661952720,"message":"Received message"}
{"level":"error","event code":"2000aaaa","resource":"sds212","alert code":"2222f000","error":"dial tcp 10.43.143.174:5432: connect: connection refused","time":1661952723,"message":"failed to open transaction"}
{"level":"error","error":"dial tcp 10.43.143.174:5432: connect: connection refused","event id":"6169a2f32b51f987","time":1661952723,"message":"Get Message failed"}
{"level":"warn","error":"key is of invalid type","time":1661952725,"message":"got error parsing token"}
Ex. 3: Event history service is not available because activemq is down.
New events will not reach the service while ActiveMQ is down, but existing events should be available for query.
Cause
PSQL database stalls on startup, and therefore ActiveMQ is also down.
Unstable database connection causes several pods to restart.
Unstable database connection causes several pods to restart.
Resolution
Wait a few minutes for the database to come up, which leads to the service starting again.
At this point the pods will recover.
At this point the pods will recover.
Affected Products
VxRack, PowerFlex ApplianceArticle Properties
Article Number: 000207747
Article Type: Solution
Last Modified: 17 Jun 2025
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.