App startup failure in Tanzu Platform for Cloud Foundry due to time sync issues

Products

• VMware Tanzu Platform - Cloud Foundry
• VMware Tanzu Application Service

Issue/Introduction

Application staging or startup would fail with the timestamp errors listed below.

2026-04-06T17:14:52.044+08:00 [CELL/0] [ERR] Copying into the container failed: stream-in: nstar: error streaming in: exit status 2. Output: tar: ./app/BOOT-INF/#############: time stamp 2026-04-06 14:51:56 is 20224.552547792 s in the future
2026-04-06T17:14:52.044+08:00 [CELL/0] [ERR] tar: ./app/BOOT-INF/#############: time stamp 2026-04-06 14:51:56 is 20224.552404605 s in the future
2026-04-06T17:14:52.044+08:00 [CELL/0] [ERR] tar: ./app/BOOT-INF/#############: time stamp 2026-04-06 14:51:52 is 20220.552092501 s in the future

Environment

Tanzu Platform for Cloud Foundry
Elastic Application Runtime
Tanzu Application Service 

Cause

This can occur if the application binds to an NFS service and mounts an NFS share in its filesystem, and if there is a time synchronization issue between the application/Diego cell and the NFS server/Appliance.

Resolution

Check the time sync across the Diego Cells/apps and the NFS server/appliance. Also, in the Bosh Director under the "Director Config," make sure the "NTP Servers" are defined.