# Socks5() general failure - bitcoin sync hangs up

**URL:** <https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735>\
**Category:** Support and Troubleshooting\
**Created:** [May 8, 2021, 7:03pm UTC](https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735 "2021-05-08T19:03:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahaspharos](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@ahaspharos](https://community.umbrel.com/u/ahaspharos)\
**Post date:** [May 8, 2021, 7:03pm UTC](https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735/1 "2021-05-08T19:03:41Z")

</div>

Hi @all !

I have a strange issue.

Every round about 8h my node hang up while syncing.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/1X/52aa86a3c467a0c9fd5efeaf451cf5eb098f033f.jpeg)

At this point, only restarting (whats takes more time than usual in this case) get’s the node back working.

I run Umbrel 0.3.10 on Ubuntu 20.04.2 LTS … does maybe my tor hang up, so that bitcoin lose its connection?

Thank you for every response

---

<div class="post-metadata">

**Author:** ![DarthCoin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/darthcoin/32/1628_2.png) [@DarthCoin](https://community.umbrel.com/u/DarthCoin)\
**Post date:** [May 8, 2021, 8:21pm UTC](https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735/2 "2021-05-08T20:21:22Z")

</div>

Few days ago I also had my node (on Debian) making funny things because of Tor. But the logs in bitcoind was OK.

Run `docker-compose logs tor` to see something funny in Tor.

Also if you edit your lnd.conf file, be sure it was edited OK, sometimes spaces can messup.  
Don’t restart immediately, wait a bit longer. Sometimes gets it.  
Patience is a the key for a node operator.

---

<div class="post-metadata">

**Author:** ![ahaspharos](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@ahaspharos](https://community.umbrel.com/u/ahaspharos)\
**Post date:** [May 8, 2021, 10:39pm UTC](https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735/3 "2021-05-08T22:39:15Z")

</div>

Is this normal LND behaviour?

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/1X/9f1cc9e902a76094521e1541d30539c48d95ddd1.png)

the Node was stuck for 8h and more when the socks5 issue came up.

i reinstalled docker-ce now, in doubt that it worked properly

---

<div class="post-metadata">

**Author:** ![ahaspharos](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@ahaspharos](https://community.umbrel.com/u/ahaspharos)\
**Post date:** [May 10, 2021, 7:35am UTC](https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735/4 "2021-05-10T07:35:15Z")

</div>

![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/1X/ef63b761a3157b4a1b49314ae471301448a1b0b3.png)  
happened again. meanwhile i reinstalled docker-ce. thought that it fixed it.

but now it’s stuck again. the webUi doesn’t get any informations too, but the login process works

---

<div class="post-metadata">

**Author:** ![ahaspharos](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@ahaspharos](https://community.umbrel.com/u/ahaspharos)\
**Post date:** [May 10, 2021, 7:35am UTC](https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735/5 "2021-05-10T07:35:52Z")

</div>

![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/1X/cb5f2be94ffe66b07976541b6e9cbe2e97dfaf20.png)

---

<div class="post-metadata">

**Author:** ![ahaspharos](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@ahaspharos](https://community.umbrel.com/u/ahaspharos)\
**Post date:** [May 12, 2021, 8:41am UTC](https://community.umbrel.com/t/socks5-general-failure-bitcoin-sync-hangs-up/735/6 "2021-05-12T08:41:27Z")

</div>

SOLUTION:

It was a memory issue. 4gb RAM where running full, and the existing swap file was located on an HDD.

Reaching the RAM limit resulted in heavy I/O Rates and slowed down the whole system , until sudden death.

deactivating swap resulted in a new level of performance.

now with a swap file located on an different ssd, the whole system runs stable and fast.
