Samourai broken after upgrade bitcoin core to 28.0

JB123 · November 3, 2024, 10:26pm

samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_tor_1 samourai-server_node_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_node_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_tor_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_db_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 samourai-server_node_1 | 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:47Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:47Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:47Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:48Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| Nov 03 20:40:43.581 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.
| Nov 03 20:40:43.581 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
| Nov 03 20:40:43.582 [notice] Read configuration file “/etc/tor/torrc”.
| Nov 03 20:40:43.795 [notice] Opening Socks listener on 127.0.0.1:9050
| Nov 03 20:40:43.795 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
| Nov 03 20:40:43.000 [notice] Bootstrapped 0% (starting): Starting
| Nov 03 20:40:43.000 [notice] Starting with guard context “default”
| Nov 03 20:40:44.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
| Nov 03 20:40:50.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
| Nov 03 20:40:50.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
| Nov 03 20:40:51.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
| Nov 03 20:40:51.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
| Nov 03 20:40:51.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
| Nov 03 20:40:51.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
| Nov 03 20:40:51.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
| Nov 03 20:40:51.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
| 2024-11-03T22:15:48Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:48Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| Nov 03 20:40:52.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| Nov 03 20:40:52.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
| Nov 03 20:40:52.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/8127, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
| Nov 03 20:40:52.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
| Nov 03 20:40:54.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
| 2024-11-03T22:15:48Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| Nov 03 20:40:56.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
| Nov 03 20:40:56.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors
| Nov 03 20:40:57.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors
| Nov 03 20:40:57.000 [notice] Bootstrapped 72% (loading_descriptors): Loading relay descriptors
| Nov 03 20:40:57.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
| Nov 03 20:40:58.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
| Nov 03 20:40:58.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
| Nov 03 20:40:58.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
| Nov 03 20:40:58.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
| Nov 03 20:40:58.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
| Nov 03 20:40:59.000 [notice] Bootstrapped 100% (done): Done
| 2024-11-03 20:40:42+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.7.1+maria~focal started.
| 2024-11-03 20:40:45 0 [Note] mariadbd (server 10.7.1-MariaDB-1:10.7.1+maria~focal) starting as process 7 …
| 2024-11-03 20:40:45 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
| 2024-11-03 20:40:45 0 [Note] InnoDB: Number of transaction pools: 1
| 2024-11-03 20:40:45 0 [Note] InnoDB: Using ARMv8 crc32 instructions
| 2024-11-03 20:40:45 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
| 2024-11-03 20:40:45 0 [Note] InnoDB: Using Linux native AIO
| 2024-11-03 20:40:45 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 16777216
| 2024-11-03 20:40:45 0 [Note] InnoDB: Completed initialization of buffer pool
| 2024-11-03 20:40:46 0 [Note] InnoDB: 128 rollback segments are active.
| 2024-11-03 20:40:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
| 2024-11-03 20:40:46 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
| 2024-11-03 20:40:46 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.
| 2024-11-03 20:40:46 0 [Note] InnoDB: 10.7.1 started; log sequence number 87260; transaction id 52
| 2024-11-03 20:40:46 0 [Note] Plugin ‘FEEDBACK’ is disabled.
| 2024-11-03 20:40:46 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
| 2024-11-03 20:40:46 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
| 2024-11-03 20:40:46 0 [Note] Server socket created on IP: ‘0.0.0.0’.
| 2024-11-03 20:40:46 0 [Note] Server socket created on IP: ‘::’.
| 2024-11-03 20:40:46 0 [Warning] ‘proxies_priv’ entry ‘@% root@92183c3cdc68’ ignored in --skip-name-resolve mode.
| 2024-11-03 20:40:46 0 [Note] InnoDB: Buffer pool(s) load completed at 241103 20:40:46
| 2024-11-03 20:40:46 0 [Note] mariadbd: ready for connections.
| Version: ‘10.7.1-MariaDB-1:10.7.1+maria~focal’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
| 2024-11-03 20:40:47 3 [Warning] Aborted connection 3 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.25’ (This connection closed normally without authentication)
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:48Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:48Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }
| 2024-11-03T22:15:48Z ERROR Bitcoind RPC : LatestBlock.onBlockHash()
| { code: -32600, message: ‘jsonrpc field must be a string’ }

enkumber · November 5, 2024, 3:27am

Mine broke too!

enkumber · November 6, 2024, 8:21am

guys, still nothing?

denny · November 6, 2024, 9:15am

@nmfretz Can you take a look at that? Obviously the JSON-RPC field must also be set correctly here ("jsonrpc": "2.0").

Same as here:

enkumber · November 7, 2024, 3:01pm

Up

denny · November 9, 2024, 8:01am

I’ve opened a GitHub issue for this:

github.com/getumbrel/umbrel-apps

[Samourai Server] - JSON-RPC Error: jsonrpc field must be a string

opened 08:01AM - 09 Nov 24 UTC

dennysubke

**Description:** I am encountering a recurring error with Samourai Server wh…en it attempts to interact with Bitcoin Core. The error log shows the following message repeatedly: ``` 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash() { code: -32600, message: 'jsonrpc field must be a string' } ``` See also here: https://community.umbrel.com/t/samourai-broken-after-upgrade-bitcoin-core-to-28-0/19811 ## **Steps to Reproduce:** Start Samourai Server and Bitcoin Core. Observe the error messages in the Samourai Server logs. ## **Expected Behavior:** Samourai Server should interact with Bitcoin Core without JSON-RPC field errors. ## **Actual Behavior:** The server logs an error indicating that the `jsonrpc` field must be a string, preventing normal operation. ## **Troubleshooting Attempts:** - Checked configuration files for JSON-RPC formatting issues. - Ensured jsonrpc field is set to "2.0" in any relevant configurations. - Restarted both Samourai Server and Bitcoin Core. ## **Additional Information:** This error may indicate an incompatibility between the versions of Samourai Server and Bitcoin Core, or a possible configuration issue with JSON-RPC fields.

enkumber · November 9, 2024, 9:33am

thank you Denny

enkumber · November 12, 2024, 12:19pm

seems like this app is dead. almost 10 days since it’s broken and looks like noone will fix it too bad, I loved umbrel

enkumber · November 12, 2024, 12:20pm

@nmfretz can you tell us if there’s any chance this will be fixed? thank you!

enkumber · November 15, 2024, 11:58am

no response @nmfretz . great, thanks!

denny · November 15, 2024, 9:57pm

I think we should be patient. I will bring this up again in the next few days.

enkumber · November 16, 2024, 6:53am

ok, thanks

denny · November 16, 2024, 8:52pm

You’re welcome!

denny · November 19, 2024, 3:45pm

github.com/getumbrel/umbrel-apps

[Samourai Server] - JSON-RPC Error: jsonrpc field must be a string

opened 08:01AM - 09 Nov 24 UTC

dennysubke

**Description:** I am encountering a recurring error with Samourai Server wh…en it attempts to interact with Bitcoin Core. The error log shows the following message repeatedly: ``` 2024-11-03T22:15:46Z ERROR Bitcoind RPC : LatestBlock.onBlockHash() { code: -32600, message: 'jsonrpc field must be a string' } ``` See also here: https://community.umbrel.com/t/samourai-broken-after-upgrade-bitcoin-core-to-28-0/19811 ## **Steps to Reproduce:** Start Samourai Server and Bitcoin Core. Observe the error messages in the Samourai Server logs. ## **Expected Behavior:** Samourai Server should interact with Bitcoin Core without JSON-RPC field errors. ## **Actual Behavior:** The server logs an error indicating that the `jsonrpc` field must be a string, preventing normal operation. ## **Troubleshooting Attempts:** - Checked configuration files for JSON-RPC formatting issues. - Ensured jsonrpc field is set to "2.0" in any relevant configurations. - Restarted both Samourai Server and Bitcoin Core. ## **Additional Information:** This error may indicate an incompatibility between the versions of Samourai Server and Bitcoin Core, or a possible configuration issue with JSON-RPC fields.

enkumber · November 24, 2024, 2:04pm

I’m still waiting, three weeks passed. No answer.

btnksud4 · November 29, 2024, 11:14pm

@nmfretz just bumping this issue…

Any way to revert to an older version of Bitcoin Core to fix this?

denny · December 1, 2024, 7:40pm

Just to bring the topic back up!

Topic		Replies	Views
Samourai Server stuck since 0.4.1 upgrade Support and Troubleshooting	12	1296	September 15, 2021
Samourai server hotfix 2 Support and Troubleshooting	5	364	February 20, 2023
Public pool no longer works since Bitcoin core 28.0 Support and Troubleshooting	10	134	October 31, 2024
Samourai Server not seeing transactions Support and Troubleshooting	0	54	June 5, 2024
Samourai server qr code not working, cant connect Support and Troubleshooting	0	261	February 1, 2023

Samourai broken after upgrade bitcoin core to 28.0

Related topics