Closed abhiShandy closed 4 years ago
I am having the same issues now for a few days, have tried resetting tor and rebooting but no luck. Was working excellent until then
If you are having this issue, see if it was for the same reason as me
There's multiple issues going on here. The first issue is the clock is always wrong on the Pi 4 on boot. There is no Real Time Clock saved on the hardware, so Pi depends on a network time server. I believe some script is writing to systemd-timesyncd.service unit file which causes systemd to refuse to start the unit:
admin@myNode:/mnt/hdd/mynode/bitcoin $ sudo systemctl start systemd-timesyncd Warning: The unit file, source configuration file or drop-ins of systemd-timesyncd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
To work around this every time my Pi boots MyNode: (The below is assuming you already worked around issue #133 by commenting the line in mynode_startup.sh and have working nameservers in /etc/resolv.conf ) sudo systemctl daemon-reload sudo systemctl start systemd-timesyncd The clock now gets set correctly.
After this point, it seems Tor, then LND both may need manual restarts... or I'm not waiting long enough. I wasn't able to find what writes to the systemd timesyncd unit file as the text timesyncd doesn't occur in /usr/bin - possibly a batch copy.
sudo systemctl start tor (Wait a few minutes) sudo systemctl restart lnd The unlock script is already waiting and runs automatically in about 30 sec after this and LND starts up.
Tor is not on a much newer version. Closing.
Sometimes resetting Tor from the settings page solves the issue.