Hallo zusammen,
ich betreibe nun schon eine Weile meinen Raspiblitz, habe aber immer wieder neue Probleme.
Der Raspi hat zuletzt einwandfrei funktioniert, keine Interaktion meinerseits. Plötzlich war remote keine Verbindung mehr möglich. Nach ca. 2 Wochen bin ich heute wieder zum Standort des Raspi gekommen. Bei Neustart beginnt eine Restart Dauerschleife, Bitcoin daemon startet nicht. Vllt. kann ja jemand helfen…bin mittlerweile echt frustriert.
Viele Grüße
Boddei
Hier der Debug report:
- RASPIBLITZ DEBUG LOGS
blitzversion: 1.8.0
chainnetwork: bitcoin / main
22:10:02 up 13 min, 2 users, load average: 1.48, 2.51, 1.78
*** SETUPPHASE / BOOTSTRAP ***
see logs: cat /home/admin/raspiblitz.log
setupPhase–> done
state–> ready
*** BACKGROUNDSERVICE ***
to monitor Background service call: sudo journalctl -f -u background
*** BLOCKCHAIN (MAINNET) SYSTEMD STATUS ***
● bitcoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2023-08-02 22:09:49 BST; 13s ago
Process: 82243 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log blockchain STARTED (code=exited, status=0/SUCCESS)
Process: 82254 ExecStartPre=/bin/chgrp bitcoin /mnt/hdd/bitcoin (code=exited, status=1/FAILURE)
CPU: 60ms
Aug 02 22:09:51 raspberrypi systemd[1]: bitcoind.service: Failed with result ‚exit-code‘.
Aug 02 22:09:51 raspberrypi systemd[1]: Failed to start Bitcoin daemon.
*** LAST BLOCKCHAIN (MAINNET) ERROR LOGS ***
sudo journalctl -u bitcoind -b --no-pager -n8
– Journal begins at Tue 2023-08-01 17:29:22 BST, ends at Wed 2023-08-02 22:10:02 BST. –
Aug 02 22:09:49 raspberrypi systemd[1]: bitcoind.service: Scheduled restart job, restart counter is at 5.
Aug 02 22:09:49 raspberrypi systemd[1]: Stopped Bitcoin daemon.
Aug 02 22:09:49 raspberrypi systemd[1]: bitcoind.service: Start request repeated too quickly.
Aug 02 22:09:49 raspberrypi systemd[1]: bitcoind.service: Failed with result ‚exit-code‘.
Aug 02 22:09:49 raspberrypi systemd[1]: Failed to start Bitcoin daemon.
Aug 02 22:09:51 raspberrypi systemd[1]: bitcoind.service: Start request repeated too quickly.
Aug 02 22:09:51 raspberrypi systemd[1]: bitcoind.service: Failed with result ‚exit-code‘.
Aug 02 22:09:51 raspberrypi systemd[1]: Failed to start Bitcoin daemon.
*** LAST BLOCKCHAIN (MAINNET) 20 INFO LOGS ***
sudo tail -n 20 /mnt/hdd/bitcoin/debug.log
tail: error reading ‚/mnt/hdd/bitcoin/debug.log‘: Input/output error
*** LND (MAINNET) SYSTEMD STATUS ***
● lnd.service - Lightning Network Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Wed 2023-08-02 22:04:39 BST; 5min ago
Process: 32832 ExecStartPre=/home/admin/config.scripts/lnd.check.sh prestart mainnet (code=exited, status=0/SUCCESS) Process: 33071 ExecStart=/usr/local/bin/lnd --configfile=/home/bitcoin/.lnd/lnd.conf (code=exited, status=2)
Main PID: 33071 (code=exited, status=2)
CPU: 2.322s
Aug 02 22:09:51 raspberrypi systemd[1]: Dependency failed for Lightning Network Daemon.
Aug 02 22:09:51 raspberrypi systemd[1]: lnd.service: Job lnd.service/start failed with result ‚dependency‘.
*** LAST LND (MAINNET) ERROR LOGS ***
sudo journalctl -u lnd -b --no-pager -n12
– Journal begins at Tue 2023-08-01 17:29:22 BST, ends at Wed 2023-08-02 22:10:02 BST. –
Aug 02 22:07:03 raspberrypi systemd[1]: Dependency failed for Lightning Network Daemon.
Aug 02 22:07:03 raspberrypi systemd[1]: lnd.service: Job lnd.service/start failed with result ‚dependency‘.
Aug 02 22:07:36 raspberrypi systemd[1]: Dependency failed for Lightning Network Daemon.
Aug 02 22:07:36 raspberrypi systemd[1]: lnd.service: Job lnd.service/start failed with result ‚dependency‘.
Aug 02 22:08:10 raspberrypi systemd[1]: Dependency failed for Lightning Network Daemon.
Aug 02 22:08:10 raspberrypi systemd[1]: lnd.service: Job lnd.service/start failed with result ‚dependency‘.
Aug 02 22:08:44 raspberrypi systemd[1]: Dependency failed for Lightning Network Daemon.
Aug 02 22:08:44 raspberrypi systemd[1]: lnd.service: Job lnd.service/start failed with result ‚dependency‘.
Aug 02 22:09:18 raspberrypi systemd[1]: Dependency failed for Lightning Network Daemon.
Aug 02 22:09:18 raspberrypi systemd[1]: lnd.service: Job lnd.service/start failed with result ‚dependency‘.
Aug 02 22:09:51 raspberrypi systemd[1]: Dependency failed for Lightning Network Daemon.
Aug 02 22:09:51 raspberrypi systemd[1]: lnd.service: Job lnd.service/start failed with result ‚dependency‘.
*** LAST 30 LND (MAINNET) INFO LOGS ***
sudo tail -n 30 /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log
2023-08-02 22:01:55.611 [ERR] RPCS: [/lnrpc.Lightning/ChannelBalance]: waiting to start, RPC services not available
2023-08-02 22:01:57.224 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:01:59.297 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:01.317 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:03.329 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:05.341 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:07.358 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:09.370 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:11.379 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:13.389 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:15.398 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:17.411 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:19.422 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:21.433 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:23.443 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:25.454 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:27.474 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:29.485 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:31.495 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:32.323 [ERR] RPCS: [/lnrpc.Lightning/ChannelBalance]: waiting to start, RPC services not available
2023-08-02 22:02:33.505 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:35.514 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:37.537 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:39.547 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:41.569 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:43.580 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:45.590 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:47.599 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:49.607 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2023-08-02 22:02:51.616 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
*** CORE LIGHTNING (MAINNET) SYSTEMD STATUS ***
- not activated -
*** BLOCKCHAIN (TESTNET) SYSTEMD STATUS ***
- OFF by config -
*** LND (TESTNET) SYSTEMD STATUS *** - OFF by config -
*** CORE LIGHTNING (TESTNET) SYSTEMD STATUS ***
- not activated -
*** BLOCKCHAIN (SIGNET) SYSTEMD STATUS ***
- OFF by config -
*** LND (SIGNET) SYSTEMD STATUS *** - OFF by config -
*** CORE LIGHTNING (SIGNET) SYSTEMD STATUS ***
- not activated -
*** NGINX SYSTEMD STATUS ***
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/nginx.service.d
└─raspiblitz.conf
Active: active (running) since Wed 2023-08-02 21:59:23 BST; 10min ago
Docs: man:nginx(8)
Process: 15487 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 15500 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Main PID: 15511 (nginx)
Tasks: 5 (limit: 9353)
CPU: 274ms
CGroup: /system.slice/nginx.service
├─15511 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
├─15513 nginx: worker process
├─15514 nginx: worker process
├─15515 nginx: worker process
└─15516 nginx: worker process
Aug 02 21:59:23 raspberrypi systemd[1]: Starting A high performance web server and a reverse proxy server…
Aug 02 21:59:23 raspberrypi systemd[1]: Started A high performance web server and a reverse proxy server.
*** LAST NGINX LOGS ***
sudo journalctl -u nginx -b --no-pager -n20
– Journal begins at Tue 2023-08-01 17:29:22 BST, ends at Wed 2023-08-02 22:10:03 BST. –
Aug 02 21:53:40 raspberrypi nginx[644]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 02 21:53:40 raspberrypi systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Aug 02 21:53:40 raspberrypi systemd[1]: nginx.service: Failed with result ‚exit-code‘.
Aug 02 21:53:40 raspberrypi systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Aug 02 21:58:20 raspberrypi systemd[1]: nginx.service: Scheduled restart job, restart counter is at 1.
Aug 02 21:58:20 raspberrypi systemd[1]: Stopped A high performance web server and a reverse proxy server.
Aug 02 21:58:20 raspberrypi systemd[1]: Starting A high performance web server and a reverse proxy server…
Aug 02 21:58:21 raspberrypi nginx[9165]: nginx: [emerg] bind() to 0.0.0.0:50002 failed (98: Address already in use)
Aug 02 21:58:21 raspberrypi nginx[9165]: nginx: [emerg] bind() to 0.0.0.0:50002 failed (98: Address already in use)
Aug 02 21:58:22 raspberrypi nginx[9165]: nginx: [emerg] bind() to 0.0.0.0:50002 failed (98: Address already in use)
Aug 02 21:58:22 raspberrypi nginx[9165]: nginx: [emerg] bind() to 0.0.0.0:50002 failed (98: Address already in use)
Aug 02 21:58:23 raspberrypi nginx[9165]: nginx: [emerg] bind() to 0.0.0.0:50002 failed (98: Address already in use)
Aug 02 21:58:23 raspberrypi nginx[9165]: nginx: [emerg] still could not bind()
Aug 02 21:58:23 raspberrypi systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Aug 02 21:58:23 raspberrypi systemd[1]: nginx.service: Failed with result ‚exit-code‘.
Aug 02 21:58:23 raspberrypi systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Aug 02 21:59:23 raspberrypi systemd[1]: nginx.service: Scheduled restart job, restart counter is at 2.
Aug 02 21:59:23 raspberrypi systemd[1]: Stopped A high performance web server and a reverse proxy server.
Aug 02 21:59:23 raspberrypi systemd[1]: Starting A high performance web server and a reverse proxy server…
Aug 02 21:59:23 raspberrypi systemd[1]: Started A high performance web server and a reverse proxy server.
→ CHECK CONFIG: sudo nginx -t
nginx: [emerg] cannot load certificate „/mnt/hdd/app-data/nginx/tls.cert“: BIO_new_file() failed (SSL: error:02001005:system library:fopen:Input/output error:fopen(‚/mnt/hdd/app-data/nginx/tls.cert‘,‚r‘) error:2006D002:BIO routines:BIO_new_file:system lib)
nginx: configuration file /etc/nginx/nginx.conf test failed
*** BLITZAPI SYSTEMD STATUS ***
● blitzapi.service - BlitzBackendAPI
Loaded: loaded (/etc/systemd/system/blitzapi.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2023-08-02 21:53:39 BST; 16min ago
Main PID: 818 (python)
Tasks: 7 (limit: 9353)
CPU: 8.848s
CGroup: /system.slice/blitzapi.service
└─818 /usr/bin/python -m uvicorn app.main:app --port 11111 --host=0.0.0.0 --root-path /api
Aug 02 22:03:39 raspberrypi python[818]: aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected
Aug 02 22:03:39 raspberrypi python[818]: ERROR:root:LND_GRPC: Unknown error: Socket closed
*** LAST BLITZAPI LOGS ***
sudo journalctl -u blitzapi -b --no-pager -n20
– Journal begins at Tue 2023-08-01 17:29:22 BST, ends at Wed 2023-08-02 22:10:03 BST. –
Aug 02 22:03:39 raspberrypi python[818]: future: <Task finished name=‚Task-6‘ coro=<_initialize_bitcoin() done, defined at ./app/main.py:128> exception=ServerDisconnectedError(‚Server disconnected‘)>
Aug 02 22:03:39 raspberrypi python[818]: Traceback (most recent call last):
Aug 02 22:03:39 raspberrypi python[818]: File „./app/main.py“, line 130, in _initialize_bitcoin
Aug 02 22:03:39 raspberrypi python[818]: await initialize_bitcoin_repo()
Aug 02 22:03:39 raspberrypi python[818]: File „./app/repositories/bitcoin.py“, line 35, in initialize_bitcoin_repo
Aug 02 22:03:39 raspberrypi python[818]: await get_blockchain_info()
Aug 02 22:03:39 raspberrypi python[818]: File „./app/repositories/bitcoin.py“, line 54, in get_blockchain_info
Aug 02 22:03:39 raspberrypi python[818]: result = await bitcoin_rpc_async(„getblockchaininfo“)
Aug 02 22:03:39 raspberrypi python[818]: File „./app/repositories/bitcoin_utils.py“, line 72, in bitcoin_rpc_async
Aug 02 22:03:39 raspberrypi python[818]: async with session.post(bitcoin_config.rpc_url, data=data) as resp:
Aug 02 22:03:39 raspberrypi python[818]: File „/usr/local/lib/python3.9/dist-packages/aiohttp/client.py“, line 1138, in aenter
Aug 02 22:03:39 raspberrypi python[818]: self._resp = await self._coro
Aug 02 22:03:39 raspberrypi python[818]: File „/usr/local/lib/python3.9/dist-packages/aiohttp/client.py“, line 559, in _request
Aug 02 22:03:39 raspberrypi python[818]: await resp.start(conn)
Aug 02 22:03:39 raspberrypi python[818]: File „/usr/local/lib/python3.9/dist-packages/aiohttp/client_reqrep.py“, line 898, in start
Aug 02 22:03:39 raspberrypi python[818]: message, payload = await protocol.read() # type: ignore[union-attr]
Aug 02 22:03:39 raspberrypi python[818]: File „/usr/local/lib/python3.9/dist-packages/aiohttp/streams.py“, line 616, in read
Aug 02 22:03:39 raspberrypi python[818]: await self._waiter
Aug 02 22:03:39 raspberrypi python[818]: aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected
Aug 02 22:03:39 raspberrypi python[818]: ERROR:root:LND_GRPC: Unknown error: Socket closed
- TOUCHSCREEN is OFF by config
- Loop is OFF by config
*** LND-RTL ***
● RTL.service - RTL Webinterface
Loaded: loaded (/etc/systemd/system/RTL.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2023-08-02 22:09:55 BST; 8s ago
Process: 82698 ExecStartPre=/home/admin/config.scripts/bonus.rtl.sh prestart lnd mainnet (code=exited, status=0/SUCCESS)
Process: 82871 ExecStart=/usr/bin/node /home/rtl/RTL/rtl (code=exited, status=1/FAILURE)
Main PID: 82871 (code=exited, status=1/FAILURE)
CPU: 5.594s
Aug 02 22:09:55 raspberrypi node[82871]: at new ExpressApplication (file:///home/rtl/RTL/backend/utils/app.js:80:14)Aug 02 22:09:55 raspberrypi node[82871]: at file:///home/rtl/RTL/rtl.js:10:13
Aug 02 22:09:55 raspberrypi node[82871]: at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
Aug 02 22:09:55 raspberrypi node[82871]: at async Promise.all (index 0)
Aug 02 22:09:55 raspberrypi node[82871]: at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
Aug 02 22:09:55 raspberrypi node[82871]: at async loadESM (node:internal/process/esm_loader:88:5)
Aug 02 22:09:55 raspberrypi node[82871]: at async handleMainPromise (node:internal/modules/run_main:61:12)
Aug 02 22:09:55 raspberrypi systemd[1]: RTL.service: Main process exited, code=exited, status=1/FAILURE
Aug 02 22:09:55 raspberrypi systemd[1]: RTL.service: Failed with result ‚exit-code‘.
Aug 02 22:09:55 raspberrypi systemd[1]: RTL.service: Consumed 5.594s CPU time.
Hint: Some lines were ellipsized, use -l to show in full.
- CL-RTL is OFF by config
*** LAST 20 ElectRS LOGS ***
sudo journalctl -u electrs -b --no-pager -n20
– Journal begins at Tue 2023-08-01 17:29:22 BST, ends at Wed 2023-08-02 22:10:04 BST. –
Aug 02 22:08:39 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Aug 02 22:08:39 raspberrypi electrs[73484]: [2023-08-02T21:08:39.822Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
Aug 02 22:08:39 raspberrypi electrs[73484]: [2023-08-02T21:08:39.822Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
Aug 02 22:08:39 raspberrypi electrs[73484]: Error: electrs failed
Aug 02 22:08:39 raspberrypi electrs[73484]: Caused by:
Aug 02 22:08:39 raspberrypi electrs[73484]: 0: failed to open DB: /mnt/hdd/app-storage/electrs/db/bitcoin
Aug 02 22:08:39 raspberrypi electrs[73484]: 1: IO error: while open a file for lock: /mnt/hdd/app-storage/electrs/db/bitcoin/LOCK: Read-only file system
Aug 02 22:08:39 raspberrypi systemd[1]: electrs.service: Failed with result ‚exit-code‘.
Aug 02 22:09:40 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 6.
Aug 02 22:09:40 raspberrypi systemd[1]: Stopped Electrs.
Aug 02 22:09:40 raspberrypi systemd[1]: Started Electrs.
Aug 02 22:09:40 raspberrypi electrs[81081]: Starting electrs 0.9.9 on aarch64 linux with Config { network: Bitcoin, db_path: „/mnt/hdd/app-storage/electrs/db/bitcoin“, daemon_dir: „/home/electrs/.bitcoin“, daemon_auth: UserPass(„raspibolt“, „“), daemon_rpc_addr: 127.0.0.1:8332, daemon_p2p_addr: 127.0.0.1:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, disable_electrum_rpc: false, server_banner: „Welcome to electrs v0.9.9 - the Electrum Rust Server on your RaspiBlitz“, args: }
Aug 02 22:09:40 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Aug 02 22:09:40 raspberrypi electrs[81081]: [2023-08-02T21:09:40.081Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
Aug 02 22:09:40 raspberrypi electrs[81081]: [2023-08-02T21:09:40.081Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
Aug 02 22:09:40 raspberrypi electrs[81081]: Error: electrs failed
Aug 02 22:09:40 raspberrypi electrs[81081]: Caused by:
Aug 02 22:09:40 raspberrypi electrs[81081]: 0: failed to open DB: /mnt/hdd/app-storage/electrs/db/bitcoin
Aug 02 22:09:40 raspberrypi electrs[81081]: 1: IO error: while open a file for lock: /mnt/hdd/app-storage/electrs/db/bitcoin/LOCK: Read-only file system
Aug 02 22:09:40 raspberrypi systemd[1]: electrs.service: Failed with result ‚exit-code‘.
*** ElectRS Status ***
STATUS ELECTRS SERVICE
configured=1
serviceInstalled=1
serviceRunning=0
serviceRunning=0
tipSynced=0
initialSynced=0
electrumResponding=0
infoSync=‚Not running - check: sudo journalctl -u electrs‘
- LIT is OFF by config
- BTCPayServer is OFF by config
- BTC-RPC-Explorer is OFF by config
*** LAST 20 LNbits LOGS ***
sudo journalctl -u lnbits -b --no-pager -n20
– Journal begins at Tue 2023-08-01 17:29:22 BST, ends at Wed 2023-08-02 22:10:04 BST. –
Aug 02 22:09:18 raspberrypi bonus.lnbits.sh[78289]: # LNBitsFunding(lnd) → network(bitcoin) chain(main) lightning(lnd)Aug 02 22:09:18 raspberrypi bonus.lnbits.sh[78289]: # setting lnd config fresh …
Aug 02 22:09:18 raspberrypi bonus.lnbits.sh[78296]: cat: /mnt/hdd/app-data/lnd/data/chain/bitcoin/mainnet/admin.macaroon: Input/output error
Aug 02 22:09:18 raspberrypi bonus.lnbits.sh[78289]: # FAIL: missing lnd data in ‚/mnt/hdd/app-data/lnd‘ or missing access rights for lnbits user
Aug 02 22:09:18 raspberrypi systemd[1]: lnbits.service: Control process exited, code=exited, status=1/FAILURE
Aug 02 22:09:18 raspberrypi systemd[1]: lnbits.service: Failed with result ‚exit-code‘.
Aug 02 22:09:18 raspberrypi systemd[1]: Failed to start lnbits.
Aug 02 22:09:48 raspberrypi systemd[1]: lnbits.service: Scheduled restart job, restart counter is at 14.
Aug 02 22:09:48 raspberrypi systemd[1]: Stopped lnbits.
Aug 02 22:09:48 raspberrypi systemd[1]: Starting lnbits…
Aug 02 22:09:48 raspberrypi bonus.lnbits.sh[82056]: # Running: ‚bonus.lnbits.sh prestart‘
Aug 02 22:09:48 raspberrypi bonus.lnbits.sh[82056]: ## lnbits.service PRESTART CONFIG
Aug 02 22:09:48 raspberrypi bonus.lnbits.sh[82056]: # → /home/lnbits/lnbits/.env
Aug 02 22:09:48 raspberrypi bonus.lnbits.sh[82056]: # LNBitsFunding(lnd) → network(bitcoin) chain(main) lightning(lnd)Aug 02 22:09:48 raspberrypi bonus.lnbits.sh[82056]: # setting lnd config fresh …
Aug 02 22:09:48 raspberrypi bonus.lnbits.sh[82072]: cat: /mnt/hdd/app-data/lnd/data/chain/bitcoin/mainnet/admin.macaroon: Input/output error
Aug 02 22:09:48 raspberrypi bonus.lnbits.sh[82056]: # FAIL: missing lnd data in ‚/mnt/hdd/app-data/lnd‘ or missing access rights for lnbits user
Aug 02 22:09:48 raspberrypi systemd[1]: lnbits.service: Control process exited, code=exited, status=1/FAILURE
Aug 02 22:09:48 raspberrypi systemd[1]: lnbits.service: Failed with result ‚exit-code‘.
Aug 02 22:09:48 raspberrypi systemd[1]: Failed to start lnbits.
- Thunderhub is OFF by config
- SPECTER is OFF by config
- SPHINX is OFF by config
*** MOUNTED DRIVES ***
Filesystem Type Size Used Avail Use% Mounted on
/dev/root ext4 29G 15G 14G 53% /
devtmpfs devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 3.9G 16K 3.9G 1% /dev/shm
tmpfs tmpfs 1.6G 1.1M 1.6G 1% /run
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 32M 0 32M 0% /var/cache/raspiblitz
/dev/mmcblk0p1 vfat 253M 31M 222M 12% /boot
/dev/sda1 ext4 916G 618G 253G 71% /mnt/hdd
tmpfs tmpfs 787M 16K 787M 1% /run/user/1000
tmpfs tmpfs 787M 16K 787M 1% /run/user/1001
*** DATADRIVE ***
RASPIBLITZ DATA DRIVE Status
BASICS
isMounted=1
isBTRFS=0
ls: reading directory ‚/mnt/hdd‘: Input/output error
hddRaspiData=0
hddRaspiVersion=‚‘
isSSD=0
datadisk=‚sda‘
datapartition=‚sda1‘
hddCandidate=‚sda‘
hddPartitionCandidate=‚sda1‘
hddBlocksBitcoin=0
(standard_in) 1: syntax error
hddBytes=
hddGigaBytes=
hddUsedInfo=‚15G
16K
31M
618G (5311271%)‘
/home/admin/config.scripts/blitz.datadrive.sh: line 438: * 1024: syntax error: operand expected (error token is „* 1024“)
error=‚unkown command‘
*** NETWORK ***
localip=192.xxx.xxx.xxx
localiprange=192.xxx.xxx.xxx/xx
dhcp=1
network_device=eth0
*** HARDWARE TEST RESULTS ***
UndervoltageReports in Logs: 0
*** SYSTEM CACHE STATUS ***
system_vm_vagrant=„0“
system_ram_mb=„7862“
system_ups_battery=„“
system_temp_fahrenheit=„109“
system_up=„811“
system_count_undervoltage=„0“
system_cpu_load=" 1.48, 2.51, 1.78"
system_count_longscan=„2“
system_board=„rp4“
system_init_time=„1691009623“
system_count_start_blockchain=„86“
system_ram_available_mb=„6876“
system_ram_gb=„8“
system_ups_status=„OFF“
system_temp_celsius=„43“
system_count_start_tui=„0“
system_count_start_lightning=„1“
ln_default_error_short=„“
ln_default_online=„0“
ln_default_activated=„1“
ln_default_version=„0.15.4-beta“
ln_default_error_full=„“
ln_default_locked=„0“
ln_default_sync_initial_done=„1“
ln_default_running=„0“
ln_default_ready=„0“
btc_default_version=„v23.0.0“
btc_default_peers=„0“
btc_default_error_short=„“
btc_default_online=„0“
btc_default_sync_percentage=„0“
btc_default_sync_initial_done=„1“
btc_default_port=„“
btc_default_activated=„1“
btc_default_ready=„0“
btc_default_error_full=„“
btc_default_running=„0“