vSAN daemon Liveness alert due to EPD service failure.
search cancel

vSAN daemon Liveness alert due to EPD service failure.

book

Article ID: 371897

calendar_today

Updated On:

Products

VMware vSAN 8.x VMware vSphere ESXi 8.0

Issue/Introduction

This article provides troubleshooting steps to get the EPD service running if it will not start.

Symptoms:

  • EPD (Entry Persistence Daemon) is a user space daemon that runs on every host that is part of the vSAN cluster. The main job of EPD is to make sure there is no component leakage when objects are deleted.
  • Skyline Health reports error: vSAN daemon liveness.
  • EPD service is not running
  • Screenshot of error reflected under "Skyline Health" for "EPD Status"

       

  • When you manually try to start the "EPD" service you will get below error:

    [root@hostname:~] /etc/init.d/epd restart
    epd is not running
    INIT: EPD uses /scratch to store the db file.
    INIT: EPD using Security domain:  ID:
    epd started

    [root@hostname:~] /etc/init.d/epd status
    epd is not running

  • The epd.log may show the following errors

     YYYY-MM-DDTHH:MM:SS.###Z No(13) epd[2106465]: EntryDB_EnableCksumExtension: Failed to run VACUUM : database disk image is malformed (11) failedAt:1919
     YYYY-MM-DDTHH:MM:SS.###Z No(13) epd[2106465]: EntryDB_Open: Failed to enable libcksumvfs db '/scratch/epd-storeV2.db': database disk image is malformed (195887105)
     YYYY-MM-DDTHH:MM:SS.###Z No(13) epd[2106465]: EPDStoreOpen: Failed to open db (/scratch/epd-storeV2.db): Failure

Environment

VMware vSphere ESXi 8.0

VMware vSAN 8.x

Cause

Scratch partition issues cause the EPD service to fail. The EPD service writes to an epd-storeV2.db file on /scratch.

If /scratch is not available the EPD service cannot start. 

Resolution

We can copy the current database file to a new one and delete the old one. Then restart the epd.

(1) Stop epd service
/etc/init.d/epd stop

(2) Verify epd is stopped
 /etc/init.d/epd status

(3) Copy existing epd database
cp /scratch/epd-storeV2.db /scratch/epd-storeV2-copy.db

(4) Delete existing epd database
rm -f /scratch/epd-storeV2.db

(5) Restart the epd service and verify the status
/etc/init.d/epd start
/etc/init.d/epd status

Additional Information

Powered by Wolken Software