Closed tchjntr closed 5 months ago
Found out about #665 so I am currently reindexing my Bitcoin node before giving electrs a second try.
I've finished reindexing my Bitcoin node and now I am trying to start indexing electrs but every time I try to start the system unit it stops with the following error message:
electrs[852160]: Error: Failed to read configuration file /home/janitor/.electrs/electrs.conf: Permission denied (os error 13)
This is the system unit:
# systemd unit for electrs
# /etc/systemd/system/electrs.service
[Unit]
Description=Electrs
Wants=bitcoind.service
After=bitcoind.service
[Service]
ExecStart=/usr/local/bin/electrs --conf /home/janitor/.electrs/electrs.conf
# Process management
####################
Type=simple
TimeoutSec=300
KillMode=process
# Directory creation and permissions
####################################
RuntimeDirectory=electrs
RuntimeDirectoryMode=0710
User=janitor
Group=janitor
# Hardening Measures
####################
PrivateTmp=true
ProtectSystem=full
ProtectHome=true
PrivateDevices=true
MemoryDenyWriteExecute=true
[Install]
WantedBy=multi-user.target
And the permissions for the electrs.conf file are correct:
janitor@u59pro:~/.electrs$ ls -lah
total 12K
drwxr-xr-x 2 janitor janitor 4.0K May 29 15:41 .
drwx------ 19 janitor janitor 4.0K May 29 15:39 ..
-rw-r--r-- 1 janitor janitor 1.9K May 29 15:41 electrs.conf
probably caused by ProtectHome=true
probably caused by
ProtectHome=true
Thanks. It started indexing.
I'll report back if there's any issue with indexing blocks or after it's fully indexed.
electrs successfully synced after reindexing Bitcoin.
Describe the bug electrs stops as it fails to get Block 1 (00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048)
Electrs version v0.10.5
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect electrs to sync
Configuration
Environment variables: N/A Arguments:
--disable-electrum-rpc
System running electrs
Additional context This issue seems to be similar to #905 so I ran
bitcoin-cli getblock
to confirm that the block was actually on disk.