-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOError: BrokenPipeError(32, 'Broken pipe') #102
Comments
sorry, I tried to make formatting nice. After 3rd attempt I give up. |
Add Also go to the Qt console and write Also have a look in the debug log (the filename of it is printed out near the beginning of Electrum Personal Server's output, in raspberry pi it should be |
Hi Chris, Debug log from
|
Thanks for posting. I unfortunately don't know the cause. I'll try to think about it a bit more over the next few days. |
Same setup with raspiblitz. I can confirm the same, the txs are visible but unconfirmed The icon is green and is not disconnecting |
_histogram", "id": 116} |
This sounds like a different error. Do the transactions become confirmed if you restart EPS? |
I haven’t tried that. Do I restart raspi or just restart the server? What’s the script I should use to restart server without restarting raspi if that’s the case? |
Just restart Electrum Personal Server. I don't know how the raspblitz setup is, but if EPS is running in in its own screen terminal then you can do ctrl+c and then start it again. If its using systemd then you do a restart commend for that service (I don't know what that is, it should be on the web somewhere). |
I just realized: in case you're talking about the raspbolt setup (which is linked from this project's README) instead of raspblitz you should be able to restart EPS with |
Yes raspiblitz is basically autorun installation version of raspibolt so this command line should work. Will try and keep you posted. Thanks |
I re-edited my config to match multi sig wallet as per instructions to see if it will resolve unconfirmed transactions. Now the log is stuck at mempool histogram and wallet is in synchronization stage forever and no transactions showing up |
Finally got it working. The key is waiting it out. Eventually it synced showed the balance but still may be optimized or just not suitable for raspi as it’s slow and making raspi slow and it drops connection after some time needing restart |
Are you saying the problem was because you configured multisig incorrectly? That mempool problem is issue #96, there will be an option to disable the mempool histogram in the next release because with today's large mempools it causes slow response times on raspberry pis. You could try running from master branch if you don't want to wait until the release. |
Yes. It appears that the problem was related to configuring my multi signature wallet incorrectly in the config file. I edited it and restarted server and now it’s working like a charm. The mempool problem has also resolved I just waited out. Takes little more time to synchronize but that’s expected with small machine like raspi. I have tried new transactions too which are showing instantly. So far so great. I will keep you posted with any new issues. |
How exactly did you configure the multisig wallet incorrectly? Maybe there's a way it can be made clearer. |
I am using a 2/3 multi signature wallet so initially I put ‘3’ instead of ‘2’ and then three pubkeys in the multi signature wallet section of config file. I believe this was reason for my transactions showing as unconfirmed. Once corrected it, the wallet synced and showed by confirmed balance. |
Hello Chris,
Have installed EPS on my raspberry pi 2.
Running bitcoin full node with following config.
daemon=1 txindex=1 upnp=1 logips=1 maxconnections=40 maxuploadtarget=5000 dbcache=100 maxorphantx=10 maxmempool=50 proxy=127.0.0.1:9050 listen=1 bind=127.0.0.1 onlynet=onion server=1 rpcauth=bitcoin:random_string rpcauth=lightning:random_string rpcallowip=193.168.1.0/24 zmqpubrawblock=tcp://127.0.0.1:18501 zmqpubrawtx=tcp://127.0.0.1:18502
EPS config pretty much standard setting you have apart from my own watch address.
I connect to raspberry pi by creating ssh tunnel from my guest
ssh [email protected] -L 50002:localhost:50002
Then fire up electrum via command line
electrum --oneserver --server localhost:50002:s
In my EPS log I see
ERROR:2019-04-13 15:06:11,376: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:06:11,644: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:06:12,645: IOError: OSError(0, 'Error') INFO:2019-04-13 15:06:19,695: Electrum connected from ('127.0.0.1', 33446) ERROR:2019-04-13 15:06:55,674: IOError: BrokenPipeError(32, 'Broken pipe') ERROR:2019-04-13 15:06:55,947: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:06:56,215: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:06:57,366: IOError: OSError(0, 'Error') INFO:2019-04-13 15:07:00,242: Electrum connected from ('127.0.0.1', 33482) ERROR:2019-04-13 15:07:33,309: IOError: BrokenPipeError(32, 'Broken pipe') ERROR:2019-04-13 15:07:33,578: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:07:33,848: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:07:34,117: IOError: OSError(0, 'Error') INFO:2019-04-13 15:07:40,707: Electrum connected from ('127.0.0.1', 33518) ERROR:2019-04-13 15:08:14,234: IOError: BrokenPipeError(32, 'Broken pipe') ERROR:2019-04-13 15:08:14,504: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:08:14,772: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:08:18,644: IOError: OSError(0, 'Error') INFO:2019-04-13 15:08:21,259: Electrum connected from ('127.0.0.1', 33554) ERROR:2019-04-13 15:08:56,525: IOError: BrokenPipeError(32, 'Broken pipe') ERROR:2019-04-13 15:08:56,796: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:08:57,064: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:08:58,964: IOError: OSError(0, 'Error') INFO:2019-04-13 15:09:01,801: Electrum connected from ('127.0.0.1', 33590) ERROR:2019-04-13 15:09:36,450: IOError: BrokenPipeError(32, 'Broken pipe') ERROR:2019-04-13 15:09:36,719: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:09:36,987: IOError: OSError(0, 'Error') ERROR:2019-04-13 15:09:39,606: IOError: OSError(0, 'Error') INFO:2019-04-13 15:09:42,377: Electrum connected from ('127.0.0.1', 33626)
Electrum client connection status shows green for a second then is red for a a while then connects then disconnects.
I have sent btc to the wallet, but it doesn't seem to see (un)confirmed TXs
Can you help further?
The text was updated successfully, but these errors were encountered: