Please help solve the problem with BTC Daemon.

[IMBA-Exchange]

Hello, everyone!

If someone can help, I will be very grateful!

Here's the problem: BTC daemon doesn't run stable.

------------------------------------------------------------------------------------------------------------------------------
We have a bitcoind installation into a VPS (60GB RAM, CPU:10cores, 1600 GB SSD) running on Ubuntu 16.04.6 with this configuration

server=1
rpcport=11111
rpcallowip=1.1.1.1
rpcuser=user
rpcpassword=pwd
walletnotify=/btctxs.sh %s
enableaccounts=1
txindex=1
minconf=1
dbcache=600

#onlynet=ipv4/ipv6
#prune=<N>

We are using jsonRpcClient-PHP to connect with the daemon and sending commands to it for transaction and others.
But after some time when the daemon is running, it is not responding to the RPC and not even no response from the CLI

The time is uncertain, sometimes it hangs after 5 minutes and sometimes it is after 2hrs.
Also, the log shows nothing unusual I think.
We have to kill the process and restart the daemon again, and when the daemon is killed and restarted, the balance is down to 0.00 and then after sometimes it is showing balance again, not the full balance but each transactions' amount showed up one after another, as the list transactions is showing confirmation:0 for all latest txs, but those will sum up in total after sometimes if we are lucky enough and the daemon is still running not hanged.

So anyone please advise us, what might be the problem? and how to solve that?

Some of the log entries when the daemon hanged already

[default wallet] keypool reserve 2290
[default wallet] keypool keep 2290
socket send error Broken pipe (32)
[default wallet] keypool added 1 keys (0 internal), size=2000 (1000 internal)
socket recv error Connection reset by peer (104)
------------------------------------------------------------------------------------------------------------------------------

Thanks in advance to all who will respond!

[djhomeschool]

Just a quick guess but could you disable the firewall for a few minutes and try again?

to disable the firewall

sudo ufw disable

to enable it again

sudo ufw enable

[IMBA-Exchange]

Just a quick guess but could you disable the firewall for a few minutes and try again?

to disable the firewall

sudo ufw disable

to enable it again

sudo ufw enable

Hello, dear djhomeschool!
Thank you for your answer.
We will try to do it now and I will tell you the answer.

[HCP]

Also, the log shows nothing unusual I think.

Rather than picking and choosing selected output from your log file, you'd be better served just copy/pasting the last few hundred lines after it has stopped responding to pastebin.com and then posting a link to the URL that pastebin generates.

That way folks will be able to better help diagnose the error.

[djhomeschool]

Since OP is not answering anymore i'm guessing the firewall blocked the open ports causing the deamon to become unresponsive

[BigDealCompany]

Not it was not the firewall

here is the log >> https://pastebin.com/J32B8wdA

All long line breaks are those point where the daemon is hanged and we restarted
Eg >> Line :169

[djhomeschool]

Not it was not the firewall

here is the log >> https://pastebin.com/J32B8wdA

All long line breaks are those point where the daemon is hanged and we restarted
Eg >> Line :169

hhmmmm.... some I/O error then?

[BigDealCompany]

we have installed the daemon in two different server(both ubuntu 16.04), all are having the same issue
And I/O error, what might that be ?

[djhomeschool]

we have installed the daemon in two different server(both ubuntu 16.04), all are having the same issue
And I/O error, what might that be ?

I/O error can come from HD problems but since you installed it in 2 different servers that is not the case here.

[HCP]

We have a bitcoind installation into a VPS (60GB RAM, CPU:10cores, 1600 GB SSD) running on Ubuntu 16.04.6 with this configuration

Possibly some weird VPS configuration causing your issues...

The first couple of hangs in your log appear somewhat random, the last few all seem to occur right after a "broken pipe" error. As you're running this on a VPS and not your own hardware, it might be tricky to try and track this problem down.

Have you contacted the tech support for your VPS provider? Perhaps they will be able to shed some light on why your VPS is having this issue with bitcoind...

[turndealer]

Not it was not the firewall

here is the log >> https://pastebin.com/J32B8wdA

All long line breaks are those point where the daemon is hanged and we restarted
Eg >> Line :169

Mate here you are exposing your node details, IP, Port are clearly visible and shows its open for 0.0.0.0.

I suggest you remove the last link.

Thanks

[bob123]

Mate here you are exposing your node details, IP, Port are clearly visible and shows its open for 0.0.0.0.

I suggest you remove the last link.

So what ?

An IP address is public information. If anyone wants to communicate with you, he needs your IP address.
This includes all other nodes you are connected to, all websites you visit, your email provider/server and all other online services you are using.

Giving out an IP is not a problem at all.. at least not if you aren't doing shady business.


And the port is the standard port for the bitcoin protocol. It is set in the specification. Every BTC node listens on port 8333. That's part of the protocol specification.