standby log FATAL "no PostgreSQL user name specified in startup packet" | "the database system is starting up" on Tanzu Greenplum
search cancel

standby log FATAL "no PostgreSQL user name specified in startup packet" | "the database system is starting up" on Tanzu Greenplum

book

Article ID: 296575

calendar_today

Updated On:

Products

VMware Tanzu Greenplum

Issue/Introduction

Problem A
2022-07-06 13:42:30.718561 BST,"gpadmin","gpadmin",p22772,th-1105565824,"10.225.28.70","23938",2022-07-06 13:42:30 BST,0,,,seg-1,,,,,"FATAL","57P03","the database system is starting up",,,,,,,0,,"postmaster.c",2927,

Problem B
2022-07-11 09:12:06.719760 BST,,,p31586,th-1105565824,"[local]",,2022-07-11 09:12:06 BST,0,,,seg-1,,,,,"FATAL","28000","no PostgreSQL user name specified in startup packet",,,,,,,0,,"postmaster.c",2863,

Environment

Product Version: 5.28

Resolution

Problem A
"the database system is starting up" is usually an indication of attempting connect to standby master directly which shouldn't happen as this is a standby

mdw$ psql -h smdw
psql: FATAL:  the database system is starting up

Problem B
"no PostgreSQL user name specified in startup packet" is when you try to connect but don't specify the user
$ psql -h smdw -U ""
psql: FATAL:  no PostgreSQL user name specified in startup packet

Both FATAL's can be ignored.