Container ptfe_base_startup Failed: Timeout Waiting for Startup Sequencing (Phase 1)

During some Terraform Enterprise upgrades, the application can remain in startup transition and eventually fail with:

Container [ptfe_base_startup/tfe_base_startup] failed: Timeout waiting for event startup sequencing - phase 1

This pattern usually requires quick differentiation between generic startup delay and a specific dependency authentication failure.

Diagnostic Pattern to Confirm

Start with targeted container logs from the host and verify whether repeated authentication failures are present during bootstrap. A common signal set includes:

• startup sequencing timeout in ptfe_base_startup (or tfe_base_startup)
• repeated PostgreSQL auth failures for the internal hashicorp user
• corresponding migration container log failures in relevant versions

Root Cause Pattern

When these indicators align, the failure path often points to an incorrect internal PostgreSQL password during upgrade startup sequence. The application remains blocked because core dependencies do not reach healthy readiness in order.

Recommended Recovery Direction

Use the mounted-disk recovery process for PostgreSQL credentials and then re-attempt startup with validated dependency readiness. The key is to resolve credential mismatch before broader rollback or infrastructure rework.

Support Links

HashiCorp Support article: Container ptfe_base_startup failed: Timeout waiting for event startup sequencing - phase 1

IBM Support article: Container ptfe_base_startup failed: Timeout waiting for event startup sequencing - phase 1

HashiCorp Support content migrated to IBM Support on April 1, 2026. The IBM link is included as the current support platform reference.