Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

protobuf 3.20.1 update

See original GitHub issue

Seems like a problem with pip.

Same with bench dev (v1.8R1) and v1.7

After a build_sdcard.sh with a fresh Debian11 the setup stucks in „LND Credentials“ and after the 2 min the setup stopped:

Calling _provision.setup.sh for basic setup tasks ..
Follow in a new terminal with: 'tail -f raspiblitz.provision-setup.log'
***********************************************************
ERROR - please report to development team
***********************************************************
state(error) message(lnd-no-macaroons)
https://github.com/rootzoll/raspiblitz#support
command to shutdown --> off

Try to make new macaroons over the menu failed. (Found no files) lnd.initwallet.py:

admin@10.0.0.113:~ ₿ sudo /home/admin/config.scripts/lnd.initwallet.py new mainnet password
Traceback (most recent call last):
  File "/home/admin/config.scripts/lnd.initwallet.py", line 31, in <module>
    from lndlibs import walletunlocker_pb2 as lnrpc
  File "/home/admin/config.scripts/lndlibs/walletunlocker_pb2.py", line 14, in <module>
    from . import lightning_pb2 as lightning__pb2
  File "/home/admin/config.scripts/lndlibs/lightning_pb2.py", line 33, in <module>
    _descriptor.EnumValueDescriptor(
  File "/usr/local/lib/python3.9/dist-packages/google/protobuf/descriptor.py", line 755, in __new__
    _message.Message._CheckCalledFromGeneratedFile()
TypeError: Descriptors cannot not be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
 1. Downgrade the protobuf package to 3.20.x or lower.
 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates

I found a possible solution on GitHub here and here

I added pip3 install --upgrade protobuf==3.20.0 in the build_sdcard.sh on line 307

python_libs="grpcio==1.42.0 googleapis-common-protos==1.53.0 toml==0.10.2 j2cli==0.3.10 requests[socks]==2.21.0 protobuf==3.20.0"

The build with Python 3.9.2 and bench v1.7 seems to work. The 1.8r1 seems to work with a empty SSD, but it looks like it stucks with delete data and use blockchain. But maybe this is just a other problem.

To switch on Python 3.10.1 like in the guide seems to work aswell.

———————————————————- Update:

After further tests:

All tested builds works with the change in build_sdcard.sh

The problem with the stuck SSD delete is because a dead swap-delete process.

in v1.7 the delete can stopped with ctrg-c, after that the process continues. In 1.8r1 the setup is completely inscreen and didn’t changed to shell

If I delete it manually and then start the setup everything is fine.

Is this because the swapfile belongs to another pc? (Because the VM snapshots/backups and restore)