[stork-users] problems re-registering agent
DDFR | Ronald Blaas
ronald.blaas at ddfr.nl
Wed Aug 28 07:42:21 UTC 2024
Glad to be of help 🙂
For now I have manually authorized my agents.
Thanks for opening the thread
Regards,
Ronald
________________________________
From: Slawek Figiel <slawek at isc.org>
Sent: Tuesday, August 27, 2024 18:21
To: DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>; stork-users at lists.isc.org <stork-users at lists.isc.org>
Subject: Re: [stork-users] problems re-registering agent
Ronald,
I analyzed your problem, and it seems to be a bug in the Stork agent
that we introduced, together with the improvements to the registration
process in recent releases.
Previously, you could start the Stork agent and then perform the
registration using the server token. In that case, the Stork agent
process had been responding correctly to the ping request.
Now, you cannot run the Stork agent without GRPC credentials. So, no
process would listen to the ping request, and the ping fails.
The good news is the registration artifacts are created before the ping
check. So, you can use your Stork agent installation even if the ping
returns an error.
I opened https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fstork%2F-%2Fissues%2F1491&data=05%7C02%7Cronald.blaas%40ddfr.nl%7Cdfc0ae462e344f97ff7908dcc6b4641c%7C61b60fb772d74ba78225d9b5369d780a%7C0%7C0%7C638603725334790649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=cqcg7lq2MZErMi9CVhwaR94qyPV5N5bWMcYDJ6d3zyo%3D&reserved=0<https://gitlab.isc.org/isc-projects/stork/-/issues/1491> to
solve the problem.
Regards,
Slawek Figiel
On 27/08/2024 16:05, DDFR | Ronald Blaas wrote:
> Hi Slawek,
>
> Did find this in the syslog from the stork server:
> Aug 27 16:02:24 stork-test stork-server[1011]: time="2024-08-27
> 16:02:24" level="error" msg="failed to ping the Stork agent
> host.domain.xx:8080: grpc manager is unable to re-establish connection
> with the agent host.domain.xx:8080: rpc error: code = Unavailable desc =
> connection error: desc = \"transport: Error while dialing: dial tcp
> xx.xx.xx.xx:8080: connect: connection refused\"" file="
> machines.go:569 "
>
>
> Regards,
>
> Ronald
>
> ------------------------------------------------------------------------
> *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of
> DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
> *Sent:* Tuesday, August 27, 2024 15:24
> *To:* Slawek Figiel <slawek at isc.org>; stork-users at lists.isc.org
> <stork-users at lists.isc.org>
> *Subject:* Re: [stork-users] problems re-registering agent
> Here is sone info:
>
> stork-agent register
> >>> Enter the URL of the Stork server: https://xxxxx8080
> >>> Enter the Stork server access token (optional):
> >>> Enter IP address or FQDN of the host with Stork agent (for the
> Stork server connection) [xxxxxxx]:
> >>> Enter port number that Stork Agent will listen on [8080]:
> INFO[2024-08-27 15:01:14] register.go:34 Forced agent
> certificates regeneration.
> INFO[2024-08-27 15:01:14] register.go:342
> =============================================================================
> INFO[2024-08-27 15:01:14] register.go:343 AGENT TOKEN:
> 7A25420D275543E91CEB4B645DED30E6DDAD2C3F8C485E1C156239DBF856F98E
> INFO[2024-08-27 15:01:14] register.go:344
> =============================================================================
> INFO[2024-08-27 15:01:14] register.go:349 Machine will be
> automatically registered using the server token
> INFO[2024-08-27 15:01:14] register.go:350 Agent token is
> printed above for informational purposes only
> INFO[2024-08-27 15:01:14] register.go:351 User does not need
> to copy or verify the agent token during registration via the server token
> INFO[2024-08-27 15:01:14] register.go:352 It will be sent to
> the server but it is not directly used in this type of machine registration
> INFO[2024-08-27 15:01:14] register.go:361 Try to register
> agent in Stork Server
> INFO[2024-08-27 15:01:14] register.go:212 Machine registered
> INFO[2024-08-27 15:01:14] register.go:233 Stored agent-signed
> cert and CA cert
> ERRO[2024-08-27 15:01:14] register.go:390 Retrying ping 1/3
> due to error error="problem pinging machine: Cannot ping
> machine"
> ERRO[2024-08-27 15:01:16] register.go:390 Retrying ping 2/3
> due to error error="problem pinging machine: Cannot ping
> machine"
> ERRO[2024-08-27 15:01:20] register.go:395 Cannot ping machine
> error="problem pinging machine: Cannot ping
> machine"
> FATA[2024-08-27 15:01:20] main.go:321 Registration failed
>
>
> In stork I do see the agent appearing.. (but not communicating)
>
> Syslog not showing anything helpfull
>
> If needed I can test just about anything (as this is a test setup)
>
> Regards,
>
> Ronald
>
> ------------------------------------------------------------------------
> *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of
> DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
> *Sent:* Tuesday, August 27, 2024 14:42
> *To:* Slawek Figiel <slawek at isc.org>; stork-users at lists.isc.org
> <stork-users at lists.isc.org>
> *Subject:* Re: [stork-users] problems re-registering agent
> I can however reproduce the problem on a test system.
>
> Any particular logging your after ?
>
> Regards,
> Ronald
>
> Met vriendelijke groet,
>
>
> Ronald Blaas
>
>
>
> ------------------------------------------------------------------------
> *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of
> DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
> *Sent:* Tuesday, August 27, 2024 12:24
> *To:* Slawek Figiel <slawek at isc.org>; stork-users at lists.isc.org
> <stork-users at lists.isc.org>
> *Subject:* Re: [stork-users] problems re-registering agent
> Hi Slawek,
>
> Unfortunately, I cannot.
>
> I do not see the same errors in the syslog.
>
> I only saw the error while running stork-agent register
>
>
> Is there a way I can check the server token?
>
> Maybe the token has changed (or I just made a typo)
>
> NOTE: when entering the token whilst registering the input is not shown.
> This is expected behavior ?
>
>
>
> Also good to note. When I upgraded my second dhcp server it did connect
> automatically but I had to authenticate the client again.
>
> This was unexpected as I have the server token configured in the agent.env
>
>
> Regards,
>
>
> Ronald
>
>
>
> ------------------------------------------------------------------------
> *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of
> Slawek Figiel <slawek at isc.org>
> *Sent:* Tuesday, August 27, 2024 12:14
> *To:* stork-users at lists.isc.org <stork-users at lists.isc.org>
> *Subject:* Re: [stork-users] problems re-registering agent
> Hello Roland!
>
> I'm glad to hear your original problem has been solved.
>
> Could you provide some logs generated when you try registering the
> machine using the server token?
>
> Regards,
> Slawek Figiel
>
> On 27/08/2024 12:02, DDFR | Ronald Blaas wrote:
> > And just to be complete
> >
> > I am registering with a server token.
> >
> >
> > I have now tried registering the agent without a token which is working
> > just fine (after authorizing the agent in stork server)
> >
> > Still wondering why the server token option is not working / ping not
> > working
> >
> > Regards,
> >
> > Ronald
> >
> > ------------------------------------------------------------------------
> > *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of
> > DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
> > *Sent:* Tuesday, August 27, 2024 11:49
> > *To:* Stork-users <stork-users at lists.isc.org>
> > *Subject:* Re: [stork-users] problems re-registering agent
> > So I am now a step further.
> >
> > I had a mismatch in version number (server vs agent)
> > Agent was upgrade to v1.18 whilst server was still on v1.15
> >
> > After upgrading the server I see the token being installed on the client
> > but no I am facing an issue saying cannot ping machine.
> >
> > I can ping the server from client as well as the client from server.
> > So i am a bit confused what is going wrong here.
> >
> > Any insights?
> >
> > Regards,
> > ROnald
> >
> >
> >
> > ------------------------------------------------------------------------
> > *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of
> > DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
> > *Sent:* Tuesday, August 27, 2024 10:47
> > *To:* Stork-users <stork-users at lists.isc.org>
> > *Subject:* [stork-users] problems re-registering agent
> > Hi all,
> >
> > Today I updated my ubuntu system and with the update kea (and stork
> > agent) have been updated.
> > The result is that stork is able to see the status of kea load balancing
> > but is unable to communicate with the stork agent.
> >
> > After some investigation it appears that there is a problem with the
> > certificate.
> >
> > I am trying to re-register the agent but running into an error:
> >
> > ERRO[2024-08-27 10:38:31] register.go:368 Problem registering
> > machine error="missing serverCertFingerprint in
> > response from server for registration request"
> > FATA[2024-08-27 10:38:31] main.go:321 Registration failed
> >
> > Any help how to fix this?
> >
> > Kind regards,
> >
> > Ronald
> >
> --
> Stork-users mailing list
> Stork-users at lists.isc.org
> https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fstork-users&data=05%7C02%7Cronald.blaas%40ddfr.nl%7Cdfc0ae462e344f97ff7908dcc6b4641c%7C61b60fb772d74ba78225d9b5369d780a%7C0%7C0%7C638603725334800523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=9ZW6Z8jfcptvNGCLB4wQ1nQtJxFO4zJkvHapDOU2pFc%3D&reserved=0<https://lists.isc.org/mailman/listinfo/stork-users> <https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fstork-users&data=05%7C02%7Cronald.blaas%40ddfr.nl%7Cdfc0ae462e344f97ff7908dcc6b4641c%7C61b60fb772d74ba78225d9b5369d780a%7C0%7C0%7C638603725334808364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=loBbVXUG5KD%2FbsNgkz0%2FCNShXxKKC1T7BTsjt9a%2F72c%3D&reserved=0<https://lists.isc.org/mailman/listinfo/stork-users>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20240828/ed63163c/attachment-0001.htm>
More information about the Stork-users
mailing list