LND service stuck Syncing to graph and chain for days

I’ve looked around the forum here and found the post below but I don’t know where to begin with this Chantools fix… I’m not a coder but can follow clear instructions

It’s been spinning for days… I’ve rebooted, stopped and started… did a reset… what do I do from here… I can send logs to Start9 support

Really appreciate any help

p.s. it’d be amazing if you could code in zaps on this forum? Happy to tip great advice

Syncing to graph for a long period of time could mean many things…

…it could mean you’ve only just installed LND, you have no bootstrapped peers and you should add one manually to see and sync the graph…

…or it could mean LND is stuck after starting up before Core was ready, in which case restarting LND would generally get it unstuck…

…or there could be a serious error being shown in the logs over and over which you should look for an report here.

It stopped ages ago and I rebooted it and that seemed to work… then again a few weeks ago I think, and again I rebooted and it seemed to work… but this time has been since last week

I’ve had this node a looooong time… this isn’t a new install of LND, unless you’re counting the reset…

It’s only using 40% of the disk space

“you have no bootstrapped peers” - is this channels I’ve opened with other nodes? I have at least 6… it was twice that a year or so ago but some have dropped off

I’ve just hit Restart again for the sake of it and it’s back to “Syncing to graph and chain”… been like that for 15 minutes now

I’ve got the logs open but honeslty can’t really see anything glowing in red and nothing obviously screams “Error”

I understand you’ve now sent logs to George. :ok_hand:

1 Like

The issue is LND kept restarting because it couldn’t communicate with the system dns server to resolve bitcoind.ebmassy:

unable to determine if wallet is synced: failed to parse address lookup bitcoind.embassy on 172.18.0.1:53: read udp 172.18.0.149:56271->172.18.0.1:53: read: connection refused

It’s not that the DNS resolver couldn’t resolve it, but the connection to the DNS server to even ask was refused.
Developer comments: Something malfunctioning with the systemd dns resolver, possibly binary corruption. Reflash as suggested solution. So I instructed @Chiefmonkey to reflash the OS:

  1. Follow the flashing guide to burn the latest StartOS iso to a usb thumb drive
  2. boot the thumb drive in the server. It should boot to the StartOS live installer
  3. You can either plug in a monitor, keyboard & mouse to use “Kiosk mode” to reinstall it, or you can visit http://start.local in a webbrowser from another computer on the lan to see the installer web-UI
  4. Choose Re-Install StartOS
  5. It will instruct you to remove the USB thumb drive and reboot
  6. When you reboot, re-visit http://start.local (or you’ll see the setup UI now in Kiosk mode)
  7. At that setup screen, choose Recover > Use Existing Drive
  8. Select the disk and set your password

Then he’ll be back in action (in theory). Now we await Chiefmonkey’s feedback!

I have flashed the usb with the latest iso: startos-0.3.5.1-39de098_x86_64-nonfree.iso

2 usb drives in fact… mac didn’t recognise them after flashin but aparently thats normal

Put them into my start9 in the fast slot, the blue one, reboot and nothing ???

what to do now?

how to I change the bios of a start9 to boot off the usb?

Your Mac not recognizing the drive after it’s been flashed in normal, yes.

With the booting of the USB… can you remind me what hardware this is? One of the challenges with posting for help in multiple locations is that it’s hard to keep track of everything when it’s spread all over.

I could have sworn you’ve previous showed me a Raspberry Pi. If so, while George’s steps above would be correct for most people, you’d need to do something slightly different… Flashing a microSD card.

Could you help me remember?

Apologies… I’ve committed the cardinal sin of posting in multiple places… really don’t want to be a pain… just want to get this fixed and get on

Is it a Raspberry Pi… I honestly couldn’t say… possibly… I got a pretty early one… one of the first to get a metal case after you stopped selling the transparent plastic housing because they kept melting

But then later had to transfer the guts to another new metal case in order to house the additional hardrive

I’ve flashed 2 usb’s not a microSD… and the Start9 just boots up as usual… I’ve tried both in blue and black slots… Start9 doesn’t seem to recognise them

They are definitely flashed correctly though… as previously mentioned, the mac doesn’t even see them after flashing with the startos-0.3.5.1-39de098_x86_64-nonfree.iso

So I think everything is OK so far

Just need the device to boot off one of the usb’s now

George has been a great help btw

This is no criticism… he’s been awesome… I just want to get on… time is scarce and I am not a coder and doing this stuff is taxing

George is awesome

Got it. The confusion was down to the fact that we now assume people aren’t running these older RPis for Bitcoin… we very strongly recommend against it since they haven’t really be able to run Bitcoin adequately for over a year now. I haven’t seen the logs, but this could well be a factor in what has happened to your LND.

In any case, the flashing guide for a RPi is this one:
https://docs.start9.com/0.3.5.x/flashing-guides/os-pi

While you’ll continue having problems with a Bitcoin stack, going through with this reflash may be sufficient to get things back on track for now.

Assuming your data is on an external drive…

…which I assume it is since you have what’s circle in green, so the drive must be off-screen…

you can quite easily flash the microSD. But if the microSD really is 4 years old, it might need to be swapped for a new one.

This means no USB, and no booting from the USB.

I flashed the MicroUSB… the one you guys issued years ago… stucj it in the Blue slot and yeah It’s recognised it and booted … I did a ReBuild and it bleeped differently than usual

So it’s finished that and I’m now back to this screen

I guess I need to wait another 24 hours to let the LND catch up right?

On a seperate note

If this machine is now dead/dying… always going to fall over like Biden… do I need to buy the latest and greatest?

MEGA

Make Embassy Great Again

Seriously… do you recommend I buy the Server Pure OR should I wait for the full Router to come out and how easy is it to upgrade from the old rattler to the new shiny thing?

We’re going to be building the new Plebeian app for Start9 soon so going to be testing it

It’d be nice to see it there in the Marketplace

Re: LND… I’m not sure. If it’s working not and progressing, and if it’s finished by now, then we’re good. If not, it’s time for round 2.

Re: New machine… Either the One or the Pure are fine for a predominantly or only Bitcoin us. Wouldn’t matter too much which you get. I’d be willing to bet a small amount of money that your RPi will be dead before the router is born… but the two are unrelated otherwise. Migration is simple between the two, there are guides, but with a powerful machine it can be fun to start over and watch in sync in a day.

Re: For Plebeian app, are the right people in the right places to learn and ask how to do this? Main place is this: https://matrix.to/#/#dev-service-packaging:matrix.start9labs.com

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.