<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi!</p>
<p><br>
</p>
<p>ping from server to agent host works. I tried lower and
uppercase B [ the case should not matter...] . I also verified
the IP address of the agent host<br>
</p>
<p><br>
</p>
<p><span style="font-family:monospace"><span
style="color:#54ff54;background-color:#ffffff;">root</span><span
style="color:#000000;background-color:#ffffff;">@</span><span
style="color:#b21818;background-color:#ffffff;">stork</span><span
style="color:#000000;background-color:#ffffff;">:</span><span
style="color:#18b218;background-color:#ffffff;">[</span><span
style="color:#ffff00;background-color:#ffffff;">~</span><span
style="color:#18b218;background-color:#ffffff;">]</span><span
style="color:#000000;background-color:#ffffff;">:# ping -c 3
bind9b.fantinibakery.com </span><br>
PING bind9b.fantinibakery.com (10.1.3.43) 56(84) bytes of data.
<br>
64 bytes from bind9b.fantinibakery.com (10.1.3.43): icmp_seq=1
ttl=64 time=0.260 ms
<br>
64 bytes from bind9b.fantinibakery.com (10.1.3.43): icmp_seq=2
ttl=64 time=0.212 ms
<br>
64 bytes from bind9b.fantinibakery.com (10.1.3.43): icmp_seq=3
ttl=64 time=0.109 ms
<br>
<br>
--- bind9b.fantinibakery.com ping statistics ---
<br>
3 packets transmitted, 3 received, 0% packet loss, time 2061ms
<br>
rtt min/avg/max/mdev = 0.109/0.193/0.260/0.063 ms
<br>
<span style="color:#54ff54;background-color:#ffffff;">root</span><span
style="color:#000000;background-color:#ffffff;">@</span><span
style="color:#b21818;background-color:#ffffff;">stork</span><span
style="color:#000000;background-color:#ffffff;">:</span><span
style="color:#18b218;background-color:#ffffff;">[</span><span
style="color:#ffff00;background-color:#ffffff;">~</span><span
style="color:#18b218;background-color:#ffffff;">]</span><span
style="color:#000000;background-color:#ffffff;">:# ping -c 3
bind9B.fantinibakery.com </span><br>
PING bind9B.fantinibakery.com (10.1.3.43) 56(84) bytes of data.
<br>
64 bytes from bind9b.fantinibakery.com (10.1.3.43): icmp_seq=1
ttl=64 time=0.203 ms
<br>
64 bytes from bind9b.fantinibakery.com (10.1.3.43): icmp_seq=2
ttl=64 time=0.332 ms
<br>
64 bytes from bind9b.fantinibakery.com (10.1.3.43): icmp_seq=3
ttl=64 time=0.216 ms
<br>
<br>
--- bind9B.fantinibakery.com ping statistics ---
<br>
3 packets transmitted, 3 received, 0% packet loss, time 2033ms
<br>
rtt min/avg/max/mdev = 0.203/0.250/0.332/0.057 ms<br>
<br>
</span></p>
<p><span style="font-family:monospace"><span
style="color:#54ff54;background-color:#ffffff;">root</span><span
style="color:#000000;background-color:#ffffff;">@</span><span
style="color:#b21818;background-color:#ffffff;">bind9B</span><span
style="color:#000000;background-color:#ffffff;">:</span><span
style="color:#18b218;background-color:#ffffff;">[</span><span
style="color:#ffff00;background-color:#ffffff;">~</span><span
style="color:#18b218;background-color:#ffffff;">]</span><span
style="color:#000000;background-color:#ffffff;">:# ip a
</span><br>
..<br>
2: eth0@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000
qdisc noqueue state UP group default qlen 1000
<br>
link/ether bc:24:11:f8:63:db brd ff:ff:ff:ff:ff:ff
link-netnsid 0
<br>
inet 10.1.3.43/24 brd 10.1.3.255 scope global dynamic eth0
<br>
,,<br>
<br>
<br>
</span></p>
<div class="moz-cite-prefix">On 12/9/24 05:25, Slawek Figiel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20241209102605.DF90B361CA@Mail.fantinibakery.com">Hello!
<br>
<br>
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.
<br>
The Stork agent hostname is "bind9B.fantinibakery.com," port 8080,
and the Stork server IP address is "10.1.3.3," port 8080.
<br>
<br>
You checked the connection from the Stork agent to the Stork
server, and it works using ping.
<br>
<br>
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".
<br>
<br>
I'm pretty sure this hostname is incorrect, and it cannot be
resolved in your internal network. Please verify if it is valid.
<br>
<br>
Regards
<br>
Slawek Figiel
<br>
<br>
On 07/12/2024 08:31, fbcadmin wrote:
<br>
<blockquote type="cite">for #2, I assume isc-kea-ctrl-agent will
need to be installed? I'll try now.............
<br>
<br>
After installing isc-kea-ctrl-agent and running stork-agent
register , i got the same ping error when trying to
<br>
<br>
<br>
*isc-kea-ctrl-agent.service - Kea Control Agent
<br>
Loaded: loaded
(/lib/systemd/system/isc-kea-ctrl-agent.service; enabled;
preset: enabled)
<br>
Active: active (running)since Fri 2024-12-06 17:58:56 EST;
8h ago
<br>
Docs: <a class="moz-txt-link-freetext" href="man:kea-ctrl-agent(8)">man:kea-ctrl-agent(8)</a>
<br>
Main PID: 40584 (kea-ctrl-agent)
<br>
Tasks: 5 (limit: 231595)
<br>
Memory: 1.5M
<br>
CPU: 9ms
<br>
CGroup: /system.slice/isc-kea-ctrl-agent.service
<br>
`-40584 /usr/sbin/kea-ctrl-agent -c
/etc/kea/kea-ctrl- agent.conf
<br>
<br>
Dec 06 17:58:56 bind9B systemd[1]: Started
isc-kea-ctrl-agent.service - Kea Control Agent.
<br>
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
<br>
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):
<br>
Dec 06 17:58:56 bind9B kea-ctrl-agent[40584]: INFO
CTRL_AGENT_STARTED Kea Control Agent version 2.6.1 started
<br>
<br>
# su stork-agent -s /bin/sh -c 'stork-agent register
--server-url <a class="moz-txt-link-freetext" href="http://10.1.3.3:8080">http://10.1.3.3:8080</a>'
<br>
>>> Enter the Stork server access token (optional):
<br>
>>> Enter IP address or FQDN of the host with Stork
agent (for the Stork server connection)
[bind9B.fantinibakery.com]:
<br>
>>> Enter port number that Stork Agent will listen on
[8080]:
<br>
INFO[2024-12-06 18:00:30] register.go:95 Forced agent
certificates regeneration.
<br>
INFO[2024-12-06 18:00:30] register.go:398
=============================================================================<br>
INFO[2024-12-06 18:00:30] register.go:399 AGENT TOKEN:
66B400430BCA152BFBEF023FAE9CB9DC0C5416FB600A3ABF74609CA1D3333471
<br>
INFO[2024-12-06 18:00:30] register.go:400
=============================================================================<br>
INFO[2024-12-06 18:00:30] register.go:405 Machine will
be automatically registered using the server token
<br>
INFO[2024-12-06 18:00:30] register.go:406 Agent token
is printed above for informational purposes only
<br>
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
<br>
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
<br>
INFO[2024-12-06 18:00:30] register.go:416 Try to
register agent in Stork Server
<br>
INFO[2024-12-06 18:00:30] register.go:273 Machine
registered
<br>
INFO[2024-12-06 18:00:30] register.go:294 Stored
agent-signed cert and CA cert
<br>
ERRO[2024-12-06 18:00:30] register.go:450 Retrying
ping 1/3 due to error error="problem pinging machine: Cannot
ping machine"
<br>
ERRO[2024-12-06 18:00:32] register.go:450 Retrying
ping 2/3 due to error error="problem pinging machine: Cannot
ping machine"
<br>
FATA[2024-12-06 18:00:36] main.go:320 Registration
failed error="cannot ping machine: problem pinging machine:
Cannot
<br>
ping machine"
<br>
<br>
<br>
On 12/6/24 04:29, Slawek Figiel wrote:
<br>
<blockquote type="cite">
<br>
Hello!
<br>
<br>
>> I get the following when trying to register a bind9
system to stork:
<br>
>> INFO[2024-12-04 12:34:54] register.go:273
Machine registered
<br>
>> FATA[2024-12-04 12:36:16] main.go:320
Registration
<br>
>> failed error="cannot ping
machine: problem
<br>
>> pinging machine: Cannot ping machine"
<br>
<br>
It may be a networking issue.
<br>
<br>
Your agent was able to establish a connection to the Stork
server, register itself, and send a request for ping.
<br>
But the Stork server couldn't connect to the Stork agent. The
firewall on the Stork server or agent machines may have caused
this.
<br>
<br>
Please check that:
<br>
<br>
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.
<br>
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).
<br>
<br>
I'll wait for your feedback.
<br>
<br>
> also isc-kea-ctrl-agent is not installed. Is that
needed?
<br>
<br>
The Kea Control Agent is mandatory only if you want to monitor
Kea daemons. It is not necessary to monitor BIND 9.
<br>
<br>
Regards,
<br>
Slawek Figiel
<br>
<br>
<br>
On 05/12/2024 23:40, fbcadmin wrote:
<br>
<blockquote type="cite">also isc-kea-ctrl-agent is not
installed. Is that needed?
<br>
<br>
On 12/5/24 16:53, fbcadmin wrote:
<br>
<blockquote type="cite">
<br>
Hello
<br>
<br>
I get the following when trying to register a bind9 system
to stork:
<br>
<br>
<br>
su stork-agent -s /bin/sh -c 'stork-agent register
--server-url <a class="moz-txt-link-freetext" href="http://10.1.3.3:8080">http://10.1.3.3:8080</a>'
<br>
>>> Enter the Stork server access token
(optional):
<br>
>>> Enter IP address or FQDN of the host with
Stork agent (for the Stork server connection)
[bind9B.test.com]:
<br>
>>> Enter port number that Stork Agent will
listen on [8080]:
<br>
INFO[2024-12-04 12:34:54] register.go:95 Forced
agent certificates regeneration.
<br>
INFO[2024-12-04 12:34:54] register.go:398
=============================================================================<br>
INFO[2024-12-04 12:34:54] register.go:399 AGENT
TOKEN:
D8E79ACBBC7620AE16E2C21EA002163D28974A0E0AF346B9D309F7355D4835C5
<br>
INFO[2024-12-04 12:34:54] register.go:400
=============================================================================<br>
INFO[2024-12-04 12:34:54] register.go:405
Machine will be automatically registered using the server
token
<br>
INFO[2024-12-04 12:34:54] register.go:406 Agent
token is printed above for informational purposes only
<br>
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
<br>
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
<br>
INFO[2024-12-04 12:34:54] register.go:416 Try to
register agent in Stork Server
<br>
INFO[2024-12-04 12:34:54] register.go:273
Machine registered
<br>
INFO[2024-12-04 12:34:54] register.go:294 Stored
agent- signed cert and CA cert
<br>
ERRO[2024-12-04 12:35:14] register.go:450
Retrying ping 1/3 due to error
error="problem pinging machine: Cannot ping machine"
<br>
ERRO[2024-12-04 12:35:36] register.go:450
Retrying ping 2/3 due to error
error="problem pinging machine: Cannot ping machine"
<br>
FATA[2024-12-04 12:36:16] main.go:320
Registration failed
error="cannot ping machine: problem pinging machine:
Cannot ping machine"
<br>
<br>
<br>
Package: isc-stork-agent Version: 2.0.0.241112163127 ,
Maintainer: Stork team <<a class="moz-txt-link-abbreviated" href="mailto:stork-users@lists.isc.org">stork-users@lists.isc.org</a> ,
APT-Sources: https://
dl.cloudsmith.io/public/isc/stork/deb/debian bookworm/main
amd64 Packages
<br>
<br>
# apt show bind9
<br>
Package: bind9
<br>
Version: 1:9.18.31-1+0~20241110.101+debian12~1.gbpbe8143
<br>
Priority: optional
<br>
Section: net
<br>
Maintainer: Debian DNS Team
<a class="moz-txt-link-rfc2396E" href="mailto:team+dns@tracker.debian.org"><team+dns@tracker.debian.org></a>
<br>
<br>
<br>
opsys = debian 12
<br>
<br>
<br>
Any suggestions on how to fix this? I am able to
register clients from kea dhcp systems .
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
</body>
</html>