Understanding "failed to stat file var/lib/vmware/configstore/backup/current-store-1" warning message

Products

• VMware vSphere ESXi

Issue/Introduction

The following warnings are observed in the ESXi syslog.log file:
YYYY-MM-DDTHH:MM:SS.YYYZ In(14) Jumper2[XXXXX]: extracting from file /local.tgz
YYYY-MM-DDTHH:MM:SS.YYYZ Wa(12) Jumper2[XXXXX]: failed to stat file var/lib/vmware/configstore/backup/current-store-1
YYYY-MM-DDTHH:MM:SS.YYYZ Wa(12) Jumper2[XXXXX]: failed to stat file var/lib/vmware/configstore/backup/datafile-store

Environment

VMware vSphere ESXi 8.x

Cause

Jumper2 is one of the processes executed during ESXi boot, which initializes and validates the configuration state. During this process, it performs a stat system call on specific target files on the boot disk; if this call fails, the warning is triggered.

These two files located under /var/lib/vmware/configstore/backup are dynamically created by the backup.sh script. However, at the time Jumper2 executes during the early boot sequence, these files have not yet been generated. This absence is the root cause of the stat failure. As the boot sequence progresses further and executes backup.sh, these files are successfully created.

Resolution

These warning logs have no adverse impact on system operations, performance, or data protection. Therefore, they can be safely ignored.