Not booting raspiblitz. Asking PWD for maintenance

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.

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?

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

There is no  /var/log/syslog on my SD. Showing its content.

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 only see that SD card is damage because when i check properties, says it has 43 Mbits when is 32Gb.

That is the boot partition.  You need to mount the rootfs partition which has the /var and other root directories.

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.

Thank you Brad.
This evening I have a slot to burn it. I'll give feedback.

Finally on the road.
I could flash the SD card, but started over. Asking for a node name and A and B password. And then this.

RaspiBlitz
──────────────────────────────────────────────────────────────────────────────

         ┌──────────────────────────────────────────────────┐
         │ OK - RPC password changed                        │
         │                                                  │
         │ Now starting the Setup of your RaspiBlitz.       │
         ├──────────────────────────────────────────────────┤
         │                     <  OK  >                     │
         └──────────────────────────────────────────────────┘

HDD was already initialized/prepared
Now needs to be mounted
*** Adding HDD to the System ***
started from state(waitsetup)
OK - HDD found as sda
*** Check HDD ***
OK - HDD is formatted with ext4 and is named BLOCKCHAIN
Adding line to /etc/fstab ...
UUID=36149e24-2954-4e45-8042-cf2e1fdf456a /mnt/hdd ext4 noexec,defaults 0 2
OK - HDD is listed in /etc/fstab
*** Mount HDD ***
mount: mount /dev/sda1 on /mnt/hdd failed: Structure needs cleaning
FAIL - was not able to mount
admin@RaspiBlitz:~ $
It seems the HDD is also affected. Is there any solution?

try sudo e2fsck -y /dev/sda1 then reboot

I rebooted the Pi and we come back to the beginning.

I'll flash again the SD and i'll refresh post

Ok, I could type sudo e2fsck -y /dev/sda1 and this is the result after reboot.

error: Could not connect to the server <IP_ADDRESS>:8332
Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
bitcoin still not running
*** RASPIBLITZ LOGS ***
blitzversion: 1.1
chainnetwork: bitcoin / main
16:59:03 up 1 min,  2 users,  load average: 0.09, 0.04, 0.01
*** CHAINNETWORK SYSTEMD STATUS ***
Unit bitcoind.service could not be found.
*** LAST 5 ERROR LOGS ***
-- No entries --
*** LAST 20 INFO LOGS ***
2019-03-18T03:21:10Z socket recv error Connection reset by peer (104)
2019-03-18T03:26:19Z UpdateTip: new best=0000000000000000001825a345d6046180dacbf51f37b83315b0c1405399874a height=567581 version=0x20800000 log2_work=90.451622 tx=392648043 date='2019-03-18T03:25:36Z' progress=1.000000 cache=32.6MiB(272203txo) warning='36 of last 100 blocks have unexpected version'
2019-03-18T03:27:27Z socket recv error Connection reset by peer (104)
2019-03-18T03:31:04Z socket receive timeout: 1201s
2019-03-18T03:32:43Z socket recv error Connection reset by peer (104)
2019-03-18T03:33:46Z UpdateTip: new best=0000000000000000000f6e21dbc53c50e76609b03ddfeb74de8c85d26c481373 height=567582 version=0x20000000 log2_work=90.451644 tx=392650232 date='2019-03-18T03:33:27Z' progress=1.000000 cache=33.2MiB(278080txo) warning='36 of last 100 blocks have unexpected version'
2019-03-18T03:38:32Z UpdateTip: new best=0000000000000000000a8fe607f4a70ad74a41e998806b5d5ce73784c3d57eae height=567583 version=0x20000000 log2_work=90.451666 tx=392651726 date='2019-03-18T03:38:26Z' progress=1.000000 cache=33.5MiB(280902txo) warning='35 of last 100 blocks have unexpected version'
2019-03-18T03:41:23Z socket recv error Connection reset by peer (104)
2019-03-18T03:42:12Z UpdateTip: new best=00000000000000000016abc1d7b7347a1952e48a21d9213a8994c0b760296c6a height=567584 version=0x20000000 log2_work=90.451689 tx=392652314 date='2019-03-18T03:41:52Z' progress=1.000000 cache=33.6MiB(282112txo) warning='35 of last 100 blocks have unexpected version'
2019-03-18T03:42:40Z socket recv error Connection reset by peer (104)
2019-03-18T03:46:17Z socket recv error Connection reset by peer (104)
2019-03-18T03:48:46Z socket recv error Connection reset by peer (104)
2019-03-18T03:54:02Z socket send error Connection timed out (110)
2019-03-18T03:55:18Z socket send error Broken pipe (32)
2019-03-18T04:00:53Z socket recv error Connection reset by peer (104)
2019-03-18T04:06:17Z socket recv error Connection reset by peer (104)
2019-03-18T04:06:31Z UpdateTip: new best=00000000000000000028c959eb3f9ecd0b3594d89d23ea20df55076f5da9d5f8 height=567585 version=0x20c00000 log2_work=90.451711 tx=392654865 date='2019-03-18T04:06:00Z' progress=1.000000 cache=34.3MiB(288593txo) warning='36 of last 100 blocks have unexpected version'
2019-03-18T04:12:45Z socket recv error Connection reset by peer (104)
2019-03-18T04:14:57Z socket recv error Connection reset by peer (104)
2019-03-18T04:17:37Z socket recv error Connection reset by peer (104)
*** LND SYSTEMD STATUS ***
Unit lnd.service could not be found.
*** LAST 5 LND ERROR LOGS ***
-- No entries --
*** LAST 20 LND INFO LOGS ***
2019-03-18 04:19:03.510 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622923914723000321, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:18:29 +0000 GMT) from <IP_ADDRESS>:52352
2019-03-18 04:19:03.510 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622805167429320704, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:18:29 +0000 GMT) from <IP_ADDRESS>:52352
2019-03-18 04:19:03.512 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622960198687195136, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:18:29 +0000 GMT) from <IP_ADDRESS>:52352
2019-03-18 04:19:03.513 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=607153619486965761, mflags=00000000, cflags=00000000, update_time=2019-03-18 04:18:20 +0000 GMT) from <IP_ADDRESS>:52352
2019-03-18 04:19:03.513 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622602857338699776, mflags=00000001, cflags=00000010, update_time=2019-03-18 04:18:15 +0000 GMT) from <IP_ADDRESS>:52352
2019-03-18 04:19:04.208 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=621058043559936001, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:17:48 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.209 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=623971749317574656, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:17:59 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.209 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=619435164326625281, mflags=00000001, cflags=00000001, update_time=2019-03-18 04:18:55 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.210 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=569771323650539520, mflags=00000001, cflags=00000011, update_time=2019-03-18 04:18:27 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.210 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=623669383598571520, mflags=00000001, cflags=00000011, update_time=2019-03-18 04:18:01 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.593 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622960198687195136, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:18:29 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.593 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622959099074576384, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:18:29 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.594 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=615746302915248128, mflags=00000000, cflags=00000010, update_time=2019-03-18 04:17:34 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.594 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=615636351716753408, mflags=00000000, cflags=00000000, update_time=2019-03-18 04:17:34 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.595 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=617258131317587968, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:13:04 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.595 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=614143214986657793, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:17:06 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.595 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622854645556707328, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:18:29 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.596 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=617823280247799809, mflags=00000001, cflags=00000011, update_time=2019-03-18 04:16:41 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.596 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=622923914723000321, mflags=00000001, cflags=00000000, update_time=2019-03-18 04:18:29 +0000 GMT) from <IP_ADDRESS>:52734
2019-03-18 04:19:04.596 [DBG] PEER: Received ChannelUpdate(cha
*** LAST 20 RTL LOGS ***
-- No entries --
UNKOWN STATE - there is blockain data config, but blockchain service is not running
It seems that something went wrong during sync/download/copy of the blockchain.
Or something with the config is not correct.
Sometimes a reboot helps --> sudo shutdown -r now
admin@RaspiBlitz:~ $

what is your output of running /home/admin/XXdebugLogs.sh   ?
the log above looks like something else.
Also can you confirm that the file /mnt/hdd/bitcoin/bitcoin.conf has these three lines and if not please ad them and then reboot:
rpcport=8332
rpcallowip=<IP_ADDRESS>
rpcbind=<IP_ADDRESS>:8332

actually may 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 start bitcoind.service
sudo tail -n 500 /mnt/hdd/bitcoin/debug.log | nc termbin.com 9999

Thanks for you time Brad.
This is the output.
...
UNKOWN STATE - there is blockain data config, but blockchain service is not running
It seems that something went wrong during sync/download/copy of the blockchain.
Or something with the config is not correct.
Sometimes a reboot helps --> sudo shutdown -r now
admin@RaspiBlitz:~ $ sudo systemctl status bitcoind.service
Unit bitcoind.service could not be found.
admin@RaspiBlitz:~ $ sudo systemctl start bitcoind.service
Failed to start bitcoind.service: Unit bitcoind.service not found.
admin@RaspiBlitz:~ $ sudo tail -n 500 /mnt/hdd/bitcoin/debug.log | nc termbin.com 9999
https://termbin.com/ynbz
admin@RaspiBlitz:~ $

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.

Hi Brad.
I started to back up my LND data.
admin@RaspiBlitz:~ $ scp -r admin@<IP_ADDRESS>:/home/admin/lnd-rescue-*.tar.gz ./
<EMAIL_ADDRESS>password:
lnd-rescue-8d18616bf65070a60f1fdb5782dcba30.t 100%   48MB  28.2MB/s   00:01
admin@RaspiBlitz:~ $
The script should give me a command to transfer the file but i don't know if it's transfer or not. I'm looking on my PC and no pick.
The created file is lnd-rescue-8d18616bf65070a60f1fdb5782dcba30.tar.gz in pi root. How can i transfer it? (tried to read it on windows with Ext2Fsd, but the system ask me to format de HDD)

scp -r admin@<IP_ADDRESS>:/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@<IP_ADDRESS>:/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@<IP_ADDRESS>:/home/admin/lnd-rescue-*.tar.gz ./
pscp -r admin@<IP_ADDRESS>:/home/admin/lnd-rescue-*.tar.gz ./
pscp -scp -r admin@<IP_ADDRESS>:/home/admin/lnd-rescue-*.tar.gz ./

Finally using WinSCP could transfer the file.
So... i restart my Raspiblitz with new SD and HDD drives.  Finally, after several issues solved with #450 and #466, i get my main screen.
I restored my backup and everything went smooth till now.
When i unblock the LND goes to filtering screen and come back to Unblock LND screen and over and over again. I tried ./70initLND.sh command but didn't work.
Now trying /home/admin/XXdebugLogs.sh bafore and after LND unblocking, and this is the result:
admin@WOPR:~ $ /home/admin/XXdebugLogs.sh
*** RASPIBLITZ LOGS ***
blitzversion: 1.1
chainnetwork: bitcoin / main
13:23:01 up  1:14,  2 users,  load average: 0.28, 0.36, 0.42
*** CHAINNETWORK SYSTEMD STATUS ***
â— bitcoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-03-30 12:08:15 GMT; 1h 14min ago
Process: 795 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: 813 (bitcoind)
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
Mar 30 12:08:15 WOPR systemd[1]: Started Bitcoin daemon.
Hint: Some lines were ellipsized, use -l to show in full.
*** LAST 5 ERROR LOGS ***
-- Logs begin at Sat 2019-03-30 12:04:55 GMT, end at Sat 2019-03-30 13:23:01 GMT. --
Mar 30 12:08:14 WOPR systemd[1]: Starting Bitcoin daemon...
Mar 30 12:08:14 WOPR systemd[1]: bitcoind.service: Failed to read PID from file /home/bitcoin/.bitcoin/bitcoind.pid: Invalid argument
Mar 30 12:08:15 WOPR systemd[1]: Started Bitcoin daemon.
*** LAST 20 INFO LOGS ***
2019-03-30T12:35:40Z UpdateTip: new best=0000000000000000002133c9b10cc728ccacf6491c1b3df995371ef2dcc41ae2 height=569462 version=0x20000000 log2_work=90.49386 tx=396643678 date='2019-03-30T12:35:02Z' progress=1.000000 cache=7.4MiB(65376txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:36:41Z UpdateTip: new best=000000000000000000277a2596ee5e89bc600a2760e681985970f9325be3650d height=569463 version=0x20c00000 log2_work=90.493882 tx=396645976 date='2019-03-30T12:36:08Z' progress=1.000000 cache=8.0MiB(70915txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:39:42Z Pre-allocating up to position 0x900000 in rev01578.dat
2019-03-30T12:39:43Z UpdateTip: new best=00000000000000000011a08574c1acc15f09bdcafa49cefa473153e56b9c893f height=569464 version=0x20c00000 log2_work=90.493905 tx=396648412 date='2019-03-30T12:38:37Z' progress=1.000000 cache=8.6MiB(76495txo) warning='40 of last 100 blocks have unexpected version'
2019-03-30T12:46:55Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:48382
2019-03-30T12:49:46Z Pre-allocating up to position 0x5000000 in blk01578.dat
2019-03-30T12:49:50Z UpdateTip: new best=0000000000000000000f3f01e00538443bf8fa9ff4f1370b59109d5cafb68a18 height=569465 version=0x20000000 log2_work=90.493928 tx=396651151 date='2019-03-30T12:49:26Z' progress=1.000000 cache=9.2MiB(82144txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:49:59Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:48576
2019-03-30T12:54:21Z socket recv error Connection reset by peer (104)
2019-03-30T12:56:38Z socket recv error Connection reset by peer (104)
2019-03-30T12:56:45Z socket recv error Connection reset by peer (104)
2019-03-30T12:57:34Z socket recv error Connection reset by peer (104)
2019-03-30T12:58:05Z socket recv error Connection reset by peer (104)
2019-03-30T13:06:51Z socket recv error Connection reset by peer (104)
2019-03-30T13:10:02Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49576
2019-03-30T13:10:16Z UpdateTip: new best=000000000000000000179b9ae77bb5148ff15198fcca48fa4d96c678d249ba40 height=569466 version=0x20000000 log2_work=90.493951 tx=396652358 date='2019-03-30T13:10:09Z' progress=1.000000 cache=10.4MiB(93879txo) warning='38 of last 100 blocks have unexpected version'
2019-03-30T13:14:09Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49822
2019-03-30T13:15:29Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49936
2019-03-30T13:19:23Z UpdateTip: new best=0000000000000000002aca8696f4e523b7ea93decc41461cdae43a3dab9e8747 height=569467 version=0x20000000 log2_work=90.493973 tx=396654722 date='2019-03-30T13:18:55Z' progress=1.000000 cache=11.2MiB(100541txo) warning='37 of last 100 blocks have unexpected version'
2019-03-30T13:22:50Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:50340
*** LND SYSTEMD STATUS ***
â— lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sat 2019-03-30 13:22:50 GMT; 11s ago
Process: 16135 ExecStart=/usr/local/bin/lnd --externalip=${publicIP} (code=exited, status=1/FAILURE)
Main PID: 16135 (code=exited, status=1/FAILURE)
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Unit entered failed state.
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Failed with result 'exit-code'.
*** LAST 5 LND ERROR LOGS ***
-- Logs begin at Sat 2019-03-30 12:04:55 GMT, end at Sat 2019-03-30 13:23:02 GMT. --
Mar 30 13:16:29 WOPR systemd[1]: Stopped LND Lightning Daemon.
Mar 30 13:16:29 WOPR systemd[1]: Started LND Lightning Daemon.
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Unit entered failed state.
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Failed with result 'exit-code'.
*** LAST 20 LND INFO LOGS ***
2019-03-30 13:11:02.935 [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-30 13:14:09.487 [INF] LNWL: Opened wallet
2019-03-30 13:14:09.930 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:15:10.693 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default
2019-03-30 13:15:10.693 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-03-30 13:15:10.695 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-03-30 13:15:10.700 [INF] RPCS: password RPC server listening on [::]:10009
2019-03-30 13:15:10.700 [INF] RPCS: password gRPC proxy started at [::]:8080
2019-03-30 13:15:10.700 [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-30 13:15:28.709 [INF] LNWL: Opened wallet
2019-03-30 13:15:29.180 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:15:29.492 [INF] LTND: Shutdown complete2019-03-30 13:16:29.931 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default
2019-03-30 13:16:29.931 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-03-30 13:16:29.933 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-03-30 13:16:29.937 [INF] RPCS: password RPC server listening on [::]:10009
2019-03-30 13:16:29.937 [INF] RPCS: password gRPC proxy started at [::]:8080
2019-03-30 13:16:29.937 [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-30 13:22:50.138 [INF] LNWL: Opened wallet
2019-03-30 13:22:50.620 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:22:50.922 [INF] LTND: Shutdown complete

RTL is OFF by config

admin@WOPR:~ $ /home/admin/XXdebugLogs.sh
*** RASPIBLITZ LOGS ***
blitzversion: 1.1
chainnetwork: bitcoin / main
13:23:37 up  1:15,  2 users,  load average: 0.23, 0.33, 0.41
*** CHAINNETWORK SYSTEMD STATUS ***
â— bitcoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-03-30 12:08:15 GMT; 1h 15min ago
Process: 795 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: 813 (bitcoind)
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
Mar 30 12:08:15 WOPR systemd[1]: Started Bitcoin daemon.
Hint: Some lines were ellipsized, use -l to show in full.
*** LAST 5 ERROR LOGS ***
-- Logs begin at Sat 2019-03-30 12:04:55 GMT, end at Sat 2019-03-30 13:23:37 GMT. --
Mar 30 12:08:14 WOPR systemd[1]: Starting Bitcoin daemon...
Mar 30 12:08:14 WOPR systemd[1]: bitcoind.service: Failed to read PID from file /home/bitcoin/.bitcoin/bitcoind.pid: Invalid argument
Mar 30 12:08:15 WOPR systemd[1]: Started Bitcoin daemon.
*** LAST 20 INFO LOGS ***
2019-03-30T12:35:40Z UpdateTip: new best=0000000000000000002133c9b10cc728ccacf6491c1b3df995371ef2dcc41ae2 height=569462 version=0x20000000 log2_work=90.49386 tx=396643678 date='2019-03-30T12:35:02Z' progress=1.000000 cache=7.4MiB(65376txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:36:41Z UpdateTip: new best=000000000000000000277a2596ee5e89bc600a2760e681985970f9325be3650d height=569463 version=0x20c00000 log2_work=90.493882 tx=396645976 date='2019-03-30T12:36:08Z' progress=1.000000 cache=8.0MiB(70915txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:39:42Z Pre-allocating up to position 0x900000 in rev01578.dat
2019-03-30T12:39:43Z UpdateTip: new best=00000000000000000011a08574c1acc15f09bdcafa49cefa473153e56b9c893f height=569464 version=0x20c00000 log2_work=90.493905 tx=396648412 date='2019-03-30T12:38:37Z' progress=1.000000 cache=8.6MiB(76495txo) warning='40 of last 100 blocks have unexpected version'
2019-03-30T12:46:55Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:48382
2019-03-30T12:49:46Z Pre-allocating up to position 0x5000000 in blk01578.dat
2019-03-30T12:49:50Z UpdateTip: new best=0000000000000000000f3f01e00538443bf8fa9ff4f1370b59109d5cafb68a18 height=569465 version=0x20000000 log2_work=90.493928 tx=396651151 date='2019-03-30T12:49:26Z' progress=1.000000 cache=9.2MiB(82144txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:49:59Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:48576
2019-03-30T12:54:21Z socket recv error Connection reset by peer (104)
2019-03-30T12:56:38Z socket recv error Connection reset by peer (104)
2019-03-30T12:56:45Z socket recv error Connection reset by peer (104)
2019-03-30T12:57:34Z socket recv error Connection reset by peer (104)
2019-03-30T12:58:05Z socket recv error Connection reset by peer (104)
2019-03-30T13:06:51Z socket recv error Connection reset by peer (104)
2019-03-30T13:10:02Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49576
2019-03-30T13:10:16Z UpdateTip: new best=000000000000000000179b9ae77bb5148ff15198fcca48fa4d96c678d249ba40 height=569466 version=0x20000000 log2_work=90.493951 tx=396652358 date='2019-03-30T13:10:09Z' progress=1.000000 cache=10.4MiB(93879txo) warning='38 of last 100 blocks have unexpected version'
2019-03-30T13:14:09Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49822
2019-03-30T13:15:29Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49936
2019-03-30T13:19:23Z UpdateTip: new best=0000000000000000002aca8696f4e523b7ea93decc41461cdae43a3dab9e8747 height=569467 version=0x20000000 log2_work=90.493973 tx=396654722 date='2019-03-30T13:18:55Z' progress=1.000000 cache=11.2MiB(100541txo) warning='37 of last 100 blocks have unexpected version'
2019-03-30T13:22:50Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:50340
*** LND SYSTEMD STATUS ***
â— lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sat 2019-03-30 13:22:50 GMT; 47s ago
Process: 16135 ExecStart=/usr/local/bin/lnd --externalip=${publicIP} (code=exited, status=1/FAILURE)
Main PID: 16135 (code=exited, status=1/FAILURE)
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Unit entered failed state.
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Failed with result 'exit-code'.
*** LAST 5 LND ERROR LOGS ***
-- Logs begin at Sat 2019-03-30 12:04:55 GMT, end at Sat 2019-03-30 13:23:38 GMT. --
Mar 30 13:16:29 WOPR systemd[1]: Stopped LND Lightning Daemon.
Mar 30 13:16:29 WOPR systemd[1]: Started LND Lightning Daemon.
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Unit entered failed state.
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Failed with result 'exit-code'.
*** LAST 20 LND INFO LOGS ***
2019-03-30 13:11:02.935 [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-30 13:14:09.487 [INF] LNWL: Opened wallet
2019-03-30 13:14:09.930 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:15:10.693 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default
2019-03-30 13:15:10.693 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-03-30 13:15:10.695 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-03-30 13:15:10.700 [INF] RPCS: password RPC server listening on [::]:10009
2019-03-30 13:15:10.700 [INF] RPCS: password gRPC proxy started at [::]:8080
2019-03-30 13:15:10.700 [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-30 13:15:28.709 [INF] LNWL: Opened wallet
2019-03-30 13:15:29.180 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:15:29.492 [INF] LTND: Shutdown complete2019-03-30 13:16:29.931 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default
2019-03-30 13:16:29.931 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-03-30 13:16:29.933 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-03-30 13:16:29.937 [INF] RPCS: password RPC server listening on [::]:10009
2019-03-30 13:16:29.937 [INF] RPCS: password gRPC proxy started at [::]:8080
2019-03-30 13:16:29.937 [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-30 13:22:50.138 [INF] LNWL: Opened wallet
2019-03-30 13:22:50.620 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:22:50.922 [INF] LTND: Shutdown complete

RTL is OFF by config

admin@WOPR:~ $ /home/admin/XXdebugLogs.sh
*** RASPIBLITZ LOGS ***
blitzversion: 1.1
chainnetwork: bitcoin / main
13:23:50 up  1:15,  2 users,  load average: 0.20, 0.32, 0.41
*** CHAINNETWORK SYSTEMD STATUS ***
â— bitcoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-03-30 12:08:15 GMT; 1h 15min ago
Process: 795 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: 813 (bitcoind)
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
Mar 30 12:08:15 WOPR systemd[1]: Started Bitcoin daemon.
Hint: Some lines were ellipsized, use -l to show in full.
*** LAST 5 ERROR LOGS ***
-- Logs begin at Sat 2019-03-30 12:04:55 GMT, end at Sat 2019-03-30 13:23:51 GMT. --
Mar 30 12:08:14 WOPR systemd[1]: Starting Bitcoin daemon...
Mar 30 12:08:14 WOPR systemd[1]: bitcoind.service: Failed to read PID from file /home/bitcoin/.bitcoin/bitcoind.pid: Invalid argument
Mar 30 12:08:15 WOPR systemd[1]: Started Bitcoin daemon.
*** LAST 20 INFO LOGS ***
2019-03-30T12:35:40Z UpdateTip: new best=0000000000000000002133c9b10cc728ccacf6491c1b3df995371ef2dcc41ae2 height=569462 version=0x20000000 log2_work=90.49386 tx=396643678 date='2019-03-30T12:35:02Z' progress=1.000000 cache=7.4MiB(65376txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:36:41Z UpdateTip: new best=000000000000000000277a2596ee5e89bc600a2760e681985970f9325be3650d height=569463 version=0x20c00000 log2_work=90.493882 tx=396645976 date='2019-03-30T12:36:08Z' progress=1.000000 cache=8.0MiB(70915txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:39:42Z Pre-allocating up to position 0x900000 in rev01578.dat
2019-03-30T12:39:43Z UpdateTip: new best=00000000000000000011a08574c1acc15f09bdcafa49cefa473153e56b9c893f height=569464 version=0x20c00000 log2_work=90.493905 tx=396648412 date='2019-03-30T12:38:37Z' progress=1.000000 cache=8.6MiB(76495txo) warning='40 of last 100 blocks have unexpected version'
2019-03-30T12:46:55Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:48382
2019-03-30T12:49:46Z Pre-allocating up to position 0x5000000 in blk01578.dat
2019-03-30T12:49:50Z UpdateTip: new best=0000000000000000000f3f01e00538443bf8fa9ff4f1370b59109d5cafb68a18 height=569465 version=0x20000000 log2_work=90.493928 tx=396651151 date='2019-03-30T12:49:26Z' progress=1.000000 cache=9.2MiB(82144txo) warning='39 of last 100 blocks have unexpected version'
2019-03-30T12:49:59Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:48576
2019-03-30T12:54:21Z socket recv error Connection reset by peer (104)
2019-03-30T12:56:38Z socket recv error Connection reset by peer (104)
2019-03-30T12:56:45Z socket recv error Connection reset by peer (104)
2019-03-30T12:57:34Z socket recv error Connection reset by peer (104)
2019-03-30T12:58:05Z socket recv error Connection reset by peer (104)
2019-03-30T13:06:51Z socket recv error Connection reset by peer (104)
2019-03-30T13:10:02Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49576
2019-03-30T13:10:16Z UpdateTip: new best=000000000000000000179b9ae77bb5148ff15198fcca48fa4d96c678d249ba40 height=569466 version=0x20000000 log2_work=90.493951 tx=396652358 date='2019-03-30T13:10:09Z' progress=1.000000 cache=10.4MiB(93879txo) warning='38 of last 100 blocks have unexpected version'
2019-03-30T13:14:09Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49822
2019-03-30T13:15:29Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:49936
2019-03-30T13:19:23Z UpdateTip: new best=0000000000000000002aca8696f4e523b7ea93decc41461cdae43a3dab9e8747 height=569467 version=0x20000000 log2_work=90.493973 tx=396654722 date='2019-03-30T13:18:55Z' progress=1.000000 cache=11.2MiB(100541txo) warning='37 of last 100 blocks have unexpected version'
2019-03-30T13:22:50Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:50340
*** 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-03-30 13:23:50 GMT; 186ms ago
Main PID: 21440 (lnd)
CGroup: /system.slice/lnd.service
â””â”€21440 /usr/local/bin/lnd --externalip=<IP_ADDRESS>
Mar 30 13:23:50 WOPR systemd[1]: Started LND Lightning Daemon.
*** LAST 5 LND ERROR LOGS ***
-- Logs begin at Sat 2019-03-30 12:04:55 GMT, end at Sat 2019-03-30 13:23:51 GMT. --
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Unit entered failed state.
Mar 30 13:22:50 WOPR systemd[1]: lnd.service: Failed with result 'exit-code'.
Mar 30 13:23:50 WOPR systemd[1]: lnd.service: Service hold-off time over, scheduling restart.
Mar 30 13:23:50 WOPR systemd[1]: Stopped LND Lightning Daemon.
Mar 30 13:23:50 WOPR systemd[1]: Started LND Lightning Daemon.
*** LAST 20 LND INFO LOGS ***
2019-03-30 13:15:10.695 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-03-30 13:15:10.700 [INF] RPCS: password RPC server listening on [::]:10009
2019-03-30 13:15:10.700 [INF] RPCS: password gRPC proxy started at [::]:8080
2019-03-30 13:15:10.700 [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-30 13:15:28.709 [INF] LNWL: Opened wallet
2019-03-30 13:15:29.180 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:15:29.492 [INF] LTND: Shutdown complete2019-03-30 13:16:29.931 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default
2019-03-30 13:16:29.931 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-03-30 13:16:29.933 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-03-30 13:16:29.937 [INF] RPCS: password RPC server listening on [::]:10009
2019-03-30 13:16:29.937 [INF] RPCS: password gRPC proxy started at [::]:8080
2019-03-30 13:16:29.937 [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-30 13:22:50.138 [INF] LNWL: Opened wallet
2019-03-30 13:22:50.620 [INF] LTND: Primary chain is set to: bitcoin
2019-03-30 13:22:50.922 [INF] LTND: Shutdown complete2019-03-30 13:23:51.248 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta, build=production, logging=default
2019-03-30 13:23:51.248 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-03-30 13:23:51.250 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-03-30 13:23:51.255 [INF] RPCS: password gRPC proxy started at [::]:8080
2019-03-30 13:23:51.255 [INF] RPCS: password RPC server listening on [::]:10009
2019-03-30 13:23:51.255 [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

This loop is neverend.

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

Btw, you have had so many different problems I wonder what could be causing them.  What is the exact power supply you are using?

Hi Brad.
I tried three code line you proposed in that order.
RaspiBlitz (WOPR)                                                  ─────────────────────────────────────────────────────────────────       ┌──────────────── bitcoin / main ───────────────────┐              │  Lightning Filtering Blockchain                   │              │  Progress: ?/569512                               │              │  Please wait - this can take some long time.      │              │  Its OK to close terminal and ssh back in later.  │              └───────────────────────────────────────────────────┘        admin@WOPR:~ $ sudo systemctl stop bitcoind.service
admin@WOPR:~ $ sudo -u bitcoin /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf
Error: Cannot obtain a lock on data directory /mnt/hdd/bitcoin. Bitcoin Core is probably already running.
admin@WOPR:~ $ sudo systemctl stop bitcoind.service                admin@WOPR:~ $ sudo -u bitcoin /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf
Bitcoin server starting
admin@WOPR:~ $ sudo tail -f /mnt/hdd/bitcoin/debug.log
2019-03-30T21:56:49Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=105, size=125073913, heights=569408...569512, time=2019-03-30...2019-03-30)
2019-03-30T21:56:49Z Checking all blk files are present...
2019-03-30T21:56:50Z Opening LevelDB in /mnt/hdd/bitcoin/chainstate2019-03-30T21:56:50Z Opened LevelDB successfully
2019-03-30T21:56:50Z Using obfuscation key for /mnt/hdd/bitcoin/chainstate: eadc35e843c5834c
2019-03-30T21:56:51Z Loaded best chain: hashBestChain=0000000000000000001e3043cc0eebaf7a409656524b5afa558ed56397b17b42 height=569512 date=2019-03-30T21:51:59Z progress=0.999998
2019-03-30T21:56:51Z init message: Rewinding blocks...
2019-03-30T21:56:59Z init message: Verifying blocks...
2019-03-30T21:56:59Z Verifying last 6 blocks at level 3
2019-03-30T21:56:59Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2019-03-30T21:57:18Z No coin database inconsistencies in last 6 blocks (16853 transactions)
2019-03-30T21:57:18Z  block index           51322ms
2019-03-30T21:57:18Z Opening LevelDB in /mnt/hdd/bitcoin/indexes/txindex
2019-03-30T21:57:19Z Opened LevelDB successfully
2019-03-30T21:57:19Z Using obfuscation key for /mnt/hdd/bitcoin/indexes/txindex:<PHONE_NUMBER>000000
2019-03-30T21:57:19Z Wallet disabled!
2019-03-30T21:57:19Z txindex thread start
2019-03-30T21:57:19Z Syncing txindex with block chain from height 569469
2019-03-30T21:57:19Z mapBlockIndex.size() = 569535
2019-03-30T21:57:19Z nBestHeight = 569512
2019-03-30T21:57:19Z Bound to [::]:8333
2019-03-30T21:57:19Z Bound to <IP_ADDRESS>:8333
2019-03-30T21:57:19Z init message: Loading P2P addresses...
2019-03-30T21:57:19Z Leaving InitialBlockDownload (latching to false)
2019-03-30T21:57:19Z torcontrol thread start
2019-03-30T21:57:20Z Loaded 54333 addresses from peers.dat  1072ms
2019-03-30T21:57:20Z init message: Loading banlist...
2019-03-30T21:57:21Z init message: Starting network threads...
2019-03-30T21:57:21Z net thread start
2019-03-30T21:57:21Z init message: Done loading
2019-03-30T21:57:21Z opencon thread start
2019-03-30T21:57:21Z addcon thread start
2019-03-30T21:57:21Z dnsseed thread start
2019-03-30T21:57:21Z msghand thread start
2019-03-30T21:57:21Z New outbound peer connected: version: 70015, blocks=569512, peer=0
2019-03-30T21:57:22Z New outbound peer connected: version: 70015, blocks=569512, peer=1
2019-03-30T21:57:23Z New outbound peer connected: version: 70015, blocks=569512, peer=2
2019-03-30T21:57:26Z New outbound peer connected: version: 70015, blocks=569512, peer=3
****************************************************************************                                                          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:                                             admin@WOPR:~ $ sudo systemctl stop bitcoind.service                admin@WOPR:~ $ sudo -u bitcoin /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf
Error: Cannot obtain a lock on data directory /mnt/hdd/bitcoin. Bitcoin Core is probably already running.
admin@WOPR:~ $ sudo systemctl stop bitcoind.service                admin@WOPR:~ $ sudo -u bitcoin /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf
Error: Cannot obtain a lock on data directory /mnt/hdd/bitcoin. Bitcoin Core is probably already running.                             admin@WOPR:~ $ sudo tail -f /mnt/hdd/bitcoin/debug.log             2019-03-30T21:57:38Z New outbound peer connected: version: 70015, blocks=569512, peer=11
2019-03-30T21:57:38Z New outbound peer connected: version: 70015, blocks=569512, peer=12
2019-03-30T21:57:50Z Syncing txindex with block chain from height 569491
2019-03-30T21:57:50Z New outbound peer connected: version: 70015, blocks=569512, peer=13
2019-03-30T21:58:01Z socket recv error Connection reset by peer (104)
2019-03-30T21:58:24Z Syncing txindex with block chain from height 569512
2019-03-30T21:58:24Z txindex is enabled at height 569512
2019-03-30T21:58:24Z txindex thread exit
2019-03-30T22:01:49Z socket recv error Connection reset by peer (104)
2019-03-30T22:04:44Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:39122
And the loop continuous.
In the other hand, these are the hardware I use. All plug to a good power surge protection.
Aukru Micro USB 5V 3000mA... https://www.amazon.es/dp/B01566WOAG?ref=ppx_pop_mob_ap_shareanDisk Extreme - Tarjeta de... https://www.amazon.es/dp/B06XWMQ81P?ref=ppx_pop_mob_ap_share
WD Red - Disco duro para dispositivos NAS portátiles de 1 TB (Intellipower, SATA a 6 Gb/s, 16 MB de caché, 2,5") https://www.amazon.es/dp/B00EHBES1U/ref=cm_sw_r_cp_apap_9znBaS7bqOy2NALCAR Carcasa USB 3.0 para... https://www.amazon.es/dp/B01D9KX8KG?ref=ppx_pop_mob_ap_share

Looks like bitcoind is starting OK when run from command line. Let's see what's up with it failing when run as a service. Run:
sudo ls -al /etc/systemd/system/bitcoind.service && sudo cat /etc/systemd/system/bitcoind.service
sudo ls -al /home/bitcoin/.bitcoin/bitcoind.pid && sudo cat /home/bitcoin/.bitcoin/bitcoind.pid

@Jos3xTv please run this power supply test script:  https://github.com/rootzoll/raspiblitz/issues/474#issuecomment-478347797

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)... <IP_ADDRESS>
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|: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 (<IP_ADDRESS>-2) ...
Setting up sysbench (0.4.12-1.2) ...

 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:<PHONE_NUMBER>000000
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=<IP_ADDRESS>
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.

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.

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.

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:
umount /dev/sda2 ( corresponds to /mnt/hdd on my external HDD)
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 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.
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.

memtester 500m 4
Loop 1/4:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
Solid Bits          : ok
Block Sequential    : ok
Checkerboard        : ok
Bit Spread          : ok
Bit Flip            : ok
Walking Ones        : ok
Walking Zeroes      : ok
8-bit Writes        : ok
16-bit Writes       : ok
Loop 2/4:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
Solid Bits          : ok
Block Sequential    : ok
Checkerboard        : ok
Bit Spread          : ok
Bit Flip            : ok
Walking Ones        : ok
Walking Zeroes      : ok
8-bit Writes        : ok
16-bit Writes       : ok
Loop 3/4:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
Solid Bits          : ok
Block Sequential    : ok
Checkerboard        : ok
Bit Spread          : ok
Bit Flip            : ok
Walking Ones        : ok
Walking Zeroes      : ok
8-bit Writes        : ok
16-bit Writes       : ok
Loop 4/4:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
Solid Bits          : ok
Block Sequential    : ok
Checkerboard        : ok
Bit Spread          : ok
Bit Flip            : ok
Walking Ones        : ok
Walking Zeroes      : ok
8-bit Writes        : ok
16-bit Writes       : ok
Done

Everything went ok. Thank you anyway.

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:
umount /dev/sda2 ( corresponds to /mnt/hdd on my external HDD)
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!!

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

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

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!
please wait ... update to next screen can be slow
^C
admin@WOPR:~ $ sudo umount /dev/sda1
umount: /mnt/hdd: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
admin@WOPR:~ $ sudo fsck -y /dev/sda1
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.
admin@WOPR:~ $ sudo umount /dev/sda1
umount: /mnt/hdd: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
admin@WOPR:~ $

umount: /mnt/hdd: target is busy

can try stopping the services and try again.
sudo systemctl stop bitcoind
sudo systemctl stop lnd

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: admin@WOPR:~ $ sudo systemctl stop bitcoind
admin@WOPR:~ $ sudo systemctl stop lnd                             admin@WOPR:~ $ sudo umount /dev/sda1
umount: /mnt/hdd: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)          admin@WOPR:~ $

BTW, I switch to an old Raspberry 2, and nothing different happened.

Ok, so you have switched the board and still have the error. I tmust be your HDD then, I thought you have run fsck before, but clearly not sucessfully.
Proceed with:
fuser -cuk /mnt/hdd
to kill all processess using the HDD and the:
sudo umount /dev/sda1
sudo fsck -y /dev/sda1

omg, these funny characters again!
can you try:
sudo umount -l /dev/sda1
or
sudo umount -f /dev/sda1

I don`t see an easy fix here. Your system is corrupted and the easiest way would be to start over.
You have your LND directory backed up, right?
In that case you can format the disk on your Windows machine (untick the quick format option - and could do a surface test as well)
Once that cleared start over with the whole setup with a fresh SDcard.
When everything up and running again you can attempt to restore your old LND data as described here:
https://github.com/rootzoll/raspiblitz/blob/master/FAQ.md#1-recover-lnd-data

Thank you all.
I must say i'm a bit tired of this. This would be the third time i do that @openoms
Anyway. I'll try again in these days. I'll feedback every step.

Sure @Jos3xTv, if we would sell these it would have been an RMA for refund a long time ago 😉.
I am kind of sorry we can't do that 😔.

@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.

First rock on the way.
With a new fresh SD, HDD and power supply.

Finally, after these lines
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

I get to this.

Time to restore my LND backup.

IT'S ALIVE!!!!

But this is not finish yet. I have problems to connect to a peer.

Connect to A Lightning Node

COMMAND LINE:
lncli --chain=bitcoin --network=mainnet connect 022c27b7140c6a5a3d0e6dc0db3d92103e0bfad98809b461a8136e07295688f999@<IP_ADDRESS>:9735
RESULT (might have to wait for timeout):
[lncli] rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "RaspiBlitz")"
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
FAIL
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Its possible that LND daemon is not running, not configured correct or not connected to the lncli.
Press ENTER to return to main menu.

Certificate problems??

Try to reset your macaroons and tls.cert from the EXPORT menu.

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.

i'd love to invite you a beer too, but no tippin account.

I added a link.  Not sure exactly how it works though. Minimum channel to open with them is 0.01 bitcoin. Um, no.  Still I wonder if tips somehow get routed to my address?  Need to read their FAQ I gues ;-)

For what it's worth, I was able to make progress on this by taking the usb drive and plugging it into my laptop, then, from the laptop, running sudo fsck /dev/sdb1(where sdb1 is replaced for your system). That at least allowed my raspiblitz to boot back up again.
Additionally, for the devs, this issue appeared for me only after I tried toggling some of the services (which caused a reboot).

Got it. Thanks. My first tip ever ;-)  I gotta figure out how to attach my Eclair Lightning (on Android) wallet to that Tippin.me account ... or if they require some other wallet to be used.

@fluidvoice tippin.me is a custodial service (for now). You just paste them an invoice from your RaspiBlitz (RTL, Zeus, Zap or any other connected lnd interface) or your Eclair (that is a separate another Lightning node) and if you have a channel open and sufficient incoming liquidity the satoshis will appear in your own wallet where the invoice was generated.

@fluidvoice tippin.me is a custodial service (for now). You just paste them an invoice from your RaspiBlitz (RTL, Zeus, Zap or any other connected lnd interface) or your Eclair (that is a separate stand-alone Lightning node) and if you have a channel open and sufficient incoming liquidity the satoshis will appear in your own wallet where the invoice was generated.

So what is this page then?... https://tippin.me/@fluidvoice
is this not what people use to tip me? Why would I have to send them an invoice?
Sorry, I just have not bothered to see how it works.

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!!

This solution remediated my issue encountering this error- except my external HDD is assigned to sda1.  Thanks.  Evidently, this issue can arise if the RaspBlitz is restarted without updating to the most recent release- keep your nodes updated, folks.  Thank you!


Restarting Karabiner-Elements via CLI to apply changes in JSON file

Hi,
I wrote a small tool ksp (https://github.com/nomaed/karabiner-profile-switch) to quickly toggle between KE profiles from CLI (it's a node app).
The one thing I am missing there is restarting KE after saving configuration, so it will be applied immediately.
Is there a good way to restart KE server without using GUI?
At any rate, this is a temporary solution until the official UI is out.

I thought I read in another thread that KE watches the config file and reloads it when it changes.  Is that not the case?

Not from my experience. Without restarting it, no changes take effect.
On Sat, Oct 1, 2016, 23:33 C. R. Oldham<EMAIL_ADDRESS>wrote:

I thought I read in another thread that KE watches the config file and
reloads it when it changes. Is that not the case?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tekezo/Karabiner-Elements/issues/217#issuecomment-250935873,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJHAMaZz9XGiVgjw6iwfatRa6zLH9oZ5ks5qvsORgaJpZM4KL2J1
.

Just verified it again.
No effect until the service is restarted.

So after a short googling and figuring out, after updating a profile, I use launchctl stop and launchctl start on org.pqrs.karabiner.karabiner_console_user_server and it works perfectly :)
Closing the issue.
kps v1.0.3 is fully functional. Feel free to use it to switch between profiles while the GUI is not out.


OrderBookSync example doesn't work

The OrderbookSync example in the README
const orderbookSync = new Gdax.OrderbookSync(['BTC-USD', 'ETH-USD']);
console.log(orderbookSync.books['ETH-USD'].state());

doesn't return anything. It just prints out
{ asks: [], bids: [] }
and that's it.
Not even after 5 seconds or any other period. Any help?

Here is the sample code that worked for me.. see issue #144
const Gdax = require('gdax');
const orderbookSync = new Gdax.OrderbookSync(['BTC-USD', 'ETH-USD']);
setTimeout(function() { console.log(orderbookSync.books['ETH-USD'].state()); }, 5000);
If that doesn't work, try again at a different time as I've had it not work randomly.   I wish there was more documentation/examples on using orderbooksync.

No it does not work for me. Still return empty order book :(
const Gdax = require('gdax');
const orderbookSync = new Gdax.OrderbookSync(['BTC-USD', 'ETH-USD']);

var waitTill = new Date(new Date().getTime() + 1 * 1000);
while(true){
    if(waitTill< new Date()){
        waitTill = new Date(new Date().getTime() + 1 * 1000);
        console.log(orderbookSync.books['ETH-USD'].state());
    }
}

Does the code above work for you? It does not for me either :(

Hi,
I tried your code and it just keeps outputting the same lines..
{ asks: [], bids: [] }
{ asks: [], bids: [] }

Yes it doesn't... No sure why... But i tried a big time (30s) for the code below and it did work.
const Gdax = require('gdax');
const orderbookSync = new Gdax.OrderbookSync(['BTC-USD', 'ETH-USD']);
setTimeout(function() { console.log(orderbookSync.books['ETH-USD'].state()); }, 30000);

Thannk you @rod-farva-sql , will start from here and will try to understand why.
Would be nice that someone could help from the project.
Cheers.

@axeldomingues I ran across the same issue. It appears that the maintainers on this project haven't uploaded the github version to npm, and my assumption is that you have the version from npm downloaded. To fix this remove gdax with npm uninstall gdax and install the github version with npm install coinbase/gdax-node (or with yarn: yarn add coinbase/gdax-node)

The state is loaded lazily, that's why there isn't any information initially. There should definitely be some event that's fired once it is initialised.


Validate upper bits in last word of numeric literals

Followup to #886
This fixes the issues I found in the last iteration of #886.
Also adds the new source file to the Android.mk to fix the Android NDK build.

Cc: @jcaraban

Rebased

Rebased, squashed, and merged into master as 4dbcef62ee


[BUG] card hovering

Description
When we hover on the cards, it's not smooth.
I can make it smooth which will look decent.
Screenshots
https://github.com/rohansx/informatician/assets/66116440/c4301b4d-38c2-4d99-a24d-927f64c7dd72
Any additional information?
No response
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@anamika7153 Go ahead

@rohansx hey, when will you assign the level label?

@anamika7153 it is not necessary to assign label on issue as it doesn't matter... we need to add labels on PR to get reflected.
But still.. I'll add it for you

@anamika7153 it is not necessary to assign label on issue as it doesn't matter... we need to add labels on PR for the points to get reflected. But still.. I'll add it for you

okay :)


Clear out all data between e2e tests

Goal
Clear out all data between e2e test runs

Overtaken by events


module-info missing provides declarations

bcprov-jdk15on-165.jar contains the service configuration META-INF/services/java.security.Provider so that the security providers can be discovered when the JAR fie is on the class path. The module declaration doesn't have the equivalent provides so it will not be resolved unless some other module explicitly requires it or --add-modules is used to add it as a root on the command line. There are also 3 opens clauses in the module declaration that open packages to java.base that may not be needed.

The provides statement has been added to the current beta at https://www.bouncycastle.org/betas

Closed as now in current release.


Package docker image in ghcr automatically when changed on main

🚀 Feature Request
Is your feature request related to a problem? Please describe.

*We should package blast bast base image and store it every time it is changed on main.

Describe the solution you'd like

*I think a github runner publishing automatically on pull request to main to the ghcr is the way to go for this. The docker-compose file should then be altered to allow developers to used the latest blast image instead of building it.

Completer in PR #92


Adding Content-Length Header

I'm developing a GIT LFS server that returns a S3 put URL back to the client. Unfortunately, S3 requires requests contain a Content-Length header (Even if a chunked request). I can't seem to get the LFS client to include this value even if I put it in the headers section (see below). Is there a way I can force this on?
JSON from GIT LFS Server:
  {
  	"objects": [{
  		"oid": "99a86d47165ef079873100c5db8d96b9d7abcb5f162ae24756d3097fa94d6930",
  		"actions": {
  			"upload": {
  				"href": "https://presigned-url.s3.amazonaws.com/data/99a86d47165ef079873100c5db8d96b9d7abcb5f162ae24756d3097fa94d6930",
  				"expires_at": "2016-04-20T19:11+0000",
  				"authenticated": true,
  				"header": {
  					"x-amz-content-sha256": "99a86d47165ef079873100c5db8d96b9d7abcb5f162ae24756d3097fa94d6930",
  					"Authorization": "...",
  					"X-Amz-Date": "20160420T190142Z",
  					"Host": "presigned-url.s3.amazonaws.com",
  					"Content-Type": "application/octet-stream",
  					"Content-Length": "496800"
  				}
  			},
  			"verify": {
  				"href": "http://localhost:8080/verify"
  			}
  		}
  	}]
  }

Also, here's the curl:
> PUT /data/99a86d47165ef079873100c5db8d96b9d7abcb5f162ae24756d3097fa94d6930 HTTP/1.1
> Host: presigned-url.s3.amazonaws.com
> Authorization: ...
> Content-Type: application/octet-stream
> User-Agent: git-lfs/1.2.0 (GitHub; windows amd64; go 1.6.1; git 386c5d8)
> X-Amz-Content-Sha256: 99a86d47165ef079873100c5db8d96b9d7abcb5f162ae24756d3097fa94d6930
> X-Amz-Date: 20160420T190142Z

Thanks for the help!
Picky

Ah, it's clobbering it here, as it's finishing instantiating the request, so it can actually upload the body.
	if req.Header.Get("Transfer-Encoding") == "chunked" {
		req.TransferEncoding = []string{"chunked"}
	} else {
		req.Header.Set("Content-Length", strconv.FormatInt(o.Size, 10))
	}

	req.ContentLength = o.Size

You're not returning a size property for the objects, so I'm guessing it's assuming size = 0. It is definitely required in the API spec.

That worked, missed that in the schema. Thanks!


prometheus-consul-exporter: 0.8.0 -> 0.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/consul_exporter/versions.
meta.description for prometheus-consul-exporter is: "Prometheus exporter for Consul metrics"
meta.homepage for prometheus-consul-exporter is: "https://github.com/prometheus/consul_exporter"
meta.changelog for prometheus-consul-exporter is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.0 with grep in /nix/store/5iqfhbzdgpvbvyn1d4v9yz4gjmbk5b7v-consul_exporter-0.9.0
found 0.9.0 in filename of file in /nix/store/5iqfhbzdgpvbvyn1d4v9yz4gjmbk5b7v-consul_exporter-0.9.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
prometheus-consul-exporter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5iqfhbzdgpvbvyn1d4v9yz4gjmbk5b7v-consul_exporter-0.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A prometheus-consul-exporter https://github.com/r-ryantm/nixpkgs/archive/f5300868248d6cbc8a65223f94db71297ce60266.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5iqfhbzdgpvbvyn1d4v9yz4gjmbk5b7v-consul_exporter-0.9.0
ls -la /nix/store/5iqfhbzdgpvbvyn1d4v9yz4gjmbk5b7v-consul_exporter-0.9.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

prometheus-consul-exporter

Maintainer pings
cc @hectorj for testing.

Tested roughly this way:
nix-shell -p curl prometheus-consul-exporter -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/a45c3e9b51fa39fa29246b076fa8654adb42a4ab.tar.gz --run "$(cat << 'EOF'
consul_exporter  --consul.server="http://<IP_ADDRESS>:8500" --web.listen-address=<IP_ADDRESS>:9107 > /tmp/consul_exporter.log 2>&1 &
exporter_PID=$!
curl http://<IP_ADDRESS>:9107/metrics
kill $exporter_PID
EOF
)"

It builds, it starts, and it answers http requests. LGTM
Note : in the exported metrics, consul_exporter_build_info{branch="",goversion="go1.19.3",revision="",version=""} 1 does not have the version information. But this isn't new.


A bug for the 'include_cmb' option

In GlobalSkyModel16, CMB temperature is subtracted multiple times
                output -=  K_CMB2MJysr(T, 1e9 * freq)

I think there missed a ifreq

Finally looking at this! Relevant code is here:
https://github.com/telegraphic/pygdsm/blob/60ecc65dc85fcaee97a778dcf55776b10f3dc3ce/pygdsm/gsm16.py#L201
And I agree it should read
                output[ifreq] -=  K_CMB2MJysr(T, 1e9 * freq)


Steam fails to start: glXChooseVisual failed

Describe the bug
Steam fails to start with Assertion Failed: Fatal Error: glXChooseVisual failed.
To Reproduce
Steps to reproduce the behavior:

Install steam via nix.
Try running steam.

Expected behavior
Expected Steam to start.
Screenshots

Additional context
Output and strace output here: https://gist.github.com/samuela/f8473d28d700a3fb36aaf9299f3cf7eb.
Notify maintainers

@jagajaga
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
skainswo@skainswo-X58A-UD3R:~$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.3.0-51-generic, Ubuntu, 18.04.4 LTS (Bionic Beaver)`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.4`
 - channels(skainswo): `"home-manager, nixpkgs-20.09pre226070.6feee80de09"`
 - nixpkgs: `/home/skainswo/.nix-defexpr/channels/nixpkgs`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: steam
# a list of nixos modules affected by the problem
module: steam

I get the same Message on Nixos since update to 20.03 (unstable is the same).
It might have to do with the Nvidia card, i have a GeForce GT 560M with noveau drivers (i.e. nothing special set in configuration.nix). It does work with proprietary Nvidia drivers, but they bring a whole lot of other problems.
@samuela what graphics card do you have?

I have an Nvidia gtx 1060. I'm running on Ubuntu and have installed the Ubuntu-recommended drivers (proprietary I think)

The nix package doesn't work, but the stream website install process works without any hiccups.

It worked after removing and reinstalling steam. I don't know why that should make a difference, but since it has its own update mechanism outside of nix it is probably not our problem.
I guess this can be closed?

@caaaaaa what do you mean removing and reinstalling worked?
I tried to install it via nix-env and got this same error. I removed it with nix-env -e steam and then collected the garbage: sudo nix-collect-garbage -d. I'm still getting the same error when i reinstall.

Fixed my issue with: https://github.com/NixOS/nixpkgs/issues/47932#issuecomment-447508411


Fix #2804: Transform receiver of js.Dynamic#x

This caused expressions like js.constructorOf[Foo].x to blow up with a "stub" error.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3927/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5200/
Test PASSed.


Protein-Protein-Water-Docking

I performed a docking of two proteins with water using its chemical formula 'H2O' [assigned Copies 500], but no water molecules appeared in the output PDB file when viewed with PyMOL. Could there be an issue with my configuration on web server?

By the way, I also tried assigning water using its SMILES code 'O', but encountered a warning about invalid characters.
.
Web server doesn't include water in ligand?

HI @Jason-Han-Hu, thanks for the question. We remove all water molecules during training and inference. Since the model is trained without the water molecules (but they are inherently present in the training data), the predictions will also assume that water is present (although the water molecules won't be shown explicitly).
If you have an application that requires water to be explicitly shown, we'd love to hear more.

Thanks for you response, @joshim5.
I'm trying to identify key amino acids involved in protein-protein interactions, so I need to visualize all possible hydrogen bonds, salt bridges, or other interactions. Is there a way to explicitly display these water molecules in PyMOL?


Archer AX11000 MU-MIMO Tri-Band Gaming Router V1.0 Works :) !!

Just tried it and it works :) .
Only 1 thing: I added the IP of the AX11000 and it detected 2 devices:

My Ax11000 with the right IP (xx.xx.xx.200). It only worked by connecting with https btw.
My HomeWizard P1 Meter with ip xx.xx.xx.111 .

Device version: V1.0
Firmware: 1.3.4 Build 20230906 rel.74809(4555)

@Paul1865 Thank you!
It detects devices which is already connected to HA and to your router

@Paul1865 Please, dont forget to give a star to the repo :)


Standard xml metadata

Description
Defaults to COMPACT-DECODED format, but if the rets server returns the DTD error code of 20514 then the client switches to the STANDARD-XML format.
GitHub Issues

#102

Coverage decreased (-0.4%) to 90.467% when pulling f5595c83c8d8bed2036fc6b886312002adf22f16 on mcrowson:standard-xml-metadata into 39cbaf9696199b7621f8e4e523b3d3c887366ab6 on refindlyllc:development.

Coverage increased (+0.006%) to 90.841% when pulling fd386318b2f29bbde1e56ff1240fb2586dbede24 on mcrowson:standard-xml-metadata into 39cbaf9696199b7621f8e4e523b3d3c887366ab6 on refindlyllc:development.

Coverage increased (+0.006%) to 90.841% when pulling fd386318b2f29bbde1e56ff1240fb2586dbede24 on mcrowson:standard-xml-metadata into 39cbaf9696199b7621f8e4e523b3d3c887366ab6 on refindlyllc:development.

Coverage increased (+0.006%) to 90.841% when pulling fd386318b2f29bbde1e56ff1240fb2586dbede24 on mcrowson:standard-xml-metadata into 39cbaf9696199b7621f8e4e523b3d3c887366ab6 on refindlyllc:development.

Coverage increased (+0.006%) to 90.841% when pulling fd386318b2f29bbde1e56ff1240fb2586dbede24 on mcrowson:standard-xml-metadata into 39cbaf9696199b7621f8e4e523b3d3c887366ab6 on refindlyllc:development.


Add Ukrainian translation (uk_UA)

Translated latest version to 🇺🇦.

I think you need to use "-" instead of "_" in lang file name

Thank you!

@Hrdtr My bad. Will fix this.


Please provide OCI registry distribution

https://docs.gitlab.com/runner/fleet_scaling/fleeting.html#install-a-fleeting-plugin suggests that OCI registry distribution is the recommended way of installing plugins.
I think it can be created by https://gitlab.com/gitlab-org/fleeting/fleeting-artifact

For that some GH actions plugin needed. For now, it's sufficient to use Heat stack and goreleaser.

https://github.com/sardinasystems/fleeting-plugin-openstack/pkgs/container/fleeting-plugin-openstack
Well, that was easy...

@vooon Awesome, thanks! :) I can confirm that it works! Perhaps the config example in the README.md could be adapted to it?
https://github.com/sardinasystems/fleeting-plugin-openstack/blob/7c73ab764566045a6e3d91aecfb556a830d1a580/README.md?plain=1#L108
Should be plugin = "ghcr.io/sardinasystems/fleeting-plugin-openstack:latest"

@baurmatt it's fixed in 3dc95fe , i've changed heat stack to pull image.


Terminal issue

Same as #76101
But this time it happened on Linux.

@weathon you'll need to be more descriptive and give a repro, the issue you linked is related to the system on Windows that emulates how terminals work on Linux, it is definitely not related to that. Please also provide os/vscode version and your settings file.

I cannot find this bug in my VSCode anymore, maybe it is already be fixed?


Small typo in readme: probabbly -> probably

Just fixing a small typo :)

What:
A typo in the readme fidle.

Why:

How:

Checklist:

[ ] Documentation
[ ] Tests
[X] Ready to be merged

@all-contributors please add @moniac for docs


fmt: Printf not respecting String() method of elements of a struct

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go1.7
What operating system and processor architecture are you using (go env)?
play.golang.org
What did you do?
First reported in https://groups.google.com/d/topic/golang-nuts/Upiw-xxCJxQ/discussion
If an operand of fmt.Printf implements method String() string, fmt.Printf respects it and uses it.
But it doesn't if an operand is a struct that has such an element.
https://play.golang.org/p/QJC7Q9Kpch
What did you expect to see?
Int(73) Int(73) 73
&{Int(73)} &{elem:Int(73)} &main.Box{elem:73}
…

What did you see instead?
Int(73) Int(73) 73
&{73} &{elem:73} &main.Box{elem:73}
…

In the second line of the output, none of the format specifiers ("%v", "%+v", "%#v") calls the String() method of Int, in contrast to the first line.

This only happens if the field is unexported. If it's exported, String is properly called:
https://play.golang.org/p/STKBOnEVrb

That was mentioned in the original "golang-nuts" thread quoted earlier.
But I don't see why the exported-ness of a field should affect whether String() is used or not to print that field.

works as expected.
reflect can not access an unexported field and thereby fmt cant either to call the String method.
https://play.golang.org/p/JPUA_FHkov
related:
https://github.com/golang/go/issues/8965

If there are no arguments against i think this can be closed.
That the String method of an unexported field can not be called in another package is normal behavior and fmt is another package. In general e.g. somestruct.someunexportedfield.String() is not directly callable in another package.
It is possible to define a String method on Box that has access to elem and then hands this over to fmt directly to allow for the unexported fields String method to be called:
func (b Box) String() string { return fmt.Sprintf("%s", b.elem) }

func (i Int) String() string { return fmt.Sprintf("Int(%d)", int(i)) }

I wonder if we can document this in some way that makes sense.


Extracted the processing of responses and identify empty bodies

This PR fixes #2 by returning None when Content-Length is 0.
It also extracted the response.json() condition for easy reuse.

Looks good

Hello @wingertge .
When can I expect a new release with this change?

Sorry I forgot about actually publishing. A new version is out now.


add button for smiles to app

Not all keyboard have button "smiles". It is good, when app have this button.

Probably a good place to put this would be in the same panel as stickers. Telegram does this and it works nicely without having to add too many buttons everywhere.


Granular api config

This is a PR to update the documentation for the C-Chain config file. We are adding more granular support for enabling specific services on the C-Chain instead of enabling entire namespaces. I added documentation specifying exactly which calls are added to which namespaces based on the config.
We could probably improve the style of this documentation and may want to consider providing links for each API call to either our own documentation or the relevant Ethereum API call documentation. Please leave any feedback you may have on the best way to organize this.
This PR is also blocked on actually merging the granular API config changes in coreth and bumping the AvalancheGo dependency to use the updated version.

1 nit: https://github.com/ava-labs/avalanche-docs/blob/granular-api-config/docs/build/tutorials/smart-contracts/using-truffle-with-the-avalanche-c-chain.md?plain=1#L259 should be updated as well I think


Improve documentation to make clear what paste button does

Is your feature request related to a problem? Please describe.
Relating to Issue #44
Describe the solution you'd like
Make it clear in the documentation that the Paste button does more than just paste the token in.

Updates are clear and correct.  Closing this issue.


Added Clear-NSAAASession

New functions needed to clear AAA sessions.
Description
Added Clear-NSAAASession
Related Issue
#60
How Has This Been Tested?
Tested in my local environment (NS 11.1 50.10).
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Looks good to me. Thanks @dbroeglin


Use imagestream generator for editing imagestream json files

[x] httpd-container https://github.com/sclorg/httpd-container/pull/205
[x] nginx-container
[x] s2i-php-container https://github.com/sclorg/s2i-php-container/pull/441
[x] varnish-container https://github.com/sclorg/varnish-container/pull/140
[x] mariadb-container https://github.com/sclorg/mariadb-container/pull/232
[x] postgresql-container https://github.com/sclorg/postgresql-container/pull/549
[x] s2i-nodejs-container https://github.com/sclorg/s2i-nodejs-container/pull/427
[x] s2i-python-container https://github.com/sclorg/s2i-python-container/pull/678
[x] mysql-container https://github.com/sclorg/mysql-container/pull/371
[x] redis-container https://github.com/sclorg/redis-container/pull/173
[x] s2i-perl-container https://github.com/sclorg/s2i-perl-container/pull/305
[x] s2i-ruby-container https://github.com/sclorg/s2i-ruby-container/pull/547
[x] s2i-base-container - N/A. Neither s2i-base nor s2i-core containers have imagestreams.
[x] create github action to check, if streams are up to date

Closing all issues were covered.


The plugin is not firing off the script

backstretch-rails is loading as I can see in the console, but the plugin itself is not working in my view.
At the end of my body, I placed $.backstretch("<%= image_tag 'movie-photo.png' %>"); inside of a script tag, but the background isn't changing at all. I'm using jquery-rails 4.0.2.
Update: The gem is working when I place the code inside of the application.js, and also when I place the code inside of a stand-alone JS file. But either way, backstretch-js is overriding the background for all views/controllers. How can I stop it from going beyond a single page?

Try calling it after the document has fully loaded, a common jquery method of doing this is the following:
$( document ).ready(function() {
  console.log( "ready!" );
  $.backstretch("<%= image_tag 'movie-photo.png' %>");
});

I rendered a separate javascript file with the call method inside of it. That fixed the problem that I was having. Other than that, adding the javascript directly to the application.js caused an override of all wallpaper backgrounds. But, the solution that I came up scoped the script to a specific view. Thank you for helping me.

Your method works much better and it's cleaner. Thank you.

You're welcome :)


decreased muscle spindle number MP:0008486 - axiom

EQ for decreased muscle spindle number MP:0008486 currently uses:
'has part' some ('decreased amount' and towards some 'muscle spindle' and 'has modifier' some abnormal)
USE pattern:
'has_part' some ('decreased amount' and ('inheres_in' some %s) and ('has_modifier' some 'abnormal'))

Changed EQ to:
'has part' some
('decreased amount'
and ('inheres in' some 'muscle spindle')
and ('has modifier' some abnormal))


Add a documentation page on checkpointing

This page is meant to address the following:

Explain how to save and load a checkpoint
What to do if you don't know the original object, what to do if it can be one of multiple objects (e.g., a TrainState with or without batch_stats)
How to use it in multiprocess

Codecov Report

Merging #2530 (f9cde5d) into main (69163b9) will increase coverage by 0.42%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2530      +/-   ##
==========================================
+ Coverage   78.88%   79.31%   +0.42%
==========================================
  Files          48       49       +1
  Lines        5120     5139      +19
==========================================
+ Hits         4039     4076      +37
+ Misses       1081     1063      -18

Impacted Files
Coverage Δ

flax/errors.py
86.51% <0.00%> (-0.70%)
:arrow_down:

flax/core/nn/linear.py
42.34% <0.00%> (-0.52%)
:arrow_down:

flax/linen/module.py
92.59% <0.00%> (-0.22%)
:arrow_down:

flax/core/scope.py
89.72% <0.00%> (-0.07%)
:arrow_down:

flax/core/lift.py
95.81% <0.00%> (-0.07%)
:arrow_down:

flax/linen/normalization.py
97.10% <0.00%> (-0.05%)
:arrow_down:

flax/core/frozen_dict.py
96.19% <0.00%> (-0.04%)
:arrow_down:

flax/linen/summary.py
99.00% <0.00%> (-0.01%)
:arrow_down:

flax/linen/recurrent.py
100.00% <0.00%> (ø)

flax/linen/stochastic.py
96.55% <0.00%> (ø)

... and 8 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Hey @IvyZX, to enable jupytext for these notebook run:
jupytext --set-formats ipynb,md:myst docs/guides/use_checkpointing.ipynb

More info here:
https://flax.readthedocs.io/en/latest/advanced_topics/contributing.html#creating-new-notebooks

Update in https://github.com/IvyZX/flax/pull/3