Casper 2.0 Upgrade: Sidecar Service Fails to Connect to Node on Testnet (Continuous Restarts)

Ecosystem Support Node Support
1

1. Issue Summary

  • Title of the Issue: Casper Sidecar Fails to Connect to Node (Testnet TTL Node)
  • Description: The casper-sidecar service restarts continuously due to connection timeouts to the Casper node on 127.0.0.1:7779. The node is a Testnet TTL node (v1.5.8), and UFW is disabled. The sidecar fails with Error initializing component 'rpc_api_server'.

2. Node Information

  • Node Type: TTL Node (Testnet)
  • Casper Node Version: 1.5.8
  • Network: Testnet

3. Error Details

  • Logs and Error Messages:

Mar 17 08:56:54 Ubuntu-2004-focal-64-minimal systemd[1]: Started Casper Sidecar.
Mar 17 08:56:54 Ubuntu-2004-focal-64-minimal casper-sidecar[1035633]: 2025-03-17T07:56:54.650107Z WARN casper_rpc_sidecar::node_client: failed to connect to node 127.0.0.1:7779, waiting 1000ms before retryi>
Mar 17 08:56:55 Ubuntu-2004-focal-64-minimal casper-sidecar[1035633]: 2025-03-17T07:56:55.651517Z WARN casper_rpc_sidecar::node_client: failed to connect to node 127.0.0.1:7779, waiting 2000ms before retryi>
Mar 17 08:56:57 Ubuntu-2004-focal-64-minimal casper-sidecar[1035633]: 2025-03-17T07:56:57.652881Z WARN casper_rpc_sidecar::node_client: failed to connect to node 127.0.0.1:7779, waiting 4000ms before retryi>
Mar 17 08:57:01 Ubuntu-2004-focal-64-minimal casper-sidecar[1035633]: 2025-03-17T07:57:01.654173Z WARN casper_rpc_sidecar::node_client: failed to connect to node 127.0.0.1:7779, waiting 8000ms before retryi>
Mar 17 08:57:09 Ubuntu-2004-focal-64-minimal casper-sidecar[1035633]: 2025-03-17T07:57:09.655720Z WARN casper_rpc_sidecar::node_client: failed to connect to node 127.0.0.1:7779, waiting 16000ms before retry>
Mar 17 08:57:24 Ubuntu-2004-focal-64-minimal casper-sidecar[1035633]: 2025-03-17T07:57:24.650402Z ERROR casper_sidecar::run: The server has exited with an error: Error initializing component ‘rpc_api_server’>
Mar 17 08:57:24 Ubuntu-2004-focal-64-minimal casper-sidecar[1035633]: Error: Error initializing component ‘rpc_api_server’: Failed to start component rpc_api_server in 30 [s]
Mar 17 08:57:24 Ubuntu-2004-focal-64-minimal systemd[1]: casper-sidecar.service: Main process exited, code=exited, status=1/FAILURE
Mar 17 08:57:24 Ubuntu-2004-focal-64-minimal systemd[1]: casper-sidecar.service: Failed with result ‘exit-code’.
Mar 17 08:57:25 Ubuntu-2004-focal-64-minimal systemd[1]: casper-sidecar.service: Scheduled restart job, restart counter is at 626.
Mar 17 08:57:25 Ubuntu-2004-focal-64-minimal systemd[1]: Stopped Casper Sidecar.
Mar 17 08:57:25 Ubuntu-2004-focal-64-minimal systemd[1]: Started Casper Sidecar.

1 Like
2

That is normal for the testnet and mainnet at the moment since the sidecar will be running normally only when Casper-2.0 is upgraded.

Currently the casper-sidecar’s log should show

Mar 17 09:59:31 ca casper-sidecar[79474]: 2025-03-17T09:59:31.833406Z  WARN casper_rpc_sidecar::node_client: failed to connect to node 127.0.0.1:7779, waiting 2000ms before retrying; err=Connection refused (os error 111)

since the the binary port 7779 is for Casper-2.0 only.
Once the testnet/mainnet is upgraded to Casper-2.0 the sidecar should be working.

1 Like
3

Ok.
Thanks for the clarification.

3 Likes