[stork-users] registration error 'cannot ping machine'
Slawek Figiel
slawek at isc.org
Mon Dec 9 10:25:50 UTC 2024
Hello!
I see in the attached logs that your network is configured this way: You
have two different hosts one with the Stork agent and second with the
Stork server.
The Stork agent hostname is "bind9B.fantinibakery.com," port 8080, and
the Stork server IP address is "10.1.3.3," port 8080.
You checked the connection from the Stork agent to the Stork server, and
it works using ping.
Now, please verify you can ping the Stork agent from the Stork server
host using the hostname assigned to the Stork agent:
"bind9B.fantinibakery.com".
I'm pretty sure this hostname is incorrect, and it cannot be resolved in
your internal network. Please verify if it is valid.
Regards
Slawek Figiel
On 07/12/2024 08:31, fbcadmin wrote:
> for #2, I assume isc-kea-ctrl-agent will need to be installed? I'll try
> now.............
>
> After installing isc-kea-ctrl-agent and running stork-agent register ,
> i got the same ping error when trying to
>
>
> *isc-kea-ctrl-agent.service - Kea Control Agent
> Loaded: loaded (/lib/systemd/system/isc-kea-ctrl-agent.service;
> enabled; preset: enabled)
> Active: active (running)since Fri 2024-12-06 17:58:56 EST; 8h ago
> Docs: man:kea-ctrl-agent(8)
> Main PID: 40584 (kea-ctrl-agent)
> Tasks: 5 (limit: 231595)
> Memory: 1.5M
> CPU: 9ms
> CGroup: /system.slice/isc-kea-ctrl-agent.service
> `-40584 /usr/sbin/kea-ctrl-agent -c /etc/kea/kea-ctrl-
> agent.conf
>
> Dec 06 17:58:56 bind9B systemd[1]: Started isc-kea-ctrl-agent.service -
> Kea Control Agent.
> Dec 06 17:58:56 bind9B kea-ctrl-agent[40584]: INFO
> CTRL_AGENT_HTTP_SERVICE_STARTED HTTP service bound to address
> 127.0.0.1:8000
> Dec 06 17:58:56 bind9B kea-ctrl-agent[40584]: INFO DCTL_CONFIG_COMPLETE
> server has completed configuration: listening on 127.0.0.1, port 8000,
> control sockets: d2 dhcp4 dhcp6, 0 lib(s):
> Dec 06 17:58:56 bind9B kea-ctrl-agent[40584]: INFO CTRL_AGENT_STARTED
> Kea Control Agent version 2.6.1 started
>
> # su stork-agent -s /bin/sh -c 'stork-agent register --server-url
> http://10.1.3.3:8080'
> >>> Enter the Stork server access token (optional):
> >>> Enter IP address or FQDN of the host with Stork agent (for the
> Stork server connection) [bind9B.fantinibakery.com]:
> >>> Enter port number that Stork Agent will listen on [8080]:
> INFO[2024-12-06 18:00:30] register.go:95 Forced agent
> certificates regeneration.
> INFO[2024-12-06 18:00:30] register.go:398
> =============================================================================
> INFO[2024-12-06 18:00:30] register.go:399 AGENT TOKEN:
> 66B400430BCA152BFBEF023FAE9CB9DC0C5416FB600A3ABF74609CA1D3333471
> INFO[2024-12-06 18:00:30] register.go:400
> =============================================================================
> INFO[2024-12-06 18:00:30] register.go:405 Machine will be
> automatically registered using the server token
> INFO[2024-12-06 18:00:30] register.go:406 Agent token is
> printed above for informational purposes only
> INFO[2024-12-06 18:00:30] register.go:407 User does not need
> to copy or verify the agent token during registration via the server token
> INFO[2024-12-06 18:00:30] register.go:408 It will be sent to
> the server but it is not directly used in this type of machine registration
> INFO[2024-12-06 18:00:30] register.go:416 Try to register
> agent in Stork Server
> INFO[2024-12-06 18:00:30] register.go:273 Machine registered
> INFO[2024-12-06 18:00:30] register.go:294 Stored agent-signed
> cert and CA cert
> ERRO[2024-12-06 18:00:30] register.go:450 Retrying ping 1/3
> due to error error="problem pinging machine: Cannot ping machine"
> ERRO[2024-12-06 18:00:32] register.go:450 Retrying ping 2/3
> due to error error="problem pinging machine: Cannot ping machine"
> FATA[2024-12-06 18:00:36] main.go:320 Registration failed
> error="cannot ping machine: problem pinging machine: Cannot
> ping machine"
>
>
> On 12/6/24 04:29, Slawek Figiel wrote:
>>
>> Hello!
>>
>> >> I get the following when trying to register a bind9 system to stork:
>> >> INFO[2024-12-04 12:34:54] register.go:273 Machine registered
>> >> FATA[2024-12-04 12:36:16] main.go:320 Registration
>> >> failed error="cannot ping machine: problem
>> >> pinging machine: Cannot ping machine"
>>
>> It may be a networking issue.
>>
>> Your agent was able to establish a connection to the Stork server,
>> register itself, and send a request for ping.
>> But the Stork server couldn't connect to the Stork agent. The firewall
>> on the Stork server or agent machines may have caused this.
>>
>> Please check that:
>>
>> 1. Try ping the agent machine/host from the server machine/host to
>> verify the connection works. If it fails, it is a network issue.
>> 2. Run the server and agent, authorize the agent, and verify if the
>> server can fetch the agent's state. If it passes, then the observed
>> problem was a temporary network issue or a bug in the agent (if the
>> problem is repeatable).
>>
>> I'll wait for your feedback.
>>
>> > also isc-kea-ctrl-agent is not installed. Is that needed?
>>
>> The Kea Control Agent is mandatory only if you want to monitor Kea
>> daemons. It is not necessary to monitor BIND 9.
>>
>> Regards,
>> Slawek Figiel
>>
>>
>> On 05/12/2024 23:40, fbcadmin wrote:
>>> also isc-kea-ctrl-agent is not installed. Is that needed?
>>>
>>> On 12/5/24 16:53, fbcadmin wrote:
>>>>
>>>> Hello
>>>>
>>>> I get the following when trying to register a bind9 system to stork:
>>>>
>>>>
>>>> su stork-agent -s /bin/sh -c 'stork-agent register --server-url
>>>> http://10.1.3.3:8080'
>>>> >>> Enter the Stork server access token (optional):
>>>> >>> Enter IP address or FQDN of the host with Stork agent (for the
>>>> Stork server connection) [bind9B.test.com]:
>>>> >>> Enter port number that Stork Agent will listen on [8080]:
>>>> INFO[2024-12-04 12:34:54] register.go:95 Forced agent
>>>> certificates regeneration.
>>>> INFO[2024-12-04 12:34:54] register.go:398
>>>> =============================================================================
>>>> INFO[2024-12-04 12:34:54] register.go:399 AGENT TOKEN:
>>>> D8E79ACBBC7620AE16E2C21EA002163D28974A0E0AF346B9D309F7355D4835C5
>>>> INFO[2024-12-04 12:34:54] register.go:400
>>>> =============================================================================
>>>> INFO[2024-12-04 12:34:54] register.go:405 Machine will be
>>>> automatically registered using the server token
>>>> INFO[2024-12-04 12:34:54] register.go:406 Agent token is
>>>> printed above for informational purposes only
>>>> INFO[2024-12-04 12:34:54] register.go:407 User does not
>>>> need to copy or verify the agent token during registration via the
>>>> server token
>>>> INFO[2024-12-04 12:34:54] register.go:408 It will be sent
>>>> to the server but it is not directly used in this type of machine
>>>> registration
>>>> INFO[2024-12-04 12:34:54] register.go:416 Try to register
>>>> agent in Stork Server
>>>> INFO[2024-12-04 12:34:54] register.go:273 Machine registered
>>>> INFO[2024-12-04 12:34:54] register.go:294 Stored agent-
>>>> signed cert and CA cert
>>>> ERRO[2024-12-04 12:35:14] register.go:450 Retrying ping
>>>> 1/3 due to error error="problem pinging machine:
>>>> Cannot ping machine"
>>>> ERRO[2024-12-04 12:35:36] register.go:450 Retrying ping
>>>> 2/3 due to error error="problem pinging machine:
>>>> Cannot ping machine"
>>>> FATA[2024-12-04 12:36:16] main.go:320 Registration
>>>> failed error="cannot ping machine: problem
>>>> pinging machine: Cannot ping machine"
>>>>
>>>>
>>>> Package: isc-stork-agent Version: 2.0.0.241112163127 , Maintainer:
>>>> Stork team <stork-users at lists.isc.org , APT-Sources: https://
>>>> dl.cloudsmith.io/public/isc/stork/deb/debian bookworm/main amd64
>>>> Packages
>>>>
>>>> # apt show bind9
>>>> Package: bind9
>>>> Version: 1:9.18.31-1+0~20241110.101+debian12~1.gbpbe8143
>>>> Priority: optional
>>>> Section: net
>>>> Maintainer: Debian DNS Team <team+dns at tracker.debian.org>
>>>>
>>>>
>>>> opsys = debian 12
>>>>
>>>>
>>>> Any suggestions on how to fix this? I am able to register clients
>>>> from kea dhcp systems .
>>>>
>>>>
>>>>
>>>>
>>>
>>
More information about the Stork-users
mailing list