# Replicated shared snapshotter doesn't comes up on node restart **URL:** \ **Category:** Packaging an application\ **Created:** [August 21, 2020, 5:04pm UTC](https://community.replicated.com/t/replicated-shared-snapshotter-doesnt-comes-up-on-node-restart/443 "2020-08-21T17:04:33Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![MANI\_M](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mani_m/32/136_2.png) [@MANI\_M](https://community.replicated.com/u/MANI_M)\ **Post date:** [August 21, 2020, 5:04pm UTC](https://community.replicated.com/t/replicated-shared-snapshotter-doesnt-comes-up-on-node-restart/443/1 "2020-08-21T17:04:33Z")
Whenever the primary node is restarted replicated-shared-fs-snapshotter-\* doesn’t come up and goes into `Init:CrashLoopBackOff` we need to manually force delete the pod in order to fix it. Due to this the other pods which are dependent on the shared filesystem goes into `Init:CrashLoopBackOff` due to race condition as [mentioned in this](http://community.replicated.com/t/flexvolume-creates-deadlock-and-deployment-enters-into-crashloopbackoff-on-node-reboot/439). We are running on DigitalOcean 4vCPU 8GB machine. The cluster has one primary and 2 worker nodes. The issue is observed in a single primary node as well. We have a single primary node running on AWS. There it works out fine. How to solve this? Screen shot attached for reference. ![image](https://canada1.discourse-cdn.com/flex030/uploads/replicated/original/1X/8e89a49102a70793f63fed2894a226872696e0db.png) ---
**Author:** ![salahalsaleh](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/salahalsaleh/32/464_2.png) [@salahalsaleh](https://community.replicated.com/u/salahalsaleh)\ **Post date:** [August 21, 2020, 5:58pm UTC](https://community.replicated.com/t/replicated-shared-snapshotter-doesnt-comes-up-on-node-restart/443/2 "2020-08-21T17:58:00Z")
Hello, we are tracking this and we will fix it in the next release, which is due next month.