raspiblitz: Issue with restored LND data. Authentication handshake failure.

Yesterday night i left my node running with 10/11 channels and working perfectly. Today i woke up with a failure on blue screen. I couldn’t catch up a pick of it, but i remember it was something about 8333 port. Now i’ve restarted the rasppi and this is how it shows.

8d57e436-5a03-4804-abeb-52f1ce0ba67e

I firstly wrote all my passwords, no hits, and then sudo reboot but the command line responds

sulogin: cannot read /dev/tty1: Operation not permitted.

I checked the SD card and it seems to have no system files failure. I can’t reach the node with SSH or RTL. Just wonder if reflashing SD card will works or is something about HDD.

Any suggestion?

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 52 (15 by maintainers)

Most upvoted comments

Perfect @openoms. I tipped you for a beer. @fluidvoice i’d love to invite you a beer too, but no tippin account. Send me an invoice and i’ll hit it. Thank you guys.

I close totally the issue. I’ve learned a lot these 15 days with my node out. I’ll look forward to improve my privacy too.

Jos3xTv on Apr 7, 2019

Not booting raspiblitz. Asking PWD for maintenance #442

And there is no option to type any command. Just asking for
Give root password for maintenance
(or press Control-D to continue)
And when I type Control-D shows
sulogin: cannot read /dev/tty1: Operation not permitted.

I had exactly the same problem!

It started when I powered down my pi (normal via raspiblitz menu), waited till lights stopped blinking and HDD light was off. When I powered the pi up again I had exactly the same problem. Could also not make a connection via ssh so hooked up a keyboard to the pi so I could log in as root (on lcd) Then run the following commands:

sudo umount /dev/sda2 ( corresponds to /mnt/hdd on my external HDD) sudo fsck -y /dev/sda2

On the lcd screen there is some info about errors with inodes and that it is fixed now. (Don’t know exactly what is was saying anymore and did not write it down, sorry just a noob here…) Reboot the pi and all seems to work again, so in my case it was some corruption on de external HDD?

Too bad it was not this easy for you and since the issue is still open I guess it’s not solved. But because I started with exactly the same error thought I share my experience, sorry I could not help you more… Hope you will get it fixed though!!

istie on Apr 13, 2019

try sudo e2fsck -y /dev/sda1 then reboot

fluidvoice on Mar 22, 2019

It’s possible your SD card got filled up with logs (this problem was recently fixed) or it got corrupted. I would burn the SD card again with the latest code.

fluidvoice on Mar 19, 2019

@Jos3xTv it’s not worth putting more time in with only software changes. Time to try a different hard drive, case, and power supply. New or not, your system is acting strange and it’s looking more likely some kind of hardware problem.

fluidvoice on Apr 3, 2019

umount: /mnt/hdd: target is busy

can try stopping the services and try again.

sudo systemctl stop bitcoind
sudo systemctl stop lnd

openoms on Apr 1, 2019

Nothing happen with your commands. Thank you too.

admin@WOPR:~ $ umount /dev/sda2
umount: /dev/sda2: No such file or directory
admin@WOPR:~ $ umount /dev/sda1
umount: /mnt/hdd: umount failed: Operation not permitted

A @Jos3xTv try the commands with sudo! sudo umount /dev/sda1 sudo fsck -y /dev/sda1

openoms on Apr 1, 2019

@istie yes it seems you have sorted it out with repairing the filesystem with fsck. Did you see any strange character appearing as well? If not the difference is probably that you had the issue with the hdd and @Jos3xTv has a problem corrupting the datastream somewhere.

@istie Can you run our powertest script as well to check if there is no power supply issue which could cause further corruption? Paste and run this in your terminal connected to the RaspiBlitz: wget https://raw.githubusercontent.com/openoms/raspiblitz/powertest/home.admin/XXpowertest.sh && sudo chmod +x XXpowertest.sh && ./XXpowertest.sh It runs for a minute, just copy the output here afterwards.

openoms on Apr 1, 2019

For diagnostic purposes you could try this: https://retroresolution.com/2015/11/28/overclocking-and-stability-testing-the-raspberry-pi-2-part-3-ram-check-with-memtester/

sudo apt-get install memtester
memtester 500m 4

It all comes OK on my Pi, let`s see if it can catch a problem.

openoms on Mar 31, 2019

Weird characters indeed coming at you at at random. even here:

Saving to: â€˜XXpowertest.shâ€™ XXpowertest.sh 100%[===================>] 5.25K --.-KB/s in 0.001s 2019-03-31 18:57:51 (9.06 MB/s) - â€˜XXpowertest.shâ€™ saved [5378/5378]

This might be som fundamental fault with your Pi board. The memory or the processor is messing things up. I am sure specific tests exist, I try to look it up, but I am afraid you might end needing to change the Pi itself.

openoms on Mar 31, 2019

The results of the commands…

Unlock LND Wallet --> lncli --chain=bitcoin unlock

HELP: Enter your PASSWORD C You may wait some seconds until you get asked for password.

Input wallet password:

lnd successfully unlocked! ^Cadmin@WOPR:~ $ wget https://raw.githubusercontent.com/openoms/raspiblitz/powerst/home.admin/XXpowertest.sh && sudo chmod +x XXpowertest.sh && ./XXpowertest.sh –2019-03-31 18:57:51-- https://raw.githubusercontent.com/openoms/raspiblitz/powertest/home.admin/XXpowertest.sh Resolving raw.githubusercontent.com (raw.githubusercontent.com)… 151.101.132.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.132.133|:443… connected. HTTP request sent, awaiting response… 200 OK Length: 5378 (5.3K) [text/plain] Saving to: â€˜XXpowertest.shâ€™

XXpowertest.sh 100%[===================>] 5.25K --.-KB/s in 0.001s

2019-03-31 18:57:51 (9.06 MB/s) - â€˜XXpowertest.shâ€™ saved [5378/5378]

Reading package lists… Done Building dependency tree Reading state information… Done The following additional packages will be installed: libmariadbclient18 mysql-common The following NEW packages will be installed: libmariadbclient18 mysql-common sysbench 0 upgraded, 3 newly installed, 0 to remove and 22 not upgraded. Need to get 776 kB of archives. After this operation, 4,207 kB of additional disk space will be used. Get:1 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian stretch/main armhf mysql-common all 5.8+1.0.2 [5,608 B] Get:2 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian stretch/main armhf libmariadbclient18 armhf 10.1.37-0+deb9u1 [714 kB] Get:3 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian stretch/main armhf sysbench armhf 0.4.12-1.2 [55.8 kB] Fetched 776 kB in 1s (461 kB/s) Selecting previously unselected package mysql-common. (Reading database … 81501 files and directories currently installed.) Preparing to unpack …/mysql-common_5.8+1.0.2_all.deb … Unpacking mysql-common (5.8+1.0.2) … Selecting previously unselected package libmariadbclient18:armhf. Preparing to unpack …/libmariadbclient18_10.1.37-0+deb9u1_armhf.deb … Unpacking libmariadbclient18:armhf (10.1.37-0+deb9u1) … Selecting previously unselected package sysbench. Preparing to unpack …/sysbench_0.4.12-1.2_armhf.deb … Unpacking sysbench (0.4.12-1.2) … Setting up mysql-common (5.8+1.0.2) … update-alternatives: using /etc/mysql/my.cnf.fallback to provide /etc/mysql/my.cnf (my.cnf) in auto mode Setting up libmariadbclient18:armhf (10.1.37-0+deb9u1) … Processing triggers for libc-bin (2.24-11+deb9u4) … Processing triggers for man-db (2.7.6.1-2) … Setting up sysbench (0.4.12-1.2) …

Starting sysbench to run for ~60 secsa

To stop simply press [ctrl]-[c]

48.3’C 1400 MHz 0000000000000000000 1.3438V 53.7’C 1400 MHz 0000000000000000000 1.3438V 55.8’C 1400 MHz 0000000000000000000 1.3438V 56.9’C 1400 MHz 0000000000000000000 1.3438V 58.0’C 1400 MHz 0000000000000000000 1.3438V 59.1’C 1400 MHz 0000000000000000000 1.3438V 59.1’C 1400 MHz 0000000000000000000 1.3438V 54.8’C 1400 MHz 0000000000000000000 1.2V 53.7’C 1400 MHz 0000000000000000000 1.3438V 53.2’C 1400 MHz 0000000000000000000 1.3438V 51.5’C 1400 MHz 0000000000000000000 1.3438V 51.5’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 600/ 600 MHz 1.3438V 48.9’C 1400/ 600 MHz 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400/ 600 MHz 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400/ 600 MHz 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.9’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400/ 600 MHz 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400/ 600 MHz 1.3438V 49.4’C 600 MHz 0000000000000000000 1.2V 48.9’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.9’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 51.0’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 51.5’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 600 MHz 0000000000000000000 1.2V 47.8’C 1400 MHz 0000000000000000000 1.3438V 47.2’C 1400/ 600 MHz 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 47.2’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 47.2’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400/ 600 MHz 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400/ 600 MHz 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 47.2’C 1400 MHz 0000000000000000000 1.3438V 47.2’C 1400 MHz 0000000000000000000 1.3438V 47.2’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 600/ 600 MHz 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.2V 47.8’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.2V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 600/ 600 MHz 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.9’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 600/ 600 MHz 1.3438V 46.7’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 600/ 600 MHz 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 600/ 600 MHz 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.2V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400/ 600 MHz 1.3438V 47.8’C 1400/ 600 MHz 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400/ 600 MHz 1.3438V 51.0’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400/ 600 MHz 1.3438V 48.3’C 1400 MHz 0000000000000000000 1.3438V 48.3’C 1400/ 600 MHz 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 47.8’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V 48.9’C 600/ 600 MHz 1.3438V 48.9’C 1400 MHz 0000000000000000000 1.3438V 49.4’C 1400 MHz 0000000000000000000 1.3438V 50.5’C 1400 MHz 0000000000000000000 1.3438V ^C admin@WOPR:~ $ sudo ls -al /etc/systemd/system/bitcoind.service && sudo cat /etc/systemd/system/bitcoind.service -rwxr-xr-x 1 root root 559 Mar 28 07:16 /etc/systemd/system/bitcoind.service

RaspiBlitz: systemd unit for bitcoind

[Unit] Description=Bitcoin daemon Wants=bootstrap.service After=bootstrap.service

for use with sendmail alert (coming soon)

#OnFailure=systemd-sendmail@%n

[Service] User=bitcoin Group=bitcoin Type=forking PIDFile=/home/bitcoin/.bitcoin/bitcoind.pid ExecStart=/usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/.bitcoin/bitcoind.pid KillMode=process Restart=always TimeoutSec=120 RestartSec=30 StandardOutput=null StandardError=journal

[Install] WantedBy=multi-user.targetadmin@WOPR:~ $ sudo ls -al /home/bitcoin/.bitcoin/bitc/bitcoin/.bitcoin/bitcoind.pid -rw------- 1 bitcoin bitcoin 4 Mar 31 10:29 /home/bitcoin/.bitcoin/bitcoind.pid 834 admin@WOPR:~ $ sudo shutdown -r Shutdown scheduled for Sun 2019-03-31 19:15:43 BST, use ‘shutdown -c’ to cancel. admin@WOPR:~ $

Reboot and loop again. The red light is always on. No blink at all. I tried

admin@WOPR:~ /home/admin/XXdebugLogs.sh

*** RASPIBLITZ LOGS *** blitzversion: 1.1 chainnetwork: bitcoin / main 19:31:31 up 2 min, 2 users, load average: 1.52, 0.55, 0.20

*** CHAINNETWORK SYSTEMD STATUS *** â— bitcoind.service - Bitcoin daemon Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-03-31 19:30:10 BST; 1min 21s ago Process: 794 ExecStart=/usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/.bitcoin/bitcoind.pid (code=exited, status=0/SUCCESS) Main PID: 812 (bitcoind) CGroup: /system.slice/bitcoind.service â””â”€812 /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoinâ€¦id

Mar 31 19:30:09 WOPR systemd[1]: Starting Bitcoin daemon… Mar 31 19:30:10 WOPR systemd[1]: Started Bitcoin daemon.

*** LAST 5 ERROR LOGS *** – Logs begin at Sun 2019-03-31 19:29:08 BST, end at Sun 2019-03-31 19:31:32 BST. – Mar 31 19:30:09 WOPR systemd[1]: Starting Bitcoin daemon… Mar 31 19:30:10 WOPR systemd[1]: Started Bitcoin daemon.

*** LAST 20 INFO LOGS *** 2019-03-31T18:30:10Z Cache configuration: 2019-03-31T18:30:10Z * Using 2.0MiB for block index database 2019-03-31T18:30:10Z * Using 12.2MiB for transaction index database 2019-03-31T18:30:10Z * Using 8.0MiB for chain state database 2019-03-31T18:30:10Z * Using 77.8MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space) 2019-03-31T18:30:10Z init message: Loading block index… 2019-03-31T18:30:10Z Opening LevelDB in /mnt/hdd/bitcoin/blocks/index 2019-03-31T18:30:10Z Opened LevelDB successfully 2019-03-31T18:30:10Z Using obfuscation key for /mnt/hdd/bitcoin/blocks/index: 0000000000000000 2019-03-31T18:30:44Z LoadBlockIndexDB: last block file = 1579 2019-03-31T18:30:44Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=113, size=131324248, heights=569519…569631, time=2019-03-30…2019-03-31) 2019-03-31T18:30:44Z Checking all blk files are present… 2019-03-31T18:30:45Z Opening LevelDB in /mnt/hdd/bitcoin/chainstate 2019-03-31T18:30:46Z Opened LevelDB successfully 2019-03-31T18:30:46Z Using obfuscation key for /mnt/hdd/bitcoin/chainstate: eadc35e843c5834c 2019-03-31T18:30:46Z Loaded best chain: hashBestChain=00000000000000000021b24e6627996f12ceb3f4e3422216cd189f195688d266 height=569631 date=2019-03-31T18:14:14Z progress=0.999994 2019-03-31T18:30:46Z init message: Rewinding blocks… 2019-03-31T18:30:54Z init message: Verifying blocks… 2019-03-31T18:30:54Z Verifying last 6 blocks at level 3 2019-03-31T18:30:54Z [0%]… *** 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-03-31 19:30:10 BST; 1min 22s ago Main PID: 813 (lnd) CGroup: /system.slice/lnd.service â””â”€813 /usr/local/bin/lnd --externalip=88.6.110.175

Mar 31 19:30:10 WOPR systemd[1]: Started LND Lightning Daemon.

*** LAST 5 LND ERROR LOGS *** – Logs begin at Sun 2019-03-31 19:29:08 BST, end at Sun 2019-03-31 19:31:32 BST. – Mar 31 19:30:10 WOPR systemd[1]: Started LND Lightning Daemon.

*** LAST 20 LND INFO LOGS *** 2019-03-31 19:21:51.669 [INF] LTND: Shutdown complete2019-03-31 19:22:52.091 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default 2019-03-31 19:22:52.091 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-03-31 19:22:52.092 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7 2019-03-31 19:22:52.097 [INF] RPCS: password RPC server listening on [::]:10009 2019-03-31 19:22:52.097 [INF] RPCS: password gRPC proxy started at [::]:8080 2019-03-31 19:22:52.098 [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. 2019-03-31 19:23:43.799 [INF] LNWL: Opened wallet 2019-03-31 19:23:44.458 [INF] LTND: Primary chain is set to: bitcoin 2019-03-31 19:23:44.882 [INF] LTND: Shutdown complete2019-03-31 19:25:40.346 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default 2019-03-31 19:25:40.346 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-03-31 19:25:40.473 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7 2019-03-31 19:25:40.527 [INF] RPCS: password RPC server listening on [::]:10009 2019-03-31 19:25:40.528 [INF] RPCS: password gRPC proxy started at [::]:8080 2019-03-31 19:25:40.529 [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. 2019-03-31 19:30:11.180 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default 2019-03-31 19:30:11.181 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-03-31 19:30:11.279 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7 2019-03-31 19:30:11.328 [INF] RPCS: password gRPC proxy started at [::]:8080 2019-03-31 19:30:11.328 [INF] RPCS: password RPC server listening on [::]:10009 2019-03-31 19:30:11.329 [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 admin@WOPR:~ $

Again that weird characters.

Jos3xTv on Mar 31, 2019

It looks like your bitcoind service got setup with a funky startup string. Notice the odd characters here. I have no idea what caused this but it should be not so difficult to fix this.

CGroup: /system.slice/bitcoind.service â””â”€813 /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -piâ€¦id

Mar 30 12:08:14 WOPR systemd[1]: bitcoind.service: Failed to read PID from file /home/bitcâ€¦gument

One test is to try starting up the bitcoind from the command line with: sudo systemctl stop bitcoind.service sudo -u bitcoin /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf sudo tail -f /mnt/hdd/bitcoin/debug.log

fluidvoice on Mar 30, 2019

scp -r admin@192.168.1.187:/home/admin/lnd-rescue-*.tar.gz ./

When you ran the backup script it should have displayed this direction… “RUN THE FOLLOWING COMMAND ON YOUR LAPTOP IN NEW TERMINAL:” scp -r admin@192.168.1.187:/home/admin/lnd-rescue-*.tar.gz ./ It looks like you ran it on the Raspiblitz via SSH rather than on your Mac/Windows machine. If done so, it will pull/download the backup (tar.gz) file from your Raspiblitz node into whatever folder you were in when you ran it.
Note: I’ve not done it but in Windows I think scp is included in the installed Putty app you are prob using for SSH. One of these should work: scp -r admin@192.168.1.187:/home/admin/lnd-rescue-*.tar.gz ./ pscp -r admin@192.168.1.187:/home/admin/lnd-rescue-*.tar.gz ./ pscp -scp -r admin@192.168.1.187:/home/admin/lnd-rescue-*.tar.gz ./

Let me know which works. Perhaps the script and/or doc’s should be improved to make it more obvious how this should be done.

fluidvoice on Mar 24, 2019

It looks like you’re still having problems with that HDD. You may want to try a different hard drive, or minimally I would…

backup your LND data: https://github.com/rootzoll/raspiblitz/blob/9d741270dcfa123efd79c333c3f0b0cb77047ab2/FAQ.md#how-can-i-recover-my-coins-from-a-failing-raspiblitz
then do a complete reinstall and after you get the fresh install running, restore your LND data as per those directions.

fluidvoice on Mar 24, 2019

actually maybe that is the correct log. But it seems the bitcoind.service and lnd.service is not running. Run this and post the outputs: sudo systemctl status bitcoind.service sudo systemctl status lnd.service sudo systemctl start bitcoind.service sudo tail -n 500 /mnt/hdd/bitcoin/debug.log | nc termbin.com 9999

fluidvoice on Mar 23, 2019

what is your output of running /home/admin/XXdebugLogs.sh ? the log above looks like something else.

fluidvoice on Mar 23, 2019

That is the boot partition. You need to mount the rootfs partition which has the /var and other root directories. You are using Windows then you won’t see the rootfs partition because it is formatted as Ext4 which Windows cannot see by default (it’s a Linux file format).

fluidvoice on Mar 18, 2019

get access to your SD card somehow, perhaps via card reader on another computer. Open the file /var/log/syslog and search for “Mounted /boot” then look for errors after any line showing that. Also try grep error -i -A5 /var/log/syslog to look for errors also how much free space is on your SD card?.. df -h and ls -alS /var/log

fluidvoice on Mar 18, 2019