#Failed to claim node for an unknown reason. This usually means either networking problems or a bug.

1 messages · Page 1 of 1 (latest)

somber blade
#

Hmm, hey! exit code 7, if the claim script used curl, should just be CURLE_COULDNT_CONNECT which is pretty generic...

somber blade
#

Very weird.... Is this behaviour consistent? Could this be caused by a firewall or similar?

#

Hmmmm 🤔

#

Okay, so netdata is installed there. Can you just run the claim script by itself (not from within kickstart) to see: /usr/sbin/netdata-claim.sh -token=XXXXXX -rooms=XXXXX -url=https://app.netdata.cloud ?

Netdata: Monitoring and troubleshooting transformed.

Slash your time to detect, troubleshoot and resolve infrastructure performance anomalies. Netdata: architected for speed, automated for easy.

#

ok, let me see if we can get some more info from it..

#

Can you check with adding -verbose ?

somber blade
#

all right, thanks! There should be some more info with that !

somber blade
#

Can you also do a host app.netdata.cloud ?

somber blade
#

Ok, thanks seems normal

#

Have you checked the claim script with -verbose ?

somber blade
#

Yes, indeed weird....

frail plover
#

👀

#

Actively looking into it @pale grail apologies for the inconvenience

frail plover
#

Hello @pale grail so we have potentially spotted the issue here. It seems that it is related with ipv4/ipv6 usage where in the latter case we have a bug.
We're working on some fixes that we expect to be released today 👍
So I will ping you back again in this thread for updates when all is in place.

#

Thanks a lot again for bringing this to our attention. Let's see that this gets resolved.

frail plover
#

Hey @pale grail 👋
After rolling out some relevant fixes over the last few days I wanted to ask whether you're still facing this issue.

frail plover
#

Feel free to drop a message here to this thread if you notice it coming back (I doubt it will). The issue had to do with how our Cloud application was handling ipv4/ipv6

wispy fox