# Problem after make an apt update &&apt upgrade. Storagenode always restart

**URL:** <https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104>\
**Category:** troubleshooting\
**Created:** [December 9, 2019, 10:54pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104 "2019-12-09T22:54:24Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 9, 2019, 10:54pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/1 "2019-12-09T22:54:24Z")

</div>

Since I’ve done that my storagenode is always restating:  
docker ps -a  
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
4b0e483471e1 storjlabs/watchtower “/watchtower storage…” 6 minutes ago Up 6 minutes watchtower  
85afd0276f6d storjlabs/storagenode:alpha “/entrypoint” 26 minutes ago Restarting (1) 43 seconds ago storagenode

How I can solve that?  
Triyed to stop and start the storagenode. I’ve delete it and create it again but problem is the same

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 9, 2019, 10:59pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/2 "2019-12-09T22:59:09Z")

</div>

You should change the start up storjlabs/storagenode:alpha to storjlabs/storagenode:beta

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 9, 2019, 11:00pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/3 "2019-12-09T23:00:31Z")

</div>

logs here:  
I’ve that in logs:

2019-12-09T22:42:36.359106069Z 2019-12-09T22:42:36.358Z INFO Configuration loaded from: /app/config/config.yaml  
2019-12-09T22:42:36.379618967Z 2019-12-09T22:42:36.379Z INFO Operator email: m  
2019-12-09T22:42:36.379762532Z 2019-12-09T22:42:36.379Z INFO operator wallet:  
2019-12-09T22:42:37.384926590Z 2019-12-09T22:42:37.384Z FATAL Unrecoverable error {“error”: “Error creating revocation database: revocation database error: boltdb error: timeout\n\tstorjDOTio/storj/storage/boltdb.New:43\n\tstorjDOTio/storj/pkg/revocation.newDBBolt:50\n\tstorjDOTio/storj/pkg/revocation.NewDB:33\n\tstorjDOTio/storj/pkg/revocation.NewDBFromCfg:21\n\tmain.cmdRun:162\n\tstorjDOTio/storj/pkg/process.cleanup.func1.2:278\n\tstorjDOTio/storj/pkg/process.cleanup.func1:296\n\tgithubDOTcom/spf13/cobra.(\*Command).execute:826\n\tgithubDOTcom/spf13/cobra.(\*Command).ExecuteC:914\n\tgithubDOTcom/spf13/cobra.(\*Command).Execute:864\n\tstorjDOTio/storj/pkg/process.Exec:74\n\tmain.main:315\n\truntime.main:203”, “errorVerbose”: “Error creating revocation database: revocation database error: boltdb error: timeout\n\tstorjDOTio/storj/storage/boltdb.New:43\n\tstorjDOTio/storj/pkg/revocation.newDBBolt:50\n\tstorjDOTio/storj/pkg/revocation.NewDB:33\n\tstorjDOTio/storj/pkg/revocation.NewDBFromCfg:21\n\tmain.cmdRun:162\n\tstorjDOTio/storj/pkg/process.cleanup.func1.2:278\n\tstorjDOTio/storj/pkg/process.cleanup.func1:296\n\tgithubDOTcom/spf13/cobra.(\*Command).execute:826\n\tgithubDOTcom/spf13/cobra.(\*Command).ExecuteC:914\n\tgithubDOTcom/spf13/cobra.(\*Command).Execute:864\n\tstorjDOTio/storj/pkg/process.Exec:74\n\tmain.main:315\n\truntime.main:203\n\tmain.cmdRun:164\n\tstorjDOTio/storj/pkg/process.cleanup.func1.2:278\n\tstorjDOTio/storj/pkg/process.cleanup.func1:296\n\tgithubDOTcom/spf13/cobra.(\*Command).execute:826\n\tgithubDOTcom/spf13/cobra.(\*Command).ExecuteC:914\n\tgithubDOTcom/spf13/cobra.(\*Command).Execute:864\n\tstorjDOTio/storj/pkg/process.Exec:74\n\tmain.main:315\n\truntime.main:203”}

replace DOT by .

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 9, 2019, 11:02pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/4 "2019-12-09T23:02:27Z")

</div>

You should try removing the contrainer from docker and try starting a new one. Also what hardware is this running on because I had issues with arm processers after I updated kernals.

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 9, 2019, 11:03pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/5 "2019-12-09T23:03:20Z")

</div>

Same with beta:  
docker ps -a  
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
b065047f0645 storjlabs/storagenode:beta “/entrypoint” 44 seconds ago Restarting (1) 11 seconds ago storagenode  
4b0e483471e1 storjlabs/watchtower “/watchtower storage…” 18 minutes ago Up 18 minutes watchtower

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 9, 2019, 11:04pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/6 "2019-12-09T23:04:15Z")

</div>

Try removing watchtower and storagenode containters

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 9, 2019, 11:05pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/7 "2019-12-09T23:05:27Z")

</div>

My server:  
4.15.0-48-generic #51~16.04.1-Ubuntu SMP Fri Apr 5 12:01:12 UTC 2019 x86\_64 x86\_64 x86\_64 GNU/Linux

Make a docker rm storagenode and watchtower was already done

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 9, 2019, 11:05pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/8 "2019-12-09T23:05:55Z")

</div>

What does your command to start it look like?

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 9, 2019, 11:07pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/9 "2019-12-09T23:07:03Z")

</div>

```
docker run -d --restart unless-stopped -p 28967:28967 \
-e WALLET="0xc" \
-e EMAIL="@gmail.com" \
-e ADDRESS="@IP:28967" \
-e BANDWIDTH="50TB" \
-e STORAGE="0.5TB" \
--mount type=bind,source="/root/.local/share/storj/identity/storagenode",destination=/app/identity \
--mount type=bind,source="/root/storagenode",destination=/app/config \
--name storagenode storjlabs/storagenode:beta
```

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 9, 2019, 11:11pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/10 "2019-12-09T23:11:57Z")

</div>

Not 100% sure at the moment your startup command looks fine, The only issue I can really think of is ubuntu 16 updating is what caused the problem.

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 9, 2019, 11:13pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/11 "2019-12-09T23:13:49Z")

</div>

I think that too!  
I’m using the same start command as before. Problem appear after the upgade

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 9, 2019, 11:15pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/12 "2019-12-09T23:15:39Z")

</div>

I wish I had a better answer for you I run ubuntu 18.04, I havent updated since I started running my node in may the only experience I had was with a pi4 and it pretty much stopped working with docker all together after an update of the kernel.

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [December 10, 2019, 4:24am UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/13 "2019-12-10T04:24:29Z")

</div>

Hello @bundyboss,  
Welcome to the forum!  
Since you store the identity and data under the root home directory, you must use a `sudo` to run the docker container.

If you do not, then please re-apply permission for your user for the data folder recursively.

---

<div class="post-metadata">

**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\
**Post date:** [December 10, 2019, 4:28am UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/14 "2019-12-10T04:28:29Z")

</div>

Im assuming he had to start it in sudo or it would have said permission denied anyways, Least for me it does.

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [December 10, 2019, 4:39am UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/15 "2019-12-10T04:39:50Z")

</div>

> [@bundyboss](#):
>
> Error creating revocation database: revocation database error

The lack of permissions could be a reason. The other way is read-only filesystem or disk inconsistency.  
In the last case I would recommend to boot from other media and check the disk for errors.

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 10, 2019, 8:15am UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/16 "2019-12-10T08:15:40Z")

</div>

I start it with user root so it’s not a permission problem

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 10, 2019, 8:23am UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/17 "2019-12-10T08:23:37Z")

</div>

> [@Alexey](#):
>
> The lack of permissions could be a reason. The other way is read-only filesystem or disk inconsistency.  
> In the last case I would recommend to boot from other media and check the disk for errors.

I’m on a VPS server so can’t boot from other media. For exemple watchtower is working fine. Only Storage node is not working well

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 10, 2019, 12:54pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/18 "2019-12-10T12:54:10Z")

</div>

Any others idea? It was working well for 6 months. No dev to analyse the problem?

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [December 10, 2019, 1:21pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/19 "2019-12-10T13:21:33Z")

</div>

> [@bundyboss](#):
>
> Error creating revocation database

Have you tried checking HDD for errors as Alexey pointed out? It seems like a permission problem

---

<div class="post-metadata">

**Author:** ![bundyboss](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bundyboss/32/71_2.png) [@bundyboss](https://forum.storj.io/u/bundyboss)\
**Post date:** [December 10, 2019, 1:25pm UTC](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104/20 "2019-12-10T13:25:43Z")

</div>

> [@nerdatwork](#):
>
> Have you

Start as root. so it’s not a right problem!  
root@2:~/storagenode# ls -l  
total 176  
-rw-r–r-- 1 root root 715 May 6 2019 config.yaml  
-rw------- 1 root root 262144 Oct 3 21:19 kademlia  
-rw------- 1 root root 32768 Nov 20 19:16 revocations.db  
drwx------ 7 root root 4096 Nov 20 19:19 storage

[Next page](https://forum.storj.io/t/problem-after-make-an-apt-update-apt-upgrade-storagenode-always-restart/3104.md?page=2)