qT87DSMX9oW3Nuibod23

I experienced exactly the same issue. My description (I created duplicate issue, closed now): In default setting, ElectrumX is spamming messages like this to INFO output level: ``` INFO:ElectrumX:[1195011] changing...

Any update on this? Does anyone know how to comment-out this spam messages, in source files? I'd like to fix it, I am not a developer, unfortunately. Thanks.

Thanks for your reply. I am a bit confused, this is spesmilo electrumX issue, but you linked file in kyuupichan electrumX?

Thank you. I found pip package aiorpcX installed in my system and I located session.py file successfully. However, other INFO messages (below), are not in that file. I checked all...

Another crash today after 12 days uptime. Dmesg: `[Mon Sep 28 11:46:31 2020] electrumx_serve[2953515]: segfault at 20008 ip 000000000050fc10 sp 00007ffda68f3138 error 4 in python3.7[421000+232000] [Mon Sep 28 11:46:31 2020]...

Another crash today after less than 24h uptime. This time I attached python electrumx_server process to gdb debugger. Output: ``` (gdb) continue Continuing. Thread 1 "electrumx_serve" received signal SIGSEGV, Segmentation...

And another one: ``` [Wed Sep 30 02:52:33 2020] electrumx_serve[2406972]: segfault at 2c ip 0000000000541c7c sp 00007ffe29395cc0 error 4 in python3.7[421000+232000] [Wed Sep 30 02:52:33 2020] Code: 8b 0d 18...

Another one after 7 days uptime: `[Wed Oct 7 07:17:59 2020] electrumx_serve[3848664]: segfault at 0 ip 0000000000000000 sp 00007ffd540d52c8 error 14 in python3.7[400000+21000]` Bitcoind uptime 32 days.

> I managed to resolve my crashing on the 4GB Raspberry Pi by setting CACHE_MB = 500, deleting the data and starting over from scratch. I have experienced zero crashes...

I am not sure how I can check that. Both bitcoind and electrumX have been started 7 days ago. Bitcoind continues to operate, its uptime is 7d 19h, it works...