Troubleshooting OpenEBS - Jiva
General guidelines for troubleshooting#
- Contact OpenEBS Community for support.
- Search for similar issues added in this troubleshooting section.
- Search for any reported issues on StackOverflow under OpenEBS tag
Jiva replica pod logs showing meta file missing entry
Jiva replica pod logs showing "Failed to find metadata"#
Jiva target pod may not be syncing data across all replicas when replica pod logs contains below kind of messages:
Troubleshooting:
Perform following steps to restore the missing metadata file of internal snapshots.
Check all replica pods are in running state. Faulty replica pod will be in
crashloopBackoffstate in OpenEBS 1.0.0 version.Find the replica in
RWmode using mayactl command, consider it as healthy.Consider the replica that have above kind of error messages in its logs as faulty.
Log in to the nodes of healthy and faulty replica and list all the snapshots under
**/var/openebs/<PV-name>**.Example snippet of Healthy replica:
Example snippet of faulty replica:
From above snippet of faulty replica, metadata for the
volume-snap-b72764f0-4ca8-49b1-b9ca-57cb9dfb6fa9.imgsnapshot is not present.If only one meta file is missing, then copy meta file name and content from one of the healthy replica to the faulty replica.
For above case, copy
volume-snap-b72764f0-4ca8-49b1-b9ca-57cb9dfb6fa9.img.metafrom healthy replica to faulty replica and restart the faulty replica. You can verify the logs of the replica pod to ensure that there are no error messages as mentioned above.If multiple meta files are missing, then delete all files from replica pods and then restart the faulty replica pod to rebuild from healthy replica.