Skip to main content
NetApp Knowledge Base

Trident does not properly initialize and shows the error "etcdserver: another etcd process is using "//var//etcd//data//member//snap//db" and holds the file lock, or loading backend file is taking >10 seconds"" to "Cloud/Astra/Trident/Trident does not properly initialize and show error

Views:
215
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident 19.10 (using etcd database)
  • RedHat OCP 3.11 

Issue

After a power outage which affected the kubernetes cluster, Trident does not properly initialize and gets stuck:

YYYY-MM-DD hh:mm:ss I | etcdmain: etcd Version: 3.3.13
YYYY-MM-DD hh:mm:ss I | etcdmain: Git SHA: XXXXXX
YYYY-MM-DD hh:mm:ss I | etcdmain: Go Version: go1.10.8
YYYY-MM-DD hh:mm:ss I | etcdmain: Go OS/Arch: linux/amd64
YYYY-MM-DD hh:mm:ss I | etcdmain: setting maximum number of CPUs to 32, total number of available CPUs is 32
YYYY-MM-DD hh:mm:ss W | etcdmain: found invalid file/dir backup under data dir /var/etcd/data (Ignore this if you are upgrading etcd)
YYYY-MM-DD hh:mm:ss N | etcdmain: the server is already initialized as member before, starting as etcd member...
YYYY-MM-DD hh:mm:ss I | embed: listening for peers on http://127.0.0.1:8002
YYYY-MM-DD hh:mm:ssI | embed: listening for client requests on 127.0.0.1:8001
YYYY-MM-DD hh:mm:ss W | etcdserver: another etcd process is using "/var/etcd/data/member/snap/db" and holds the file lock, or loading backend file is taking >10 seconds
YYYY-MM-DD hh:mm:ss W | etcdserver: waiting for it to exit before starting...

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.