Error while register node #50
Comments
|
Hi! I am not being able to replicate this. Can you paste the logs of |
|
|
Ok. This is weird. Did your node remained hanged, and showing the register URL?
Thats a perfectly normal log message. Clients poke the server multiple times as part of their initialization... |
|
Yes, after showing the register URL, it hangs .. Nothing output |
|
Can you please send me the output of these commands? In the client:
In the server:
|
|
tailscale status: root@awxt-aaaw:~# tailscale status
Logged out.
Log in at: http://127.0.0.1:8000/register?key=6b81abd8292b2edfe86720f53c25f4fa3c968974df844b9b99238f800588d537headscale -n wentx nodes list -o json : ubuntu@VM-4-11-ubuntu:~$ sudo headscale -n wentx nodes list -o json
[
{
"ID": 1,
"MachineKey": "6b81abd8292b2edfe86720f53c25f4fa3c968974df844b9b99238f800588d537",
"NodeKey": "523aec74972f1477d63712705de9db24d32f8852765170f1ac72b446fd38cb50",
"DiscoKey": "89e37ceee33501990c4becce8ecbf52f2c49a65757a4b81a7f8a3c8e63c4f450",
"IPAddress": "100.127.105.139",
"Name": "awxt-aaaw",
"NamespaceID": 1,
"Namespace": {
"ID": 0,
"CreatedAt": "0001-01-01T00:00:00Z",
"UpdatedAt": "0001-01-01T00:00:00Z",
"DeletedAt": null,
"Name": ""
},
"Registered": true,
"RegisterMethod": "cli",
"AuthKeyID": 0,
"AuthKey": null,
"LastSeen": "2021-07-14T23:26:44.203438+08:00",
"Expiry": "0001-01-01T08:05:43+08:05",
"HostInfo": {
"OS": "linux",
"GoArch": "amd64",
"NetInfo": {
"PCP": false,
"PMP": false,
"UPnP": false,
"WorkingUDP": true,
"DERPLatency": {
"1-v4": 0.214764163,
"2-v4": 0.136939201,
"3-v4": 0.330014741,
"4-v4": 0.259974053,
"5-v4": 0.315374518,
"6-v4": 0.340824564,
"7-v4": 0.248941838,
"8-v4": 0.255692985,
"9-v4": 0.176007433
},
"HairPinning": true,
"WorkingIPv6": false,
"PreferredDERP": 2,
"MappingVariesByDestIP": false
},
"Hostname": "awxt-aaaw",
"Services": [
{
"Port": 64569,
"Proto": "peerapi4"
}
],
"OSVersion": "Ubuntu 18.04.5 LTS (Bionic Beaver); kernel=4.15.0-144-generic; container",
"IPNVersion": "1.10.1-t6b6016130-g49e1dcc20",
"BackendLogID": "64b9694a57e0e228a490a1f35cc30f90e8c0ee747e4354dfc0fe283511c531e6"
},
"Endpoints": [
"122.228.235.37:41641",
"10.10.10.9:41641"
],
"EnabledRoutes": null,
"CreatedAt": "2021-07-13T14:53:17.215468+08:00",
"UpdatedAt": "2021-07-14T23:26:44.204246+08:00",
"DeletedAt": null
}
] |
|
I have been able to replicate it when running the tailscale client in the same machine as the headscale server. Is that your case? |
|
Can you try
|
Nop
It hangs..
|
|
Does headscale have any dependencies? I'v installed wireguard on my headscale vm. I'll try without wireguard |
|
It just the same.. tailscale hangs I can grant an access to my vm. And you can try it yourself.... |
|
I will contact you via mail
…On Thu, 15 Jul 2021 at 05:16, wentx ***@***.***> wrote:
It just the same.. tailscale hangs
I can grant an access to my vm. And you can try it yourself....
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABMGQ5546NHCNPLKJPFFMDTXZHHHANCNFSM5AIMM52A>
.
|
|
The same problem on different host. Both versions are the latest main branch. |
|
@faicker do you have nginx in front? |
|
no. @juanfont |
|
I've encountered the same problem, and it turns out it's because I have a |
|
I am running into a similar issue when registering many nodes in succession. It seems to me like there is a deadlock somewhere, potentially in the HTTP server. What I have observed is: I try to join 5 clients at the same time, 3 succeeds while 2 hangs, if I restart It does not always succeed tho, so I suspect that if you restart and already connected clients try to talk to I tried to join about 13 hosts and I think I had to restart it 8-9 times over 20 minutes to get them all in. |
+1 Facing the same issue |
|
@bharathmsd7 @momaek @faicker Can you please try with v0.5.0? https://github.com/juanfont/headscale/releases/tag/v0.5.0 |
This works man, Deadlock is not occurring now. |
|
Ah yes, I see what you mean, it get it on some of the first joined nodes. I will try to do a dive into it, it would definitively benefit us with some integration tests, just need to find a clever way to wire them up. |
|
This is fixed now in 0.7. |
|
For the record, I ran into the same issue as OP using headscale |
I've setup headscale(v0.3.3) on my Ubuntu 18.04 VM.
This is my
config.json:{ "server_url": "http://127.0.0.1:8000", "listen_addr": "0.0.0.0:8000", "private_key_path": "/etc/wireguard/privatekey", "derp_map_path": "derp.yaml", "ephemeral_node_inactivity_timeout": "30m", "db_type": "postgres", "db_host": "localhost", "db_port": 5432, "db_name": "headscale", "db_user": "headscale", "db_pass": "BZv1XGkrC7dlzjudJy0J", "tls_letsencrypt_hostname": "", "tls_letsencrypt_cache_dir": ".cache", "tls_letsencrypt_challenge_type": "HTTP-01", "tls_cert_path": "", "tls_key_path": "", "acl_policy_path": "" }And I've created a namespace.
When I try to register a node from another vm, I got an output key and I manual registered on my headscale vm:
But nothing changed on my tailscale vm. screenshot below:
No success response
The text was updated successfully, but these errors were encountered: