Hi @udalwadi, we’ve seen this happen when there’s an issue with the cryoSPARC database. I suggest cryosparcm fixdb command, which requires the latest cryoSPARC patch.
Follow these instructions to install the patch when cryoSPARC is not running: Node is not in primary or recovering state
Try that out and let me know how it goes.