-
Notifications
You must be signed in to change notification settings - Fork 889
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connectd hanging while being unable to connect to peers #7462
Comments
So looks like #7365 didn't fix anything for you... |
This is more of a medium-sized node and wasn't running into the CPU usage that PR addresses, so I'm not sure. Also the other machine I tested on has a single signet channel and was experiencing the issue described above. |
OK sth different then, we'll go and test #7365 |
I can reproduce that problem on a fresh, new node:
For convenience to reproduce this I created a little script. #!/usr/bin/env python3
import json
import subprocess
with open('nodes.json') as f:
nodes = json.load(f)["nodes"]
print(f"Got {len(nodes)} nodes")
with_address = []
for node in nodes:
if "addresses" not in node or len(node["addresses"]) == 0:
continue
with_address.append(node)
print(f"{len(with_address)} with address")
ipv4 = []
for node in with_address:
for address in node["addresses"]:
if address["type"] != "ipv4":
continue
ipv4.append(f"{node['nodeid']}@{address['address']}:{address['port']}")
print(f"{len(ipv4)} with IPV4 address")
for (i, address) in enumerate(ipv4):
print(f"Connecting to {i+1}/{len(ipv4)}: {address}")
res = subprocess.Popen(
f"timeout 10 lightning-cli connect {address}",
shell=True,
stdout=subprocess.PIPE,
).stdout.read()
try:
print(json.dumps(
json.loads(res),
indent=4,
))
except:
print("Connect timed out") Edit: This is definitely a regression since |
Can confirm the original post. Channel main node <-> test node V24.05 <-> V24.05 no problems V24.05 <-> Master same problems When I return to v25.05 everything is fine again |
If we need to iterate forward to find a timestamp (only happens if we have gossip older than 2 hours), we didn't exit the loop, as it didn't actually move the offset. Fixes: ElementsProject#7462 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Added the one line in the pull request into gossmap.c and it solved the issue for me! |
Running master at 029034a. CLN can't connect to any peers and
lightning_connectd
seems to hang at 100% CPU.When trying to shut down CLN,
lightningd
andlightning_connectd
both hang at 100% CPU each and thestop
command also hangs indefinitely. I have to usekill
to end those processes in able to restart CLN.There doesn't seem to be anything useful in
debug.log
to share.CLN config includes:
On a different machine, I am able to reproduce this without those experimental config options.
The text was updated successfully, but these errors were encountered: