Raspiblitz: Litecoind.service failure

[AngelicInsight]

I returned home to my Raspberry Pi with this error message on the screen. It has previously been working perfectly.

The EXT4-fs error pops up for a brief second at the bottom about every minute. I have not interacted with the Pi in over a day, so I'm assuming the only thing that may have caused the issue was a possible brief loss of power. Here's the messages I get when I SSH into the device.

I'm assuming there was some sort of data corruption on the hard drive due possibly to a power loss. I'll note that the drive is roughly 2 months old and was brand new for this project. Also, I believe this same issue occurred probably a month ago, but at the time I reformatted the drive and started everything from scratch.

Here are the error logs

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
14:51:28 up 19 min, 2 users, load average: 0.93, 0.93, 0.70

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sat 2019-01-26 14:51:19 GMT; 9s ago
Process: 12678 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=1/FAILURE)
Main PID: 12678 (code=exited, status=1/FAILURE)
CGroup: /system.slice/litecoind.service
└─12363 /usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.lite…nf

Jan 26 14:51:19 Hermes systemd[1]: litecoind.service: Failed with result 'e…de'.
Hint: Some lines were ellipsized, use -l to show in full.

* LAST 20 CHAINNETWORK LOGS *
2019-01-26 14:50:48 Using the 'standard' SHA256 implementation
2019-01-26 14:50:48 Default data directory /home/bitcoin/.litecoin
2019-01-26 14:50:48 Using data directory /mnt/hdd/litecoin
2019-01-26 14:50:48 Using config file /home/bitcoin/.litecoin/litecoin.conf
2019-01-26 14:50:48 Using at most 40 automatic connections (1024 file descriptors available)
2019-01-26 14:50:48 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-01-26 14:50:48 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-26 14:50:48 Using 4 threads for script verification
2019-01-26 14:50:48 scheduler thread start
2019-01-26 14:50:48 HTTP: creating work queue of depth 16
2019-01-26 14:50:48 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-01-26 14:50:48 HTTP: starting 4 worker threads
2019-01-26 14:50:48 Cache configuration:
2019-01-26 14:50:48 * Using 12.5MiB for block index database
2019-01-26 14:50:48 * Using 8.0MiB for chain state database
2019-01-26 14:50:48 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2019-01-26 14:50:48 init message: Loading block index...
2019-01-26 14:50:48 Opening LevelDB in /mnt/hdd/litecoin/blocks/index
2019-01-26 14:50:49 Opened LevelDB successfully
2019-01-26 14:50:49 Using obfuscation key for /mnt/hdd/litecoin/blocks/index: 0000000000000000

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-01-26 14:29:08 GMT; 22min ago
Main PID: 605 (lnd)
CGroup: /system.slice/lnd.service
└─605 /usr/local/bin/lnd --externalip=172.90.117.120

Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.262 [INF] RPCS: passwo…8080
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.263 [INF] LTND: Waitin… it.
Hint: Some lines were ellipsized, use -l to show in full.

* LAST 20 LND LOGS *
-- Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Sat 2019-01-26 14:51:29 GMT. --
Jan 26 14:29:08 Hermes systemd[1]: Started LND Lightning Daemon.
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.111 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.111 [INF] LTND: Active chain: Litecoin (network=mainnet)
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.250 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.262 [INF] RPCS: password RPC server listening on [::]:10009
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.262 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.263 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

• RTL is OFF by config

[fluidvoice]

What kind of drive is this, a normal HDD? Search for how to use the fsck command to test and fix HDD corruption problems. You'll have to stop the bitcoind and lnd services and unmount sda1 to run fsck.

[AngelicInsight]

It's the Toshiba HDTB410XK3AA Canvio Basics 1TB Portable External suggested in the current US shopping list.

I'll work on this later today and post results.

[rootzoll]

@AngelicInsight please post your results - its exactly now such situations we have to improve on.

[AngelicInsight]

Ok, I was unable to get fsck to run despite unmounting on the Pi. I shutdown the Raspberry Pi and plugged the hard drive into a computer running GParted Live. I was able to successfully run fsck via Terminal within GParted Live. I plugged the drive back in to the Pi and booted the system.

I'm receiving only this message after boot-up.

The error logs now look like this:

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
05:38:39 up 14 min, 2 users, load average: 0.09, 0.13, 0.15

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) since Sun 2019-01-27 05:38:16 GMT; 23s ago
Process: 9223 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=0/SUCCESS)
Main PID: 9223 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/litecoind.service

* LAST 20 CHAINNETWORK LOGS *
2019-01-27 05:38:16 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-27 05:38:16 Using 4 threads for script verification
2019-01-27 05:38:16 scheduler thread start
2019-01-27 05:38:16 HTTP: creating work queue of depth 16
2019-01-27 05:38:16 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-01-27 05:38:16 HTTP: starting 4 worker threads
2019-01-27 05:38:16 Cache configuration:
2019-01-27 05:38:16 * Using 12.5MiB for block index database
2019-01-27 05:38:16 * Using 8.0MiB for chain state database
2019-01-27 05:38:16 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2019-01-27 05:38:16 init message: Loading block index...
2019-01-27 05:38:16 Opening LevelDB in /mnt/hdd/litecoin/blocks/index
2019-01-27 05:38:16 Corruption: 78 missing files; e.g.: /mnt/hdd/litecoin/blocks/index/006767.ldb
2019-01-27 05:38:16 Database corrupted
2019-01-27 05:38:16 : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2019-01-27 05:38:16 Aborted block database rebuild. Exiting.
2019-01-27 05:38:16 Shutdown: In progress...
2019-01-27 05:38:16 scheduler thread interrupt
2019-01-27 05:38:16 Shutdown: done

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-01-27 04:47:58 GMT; 50min ago
Main PID: 729 (lnd)
CGroup: /system.slice/lnd.service
└─729 /usr/local/bin/lnd --externalip=172.90.117.120

Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.470 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.471 [INF] LTND: Waiting for wallet encryption password. Us…lock it.Hint: Some lines were ellipsized, use -l to show in full.

* LAST 20 LND LOGS *
-- Logs begin at Sun 2019-01-27 04:47:20 GMT, end at Sun 2019-01-27 05:38:40 GMT. --
Jan 27 04:47:58 Hermes systemd[1]: Started LND Lightning Daemon.
Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.419 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.421 [INF] LTND: Active chain: Litecoin (network=mainnet)
Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.461 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.468 [INF] RPCS: password RPC server listening on [::]:10009
Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.470 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 27 04:48:00 Hermes lnd[729]: 2019-01-27 04:48:00.471 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

• RTL is OFF by config

[fluidvoice]

Looks like your blockchain database got corrupted due to the those drive errors.
try via SSH:
sudo systemctl stop litecoind.service
sudo systemctl stop lnd.service
sudo /usr/local/bin/litecoind -daemon -reindex -conf=/home/bitcoin/.litecoin/litecoin.conf
Then if the DB re-index looks like it finished without errors:
sudo reboot
post any errors and/or pertinent logging you see.

[AngelicInsight]

I followed the first 3 steps. The Pi is displaying this:

The (standard_in) 1: syntax error displays for only about 2 seconds every 30 seconds or so. Based on the lack of activity by the hard drive, I don't think anything is currently happening.

Here are the logs:

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
14:21:43 up 4 min, 2 users, load average: 0.94, 0.52, 0.22

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2019-01-27 14:18:56 GMT; 2min 46s ago
Process: 1423 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=0/SUCCESS)
Main PID: 1423 (code=exited, status=0/SUCCESS)

Jan 27 14:18:56 Hermes systemd[1]: Stopped Bitcoin daemon.

* LAST 20 CHAINNETWORK LOGS *
2019-01-27 14:19:20 init message: Loading banlist...
2019-01-27 14:19:20 init message: Starting network threads...
2019-01-27 14:19:20 net thread start
2019-01-27 14:19:20 dnsseed thread start
2019-01-27 14:19:20 init message: Done loading
2019-01-27 14:19:20 opencon thread start
2019-01-27 14:19:20 msghand thread start
2019-01-27 14:19:20 addcon thread start
2019-01-27 14:19:31 Loading addresses from DNS seeds (could take a while)
2019-01-27 14:19:32 New outbound peer connected: version: 70015, blocks=1569005, peer=0
2019-01-27 14:19:42 123 addresses found from DNS seeds
2019-01-27 14:19:42 dnsseed thread exit
2019-01-27 14:19:59 New outbound peer connected: version: 70015, blocks=1569006, peer=1
2019-01-27 14:20:00 New outbound peer connected: version: 70015, blocks=1569006, peer=2
2019-01-27 14:20:01 New outbound peer connected: version: 70015, blocks=1569006, peer=3
2019-01-27 14:20:07 New outbound peer connected: version: 70015, blocks=1569006, peer=4
2019-01-27 14:20:07 New outbound peer connected: version: 70015, blocks=1569006, peer=5
2019-01-27 14:20:20 New outbound peer connected: version: 70015, blocks=1569006, peer=7
2019-01-27 14:20:20 New outbound peer connected: version: 70015, blocks=1569006, peer=6
2019-01-27 14:20:20 connect() to 192.154.150.38:9333 failed after select(): Connection refused (111)

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2019-01-27 14:19:07 GMT; 2min 36s ago
Process: 627 ExecStart=/usr/local/bin/lnd --externalip=${publicIP} (code=killed, signal=TERM)
Main PID: 627 (code=killed, signal=TERM)

Jan 27 14:19:07 Hermes systemd[1]: Stopping LND Lightning Daemon...
Jan 27 14:19:07 Hermes systemd[1]: Stopped LND Lightning Daemon.

* LAST 20 LND LOGS *
-- Logs begin at Sun 2019-01-27 14:17:05 GMT, end at Sun 2019-01-27 14:21:43 GMT. --
Jan 27 14:17:32 Hermes systemd[1]: Started LND Lightning Daemon.
Jan 27 14:17:34 Hermes lnd[627]: 2019-01-27 14:17:34.033 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
Jan 27 14:17:34 Hermes lnd[627]: 2019-01-27 14:17:34.033 [INF] LTND: Active chain: Litecoin (network=mainnet)
Jan 27 14:17:34 Hermes lnd[627]: 2019-01-27 14:17:34.075 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
Jan 27 14:17:34 Hermes lnd[627]: 2019-01-27 14:17:34.081 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 27 14:17:34 Hermes lnd[627]: 2019-01-27 14:17:34.082 [INF] RPCS: password RPC server listening on [::]:10009
Jan 27 14:17:34 Hermes lnd[627]: 2019-01-27 14:17:34.083 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
Jan 27 14:19:07 Hermes systemd[1]: Stopping LND Lightning Daemon...
Jan 27 14:19:07 Hermes systemd[1]: Stopped LND Lightning Daemon.

• RTL is OFF by config

[AngelicInsight]

It's been a few hours and progress is actually displaying on screen now. It must have just needed some time. I'll update when it appears to have finished.

[fluidvoice]

It's been a few hours and progress is actually displaying on screen now. It must have just needed some time. I'll update when it appears to have finished.

You mean the Sync Progress % on the LCD is increasing?

[AngelicInsight]

Yes, it took at least 2.5 hours to show any progress at all. It's now at a little over 5%.

[fluidvoice]

Yes, it took at least 2.5 hours to show any progress at all. It's now at a little over 5%.

Probably normal. What is your output from running...
sudo tail -n 100 /mnt/hdd/bitcoin/debug.log

[AngelicInsight]

Ok, sorry for the delay.

The blockchain sync appeared to finish. It then sat on this screen for over a day with no change.

Here are the logs:

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
04:18:00 up 2 days, 46 min, 2 users, load average: 0.12, 0.18, 0.12

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Mon 2019-01-28 03:35:22 GMT; 2 days ago
Process: 2362 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=0/SUCCESS)
Main PID: 2362 (code=exited, status=0/SUCCESS)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

* LAST 20 CHAINNETWORK LOGS *
2019-01-30 03:53:54 socket send error Broken pipe (32)
2019-01-30 03:55:02 UpdateTip: new best=6ebfc66490ded4a46c760179a3f51ffecac3f4629817d8d8f912198517d27121 height=1570540 version=0x20000000 log2_work=72.781009 tx=30952123 date='2019-01-30 03:54:58' progress=1.000000 cache=101.7MiB(874896txo)
2019-01-30 03:56:06 connect() to 213.219.143.252:9333 failed after select(): No route to host (113)
2019-01-30 03:57:49 UpdateTip: new best=8295517bd1c17b357b6a009a3ec24f8b3ad2a0a41c4089353000b57bbecee728 height=1570541 version=0x20000000 log2_work=72.781014 tx=30952162 date='2019-01-30 03:57:33' progress=1.000000 cache=101.6MiB(874698txo)
2019-01-30 04:02:34 connect() to 173.239.89.211:9333 failed after select(): Connection refused (111)
2019-01-30 04:05:06 socket recv error Connection reset by peer (104)
2019-01-30 04:07:36 socket send error Broken pipe (32)
2019-01-30 04:07:59 Potential stale tip detected, will try using extra outbound peer (last tip update: 610 seconds ago)
2019-01-30 04:08:03 UpdateTip: new best=1415ba4e5a629b2aaf4c89987f8ad15d38afc8d94a65292004558669aaff7b87 height=1570542 version=0x20000000 log2_work=72.781019 tx=30952273 date='2019-01-30 04:07:30' progress=1.000000 cache=101.6MiB(874726txo)
2019-01-30 04:08:14 UpdateTip: new best=dd92e4ba59d23581fe0f473cda1082807d7eede88d1728316e19e03c9aa41c61 height=1570543 version=0x20000000 log2_work=72.781025 tx=30952278 date='2019-01-30 04:08:03' progress=1.000000 cache=101.6MiB(874723txo)
2019-01-30 04:08:16 New outbound peer connected: version: 70015, blocks=1570543, peer=3531
2019-01-30 04:08:19 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: ad1c30883105cb7cacaafcdec24f55ce771d58b0ddc31a2495f3319515e471e4, high-hash, proof of work failed (code 16)
2019-01-30 04:08:19 Misbehaving: 206.189.123.32:47048 peer=3532 (0 -> 50)
2019-01-30 04:08:19 ERROR: invalid header received
2019-01-30 04:13:13 UpdateTip: new best=d90d02356954b9062c13c5a129032d422074036c420133c4bb220cdcddbd1cf4 height=1570544 version=0x20000000 log2_work=72.78103 tx=30952324 date='2019-01-30 04:12:49' progress=1.000000 cache=101.6MiB(874671txo)2019-01-30 04:14:21 Misbehaving: 176.31.233.194:38358 peer=3539 (0 -> 1)
2019-01-30 04:15:21 version handshake timeout from 3539
2019-01-30 04:17:03 Pre-allocating up to position 0x8000000 in blk00133.dat
2019-01-30 04:17:03 UpdateTip: new best=f2c6bbd48aca68a0fb9e3f75648e9069111a4be0bcb648c7d27acb1b1ec9782d height=1570545 version=0x20000000 log2_work=72.781035 tx=30952369 date='2019-01-30 04:16:20' progress=1.000000 cache=101.6MiB(874633txo)
2019-01-30 04:17:57 connect() to [2a02:8108:1100:7348:60f1:3ccb:d732:8bca]:9333 failed after select(): Permission denied (13)

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Mon 2019-01-28 03:35:36 GMT; 2 days ago
Process: 663 ExecStart=/usr/local/bin/lnd --externalip=${publicIP} (code=killed, signal=TERM)
Main PID: 663 (code=killed, signal=TERM)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

* LAST 20 LND LOGS *
-- No entries --

- RTL is OFF by config

I should have updated here first, my mistake, but I used sudo reboot because this step has never taken this long in the past.

After reboot, it returned to this:

Here are the current logs:

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
04:25:25 up 1 min, 2 users, load average: 0.58, 0.34, 0.13

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) since Wed 2019-01-30 04:25:09 GMT; 16s ago
Process: 1426 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=0/SUCCESS)
Main PID: 1426 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/litecoind.service

* LAST 20 CHAINNETWORK LOGS *
2019-01-30 04:25:09 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-30 04:25:09 Using 4 threads for script verification
2019-01-30 04:25:09 scheduler thread start
2019-01-30 04:25:09 HTTP: creating work queue of depth 16
2019-01-30 04:25:09 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-01-30 04:25:09 HTTP: starting 4 worker threads
2019-01-30 04:25:09 Cache configuration:
2019-01-30 04:25:09 * Using 12.5MiB for block index database
2019-01-30 04:25:09 * Using 8.0MiB for chain state database
2019-01-30 04:25:09 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2019-01-30 04:25:09 init message: Loading block index...
2019-01-30 04:25:09 Opening LevelDB in /mnt/hdd/litecoin/blocks/index
2019-01-30 04:25:09 IO error: /mnt/hdd/litecoin/blocks/index/LOCK: Permission denied
2019-01-30 04:25:09 Database I/O error
2019-01-30 04:25:09 : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2019-01-30 04:25:09 Aborted block database rebuild. Exiting.
2019-01-30 04:25:09 Shutdown: In progress...
2019-01-30 04:25:09 scheduler thread interrupt
2019-01-30 04:25:09 Shutdown: done

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-01-30 04:23:57 GMT; 1min 28s ago
Main PID: 729 (lnd)
CGroup: /system.slice/lnd.service
└─729 /usr/local/bin/lnd --externalip=172.90.117.120

Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.162 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.162 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

* LAST 20 LND LOGS *
-- Logs begin at Wed 2019-01-30 04:23:28 GMT, end at Wed 2019-01-30 04:25:25 GMT. --
Jan 30 04:23:57 Hermes systemd[1]: Started LND Lightning Daemon.
Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.013 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.015 [INF] LTND: Active chain: Litecoin (network=mainnet)
Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.146 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.160 [INF] RPCS: password RPC server listening on [::]:10009
Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.162 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 30 04:23:59 Hermes lnd[729]: 2019-01-30 04:23:59.162 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

• RTL is OFF by config

[AngelicInsight]

sudo tail -n 100 /mnt/hdd/litecoin/debug.log has the following output:

2019-01-30 05:00:32 Litecoin Core version v0.16.3 (release build)
2019-01-30 05:00:32 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-01-30 05:00:32 Assuming ancestors of block 66f49ad85624c33e4fd61aa45c54012509ed4a53308908dd07f56346c7939273 have valid signatures.
2019-01-30 05:00:32 Setting nMinimumChainWork=0000000000000000000000000000000000000000000000c1bfe2bbe614f41260
2019-01-30 05:00:32 Using the 'standard' SHA256 implementation
2019-01-30 05:00:32 Default data directory /home/bitcoin/.litecoin
2019-01-30 05:00:32 Using data directory /mnt/hdd/litecoin
2019-01-30 05:00:32 Using config file /home/bitcoin/.litecoin/litecoin.conf
2019-01-30 05:00:32 Using at most 40 automatic connections (1024 file descriptors available)
2019-01-30 05:00:32 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-01-30 05:00:32 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-30 05:00:32 Using 4 threads for script verification
2019-01-30 05:00:32 scheduler thread start
2019-01-30 05:00:32 HTTP: creating work queue of depth 16
2019-01-30 05:00:32 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-01-30 05:00:32 HTTP: starting 4 worker threads
2019-01-30 05:00:32 Cache configuration:
2019-01-30 05:00:32 * Using 12.5MiB for block index database
2019-01-30 05:00:32 * Using 8.0MiB for chain state database
2019-01-30 05:00:32 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2019-01-30 05:00:32 init message: Loading block index...
2019-01-30 05:00:32 Opening LevelDB in /mnt/hdd/litecoin/blocks/index
2019-01-30 05:00:32 IO error: /mnt/hdd/litecoin/blocks/index/LOCK: Permission denied
2019-01-30 05:00:32 Database I/O error
2019-01-30 05:00:32 : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2019-01-30 05:00:32 Aborted block database rebuild. Exiting.
2019-01-30 05:00:32 Shutdown: In progress...
2019-01-30 05:00:32 scheduler thread interrupt
2019-01-30 05:00:32 Shutdown: done

[fluidvoice]

The problem is this:

2019-01-30 05:00:32 IO error: /mnt/hdd/litecoin/blocks/index/LOCK: Permission denied
2019-01-30 05:00:32 Database I/O error
2019-01-30 05:00:32 : Error opening block database.

what is your output from running this from SSH:
sudo ls -al /mnt/hdd/litecoin/blocks/index/LOCK
I think what might have happened is when you reindexed the chain DB from the SSH session the file ownership was set to admin:admin instead of litecoin:litecoin. If so, this can be fixed using the linux chown command recursively on the whole blockchain folder and subfolders. I don't have the chown command syntax available right now, will update later if possible. You can google it or see the man page.
@rootzoll
the LCD scrypt should give a more intelligent message than unknown error (-1) if possible to detect this "Error opening block database" in the log file. Is this fix not working to set ownership here? https://github.com/rootzoll/raspiblitz/issues/239#issuecomment-452840669

[AngelicInsight]

sudo ls -al /mnt/hdd/litecoin/blocks/index/LOCK output was

It looks like it was set to root:root. I did some research and found the command sudo chown -R bitcoin:bitcoin /mnt/hdd/litecoin/blocks to recursively change the ownership.

As you can see from the picture, litecoin:litecoin is not a valid option.

Rebooted the system and was met with this:

Which within a minute switched to this:

I'll update when something changes.

Current logs:

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
00:52:41 up 3 min, 2 users, load average: 1.18, 0.72, 0.31

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) since Thu 2019-01-31 00:52:13 GMT; 28s ago
Process: 2382 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=0/SUCCESS)
Main PID: 2382 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/litecoind.service
└─2387 /usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf

* LAST 20 CHAINNETWORK LOGS *
2019-01-31 00:52:12 Using the 'standard' SHA256 implementation
2019-01-31 00:52:13 Default data directory /home/bitcoin/.litecoin
2019-01-31 00:52:13 Using data directory /mnt/hdd/litecoin
2019-01-31 00:52:13 Using config file /home/bitcoin/.litecoin/litecoin.conf
2019-01-31 00:52:13 Using at most 40 automatic connections (1024 file descriptors available)
2019-01-31 00:52:13 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-01-31 00:52:13 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-31 00:52:13 Using 4 threads for script verification
2019-01-31 00:52:13 scheduler thread start
2019-01-31 00:52:13 HTTP: creating work queue of depth 16
2019-01-31 00:52:13 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-01-31 00:52:13 HTTP: starting 4 worker threads
2019-01-31 00:52:13 Cache configuration:
2019-01-31 00:52:13 * Using 12.5MiB for block index database
2019-01-31 00:52:13 * Using 8.0MiB for chain state database
2019-01-31 00:52:13 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2019-01-31 00:52:13 init message: Loading block index...
2019-01-31 00:52:13 Opening LevelDB in /mnt/hdd/litecoin/blocks/index
2019-01-31 00:52:13 Opened LevelDB successfully
2019-01-31 00:52:13 Using obfuscation key for /mnt/hdd/litecoin/blocks/index: 0000000000000000

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-01-31 00:49:27 GMT; 3min 14s ago
Main PID: 714 (lnd)
CGroup: /system.slice/lnd.service
└─714 /usr/local/bin/lnd --externalip=172.90.117.120

Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.125 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.125 [INF] LTND: Waiting for wallet encryption password. Us…lock it.Hint: Some lines were ellipsized, use -l to show in full.

* LAST 20 LND LOGS *
-- Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Thu 2019-01-31 00:52:41 GMT. --
Jan 31 00:49:27 Hermes systemd[1]: Started LND Lightning Daemon.
Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.022 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.024 [INF] LTND: Active chain: Litecoin (network=mainnet)
Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.112 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.124 [INF] RPCS: password RPC server listening on [::]:10009
Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.125 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 31 00:49:29 Hermes lnd[714]: 2019-01-31 00:49:29.125 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

• RTL is OFF by config

[AngelicInsight]

After a few minutes the logs changed and now show a failure with litecoind.service

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
01:19:31 up 9 min, 2 users, load average: 0.90, 0.82, 0.46

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2019-01-31 01:19:06 GMT; 24s ago
Process: 5710 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=1/FAILURE)
Main PID: 5710 (code=exited, status=1/FAILURE)
CGroup: /system.slice/litecoind.service
└─5410 /usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf

Jan 31 01:19:06 Hermes systemd[1]: litecoind.service: Unit entered failed state.
Jan 31 01:19:06 Hermes systemd[1]: litecoind.service: Failed with result 'exit-code'.

* LAST 20 CHAINNETWORK LOGS *
2019-01-31 01:18:36 Using the 'standard' SHA256 implementation
2019-01-31 01:18:36 Default data directory /home/bitcoin/.litecoin
2019-01-31 01:18:36 Using data directory /mnt/hdd/litecoin
2019-01-31 01:18:36 Using config file /home/bitcoin/.litecoin/litecoin.conf
2019-01-31 01:18:36 Using at most 40 automatic connections (1024 file descriptors available)
2019-01-31 01:18:36 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-01-31 01:18:36 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-01-31 01:18:36 Using 4 threads for script verification
2019-01-31 01:18:36 scheduler thread start
2019-01-31 01:18:36 HTTP: creating work queue of depth 16
2019-01-31 01:18:36 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-01-31 01:18:36 HTTP: starting 4 worker threads
2019-01-31 01:18:36 Cache configuration:
2019-01-31 01:18:36 * Using 12.5MiB for block index database
2019-01-31 01:18:36 * Using 8.0MiB for chain state database
2019-01-31 01:18:36 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2019-01-31 01:18:36 init message: Loading block index...
2019-01-31 01:18:36 Opening LevelDB in /mnt/hdd/litecoin/blocks/index
2019-01-31 01:18:36 Opened LevelDB successfully
2019-01-31 01:18:36 Using obfuscation key for /mnt/hdd/litecoin/blocks/index: 0000000000000000

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-01-31 01:10:51 GMT; 8min ago
Main PID: 629 (lnd)
CGroup: /system.slice/lnd.service
└─629 /usr/local/bin/lnd --externalip=172.90.117.120

Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.931 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.933 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

* LAST 20 LND LOGS *
-- Logs begin at Thu 2019-01-31 01:10:24 GMT, end at Thu 2019-01-31 01:19:31 GMT. --
Jan 31 01:10:51 Hermes systemd[1]: Started LND Lightning Daemon.
Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.792 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.793 [INF] LTND: Active chain: Litecoin (network=mainnet)
Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.923 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.930 [INF] RPCS: password RPC server listening on [::]:10009
Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.931 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 31 01:10:52 Hermes lnd[629]: 2019-01-31 01:10:52.933 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

• RTL is OFF by config

[AngelicInsight]

Ok, I had to change the ownership of the /mnt/hdd/litecoin/chainstate folder to bitcoin:bitcoin as well, because I was getting the same "Permission Denied" error as seen previously.

After making that final change and rebooting, I'm back to this:

But when I run the logs I'm still getting the failure at the top....all other functionality seems normal:

* RASPIBLITZ LOGS *
blitzversion: 0.99
chainnetwork: litecoin / main
02:23:13 up 38 min, 2 users, load average: 0.82, 0.64, 0.86

* CHAINNETWORK SYSTEMD STATUS *
● litecoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2019-01-31 02:22:47 GMT; 26s ago
Process: 22290 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=1/FAILURE)
Main PID: 22290 (code=exited, status=1/FAILURE)
CGroup: /system.slice/litecoind.service
└─743 /usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf

Jan 31 02:22:47 Hermes systemd[1]: litecoind.service: Unit entered failed state.
Jan 31 02:22:47 Hermes systemd[1]: litecoind.service: Failed with result 'exit-code'.

* LAST 20 CHAINNETWORK LOGS *
2019-01-31 01:50:33 UpdateTip: new best=c61c708b563cc11fe619df3b37f23387c5f13208fec384f299b4498d96aad3cc height=1571057 version=0x20000000 log2_work=72.78376 tx=30972973 date='2019-01-31 01:18:58' progress=0.999996 cache=5.4MiB(48204txo)
2019-01-31 01:50:33 UpdateTip: new best=a4e489994e8d29791eebc8645bbe14a5fe195d6bb885473fc5a8714959a8688f height=1571058 version=0x20000000 log2_work=72.783765 tx=30973006 date='2019-01-31 01:20:50' progress=0.999997 cache=5.4MiB(48156txo)
2019-01-31 01:50:33 UpdateTip: new best=d85960203ca677199b0649a1b44b53fc3781ea50a24545290d040b7fdb752e7a height=1571059 version=0x20000000 log2_work=72.78377 tx=30973013 date='2019-01-31 01:21:04' progress=0.999997 cache=5.4MiB(48160txo)
2019-01-31 01:50:34 UpdateTip: new best=8c20534bee910d5c2e880e085d17c49121eb19cda93bc129c56e08363fc2f13d height=1571060 version=0x20000000 log2_work=72.783776 tx=30973132 date='2019-01-31 01:30:35' progress=0.999998 cache=5.4MiB(48619txo)
2019-01-31 01:50:34 UpdateTip: new best=aba26d4aeab75fdf1763928385875cda6d3093e055a730935b6a44743f4e4180 height=1571061 version=0x20000000 log2_work=72.783781 tx=30973158 date='2019-01-31 01:33:50' progress=0.999998 cache=5.4MiB(48602txo)
2019-01-31 01:50:34 UpdateTip: new best=39ed41d5d1ae601291244f0d3e8407d0595257c6f039a45a85267eec8b03402a height=1571062 version=0x20000000 log2_work=72.783786 tx=30973182 date='2019-01-31 01:33:55' progress=0.999998 cache=5.5MiB(48874txo)
2019-01-31 01:50:34 UpdateTip: new best=997b246543143c7bc43600d2bbb7c2409488e09a39c8027621ac21087bfaaa47 height=1571063 version=0x20000000 log2_work=72.783792 tx=30973217 date='2019-01-31 01:36:14' progress=0.999998 cache=5.5MiB(49031txo)
2019-01-31 01:50:34 UpdateTip: new best=2760354112aa2735b40e87a892dfb798666c63acdf4841aa26af2ae8ad5a58f2 height=1571064 version=0x20000000 log2_work=72.783797 tx=30973223 date='2019-01-31 01:37:03' progress=0.999998 cache=5.5MiB(49006txo)
2019-01-31 01:50:35 UpdateTip: new best=3e82a4621c6447eb81e89c2c042b0f582bb5851b8a01fad71e2b6dee2a5795b6 height=1571065 version=0x20000000 log2_work=72.783802 tx=30973229 date='2019-01-31 01:37:22' progress=0.999998 cache=5.5MiB(48997txo)
2019-01-31 01:50:35 UpdateTip: new best=1229a37a55f005cad35332b678b0b6c58bf36d9d20110d374d0f158cd9c64c6e height=1571066 version=0x20000000 log2_work=72.783808 tx=30973249 date='2019-01-31 01:38:44' progress=0.999999 cache=5.5MiB(49007txo)
2019-01-31 01:50:35 UpdateTip: new best=a62b3b700ce12a5a7813a9b0d918d951c95c7e2f0f4ac7349e097f9d907123e9 height=1571067 version=0x20000000 log2_work=72.783813 tx=30973257 date='2019-01-31 01:39:25' progress=0.999999 cache=5.5MiB(49019txo)
2019-01-31 01:57:43 UpdateTip: new best=cb721385f677d587826a1743377505b3484babd27abd673b7bf520418e6061d0 height=1571068 version=0x20000000 log2_work=72.783818 tx=30973501 date='2019-01-31 01:57:43' progress=1.000000 cache=5.4MiB(48777txo)
2019-01-31 02:01:15 UpdateTip: new best=8297bb89fc8d06a0fc7427a0c55adae44cf5cffd27ef839d9b106ff1c34c18bb height=1571069 version=0x20000000 log2_work=72.783824 tx=30973573 date='2019-01-31 02:00:45' progress=1.000000 cache=5.5MiB(49038txo)
2019-01-31 02:06:21 UpdateTip: new best=78ea17650d3435551d2b9d4bc760cbe0e7908f2ef06ca79e760e52bc275929bb height=1571070 version=0x20000000 log2_work=72.783829 tx=30973660 date='2019-01-31 02:05:55' progress=1.000000 cache=5.5MiB(49447txo)
2019-01-31 02:10:18 connect() to [2a02:1203:ecbc:bf20:253b:5cbc:d3a0:4abd]:9333 failed after select(): No route to host (113)
2019-01-31 02:12:12 UpdateTip: new best=1623e79051e9e3ee24f2acf3a4e1e0568788b86a78e03c843b4ea93b5e01328f height=1571071 version=0x20000000 log2_work=72.783834 tx=30973743 date='2019-01-31 02:11:55' progress=1.000000 cache=5.5MiB(49630txo)
2019-01-31 02:16:01 UpdateTip: new best=420fbe0537e36a2db85e539de08a4fabcda7fc890a230c239c89648cc74238f2 height=1571072 version=0x20000000 log2_work=72.78384 tx=30973788 date='2019-01-31 02:15:37' progress=1.000000 cache=5.6MiB(49716txo)
2019-01-31 02:18:11 socket recv error Connection reset by peer (104)
2019-01-31 02:22:08 UpdateTip: new best=ee5fbbe8d541ff6e08c7509e221c7011416dd1069c5a98ba3527f46d6673e1aa height=1571073 version=0x20000000 log2_work=72.783845 tx=30973869 date='2019-01-31 02:22:00' progress=1.000000 cache=5.7MiB(51381txo)
2019-01-31 02:22:25 UpdateTip: new best=0b83cdcdedf7ec97fe26767c6d1e01104048093d37ad5d79103f906f847b0d4d height=1571074 version=0x20000000 log2_work=72.78385 tx=30973870 date='2019-01-31 02:22:08' progress=1.000000 cache=5.7MiB(51383txo)

* LND SYSTEMD STATUS *
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-01-31 01:44:05 GMT; 39min ago
Main PID: 728 (lnd)
CGroup: /system.slice/lnd.service
└─728 /usr/local/bin/lnd --externalip=172.90.117.120

Jan 31 02:23:08 Hermes lnd[728]: 2019-01-31 02:23:08.172 [DBG] RPCS: [walletbalance] Total balance=0.03115142 BTC
Jan 31 02:23:09 Hermes lnd[728]: 2019-01-31 02:23:09.244 [INF] RPCS: [listchannels] fetched 29 channels from DB

* LAST 20 LND LOGS *
-- Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Thu 2019-01-31 02:23:13 GMT. --
Jan 31 02:22:59 Hermes lnd[728]: 2019-01-31 02:22:59.553 [DBG] PEER: Sending Ping to 75.130.204.234:39146
Jan 31 02:22:59 Hermes lnd[728]: 2019-01-31 02:22:59.631 [DBG] PEER: Received Ping from 75.130.204.234:39146
Jan 31 02:22:59 Hermes lnd[728]: 2019-01-31 02:22:59.631 [DBG] PEER: Sending Pong to 75.130.204.234:39146
Jan 31 02:22:59 Hermes lnd[728]: 2019-01-31 02:22:59.648 [DBG] PEER: Received Pong from 75.130.204.234:39146
Jan 31 02:23:01 Hermes lnd[728]: 2019-01-31 02:23:01.658 [DBG] PEER: Sending Ping to 23.237.77.18:63455
Jan 31 02:23:01 Hermes lnd[728]: 2019-01-31 02:23:01.750 [DBG] PEER: Received Pong from 23.237.77.18:63455
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.562 [DBG] PEER: Sending Ping to 195.98.26.138:24355
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.656 [DBG] PEER: Received Ping from 23.237.77.18:63455
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.656 [DBG] PEER: Sending Pong to 23.237.77.18:63455
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.686 [DBG] PEER: Received Ping from 195.98.26.138:24355
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.689 [DBG] PEER: Sending Pong to 195.98.26.138:24355
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.773 [DBG] PEER: Received Pong from 195.98.26.138:24355
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.782 [DBG] PEER: Sending Ping to 23.237.76.37:58899
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.859 [DBG] PEER: Received Ping from 23.237.76.37:58899
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.860 [DBG] PEER: Sending Pong to 23.237.76.37:58899
Jan 31 02:23:03 Hermes lnd[728]: 2019-01-31 02:23:03.866 [DBG] PEER: Received Pong from 23.237.76.37:58899
Jan 31 02:23:07 Hermes lnd[728]: 2019-01-31 02:23:07.972 [ERR] CMGR: Can't accept connection: unable to accept connection from 172.90.117.120:49890: EOF
Jan 31 02:23:08 Hermes lnd[728]: 2019-01-31 02:23:08.076 [DBG] RPCS: [walletbalance] Total balance=0.03115142 BTC
Jan 31 02:23:08 Hermes lnd[728]: 2019-01-31 02:23:08.172 [DBG] RPCS: [walletbalance] Total balance=0.03115142 BTC
Jan 31 02:23:09 Hermes lnd[728]: 2019-01-31 02:23:09.244 [INF] RPCS: [listchannels] fetched 29 channels from DB

• RTL is OFF by config

[AngelicInsight]

Should /mnt/hdd/litecoin/mempool.dat be bitcoin:bitcoin as well?

[fluidvoice]

I don't know but if your LCD output (your blue box) looks normal which it does, I wouldn't worry about it. Doesn't look like there are errors as of now. If you still have DB/file related errors you might have to reindex again but instead of using -reindex use -reindex-chainstate

[AngelicInsight]

Ok, thanks @fluidvoice for all your assistance. Also @rootzoll for your hard work on this project.