No statistics available in GUI
name: Bug report
about: Create a report to help us improve
If you believe your bug report is a security issue (e.g. a packet that can kill the server), DO NOT REPORT IT HERE. Please use https://www.isc.org/community/report-bug/ instead or send mail to security-office(at)isc(dot)org.
Describe the bug
- I see no statistics for subnets in the Stork GUI.
- One subnet is giving errors trying to allocate IPs which is not full
To Reproduce Steps to reproduce the behavior:
- Installed KEA + Stork from recommended repos on Ubuntu 20.04
- Stats hooks are loaded in ctrl agent + dhcp4 server now, still no stats.
KEA Configs:
"Control-agent": {
"http-host": "127.0.0.1",
"http-port": 8000,
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/tmp/kea4-ctrl-socket"
},
"dhcp6": {
"socket-type": "unix",
"socket-name": "/tmp/kea6-ctrl-socket"
}
},
"hooks-libraries": [
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_stat_cmds.so",
"parameters": { }
},
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so",
"parameters": { }
}
],
"loggers": [
{
"name": "kea-ctrl-agent",
"output_options": [
{
"output": "/var/log/kea/kea-ctrl-agent.log"
}
],
"severity": "INFO",
"debuglevel": 0
}
]
}
}
Stork Configs
# address to bind ie. for listening
STORK_AGENT_ADDRESS=192.168.0.7
STORK_AGENT_PORT=8079
# enable Stork functionality only, i.e. disable Prometheus exporters
STORK_AGENT_LISTEN_STORK_ONLY=true
# enable Prometheus exporters only, i.e. disable Stork functionality
# STORK_AGENT_LISTEN_PROMETHEUS_ONLY=true
# settings for exporting stats to Prometheus
# STORK_AGENT_PROMETHEUS_KEA_EXPORTER_ADDRESS=
# STORK_AGENT_PROMETHEUS_KEA_EXPORTER_PORT=
# STORK_AGENT_PROMETHEUS_KEA_EXPORTER_INTERVAL=
# STORK_AGENT_PROMETHEUS_BIND9_EXPORTER_ADDRESS=
# STORK_AGENT_PROMETHEUS_BIND9_EXPORTER_PORT=
# STORK_AGENT_PROMETHEUS_BIND9_EXPORTER_INTERVAL=
# this is used when agent is automatically registered in Stork server
STORK_AGENT_SERVER_URL=http://192.168.0.7:8080
# STORK_AGENT_ADDRESS=
# skip TLS certificate verification when the Stork Agent connects
# to Kea over TLS and Kea uses self-signed certificates
STORK_AGENT_SKIP_TLS_CERT_VERIFICATION=true
# database settings
STORK_DATABASE_HOST=192.168.0.5
STORK_DATABASE_PORT=5432
STORK_DATABASE_NAME=stork
STORK_DATABASE_USER_NAME=stork
# empty password is set to avoid prompting user for password to database
STORK_DATABASE_PASSWORD=pw
# ReST API settings
# STORK_REST_HOST=
# STORK_REST_PORT=
# STORK_REST_TLS_CERTIFICATE=
# STORK_REST_TLS_PRIVATE_KEY=
# STORK_REST_TLS_CA_CERTIFICATE=
STORK_REST_STATIC_FILES_DIR=/usr/share/stork/www
Dashboard Screenshots:
- https://salty.link/screenshots/user1/0802iv00f.png
- https://salty.link/screenshots/user1/314boia99.png
- https://salty.link/screenshots/user1/9509P7234.png
Expected behavior I expect the leases and the subnet utilization to show up in the Stork dashboard.
Environment:
2.0.0
tarball
linked with:
log4cplus 2.0.5
OpenSSL 1.1.1l 24 Aug 2021
database:
MySQL backend 12.0, library 8.0.27
PostgreSQL backend 6.2, library 130004
Memfile backend 2.1
0.22.0
root@dhcp1:/etc/stork# stork-agent -v
0.22.0
- OS: Ubuntu 20.04 x64
ii isc-stork-agent 0.22.0.211105072749 amd64 ISC Stork Agent
ii isc-stork-server 0.22.0.211105072749 amd64 ISC Stork Server
root@dhcp1:/etc/stork# dpkg --list |grep kea
ii isc-kea-admin 2.0.0-isc20210927143053 amd64 Administration utilities for ISC Kea DHCP server
ii isc-kea-common 2.0.0-isc20210927143053 amd64 Common libraries for the ISC Kea DHCP server
ii isc-kea-ctrl-agent 2.0.0-isc20210927143053 amd64 ISC Kea DHCP server REST API service
ii isc-kea-dev 2.0.0-isc20210927143053 amd64 Development headers for ISC Kea DHCP server
ii isc-kea-dhcp4-server 2.0.0-isc20210927143053 amd64 ISC Kea IPv4 DHCP server
ii isc-kea-dhcp6-server 2.0.0-isc20210927143053 amd64 ISC Kea IPv6 DHCP server
ii isc-kea-doc 2.0.0-isc20210927143053 all Documentation for ISC Kea DHCP server
ii python3-isc-kea-connector 2.0.0-isc20210927143053 all Python3 management connector for ISC Kea DHCP server
Logs:
o allocate an IPv4 address in the subnet 10.43.60.0/26, subnet-id 4, shared network
2021-11-05 20:35:31.215 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 94:57:a5:50:0e:56], cid=[01:94:57:a5:50:0e:56], tid=0x8: failed to alloc
ate an IPv4 address after 61 attempt(s)
2021-11-05 20:35:31.215 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 94:57:a5:50:0e:56], cid=[01:94:57:a5:50:0e:56], tid=0x8: Failed
to allocate an IPv4 address for client with classes: ALL, VENDOR_CLASS_CPQRIB3, UNKNOWN
2021-11-05 20:35:32.081 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_SUBNET [hwtype=1 94:57:a5:50:0e:64], cid=[01:94:57:a5:50:0e:64], tid=0x8: failed t
o allocate an IPv4 address in the subnet 10.43.60.0/26, subnet-id 4, shared network
2021-11-05 20:35:32.081 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 94:57:a5:50:0e:64], cid=[01:94:57:a5:50:0e:64], tid=0x8: failed to alloc
ate an IPv4 address after 61 attempt(s)
2021-11-05 20:35:32.081 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 94:57:a5:50:0e:64], cid=[01:94:57:a5:50:0e:64], tid=0x8: Failed
to allocate an IPv4 address for client with classes: ALL, VENDOR_CLASS_CPQRIB3, UNKNOWN
2021-11-05 20:35:32.817 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_SUBNET [hwtype=1 94:57:a5:50:1e:3c], cid=[01:94:57:a5:50:1e:3c], tid=0x8: failed t
o allocate an IPv4 address in the subnet 10.43.60.0/26, subnet-id 4, shared network
2021-11-05 20:35:32.817 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 94:57:a5:50:1e:3c], cid=[01:94:57:a5:50:1e:3c], tid=0x8: failed to alloc
ate an IPv4 address after 61 attempt(s)
2021-11-05 20:35:32.817 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 94:57:a5:50:1e:3c], cid=[01:94:57:a5:50:1e:3c], tid=0x8: Failed
to allocate an IPv4 address for client with classes: ALL, VENDOR_CLASS_CPQRIB3, UNKNOWN
2021-11-05 20:35:33.259 INFO [kea-dhcp4.leases/5416.140484751342016] DHCP4_LEASE_ALLOC [hwtype=1 2c:60:0c:d7:fc:dc], cid=[01:2c:60:0c:d7:fc:dc], tid=0x87e34c3e: lease 10.43.25.9 has be
en allocated for 3600 seconds
2021-11-05 20:35:33.696 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_SUBNET [hwtype=1 14:02:ec:38:0a:a2], cid=[01:14:02:ec:38:0a:a2], tid=0x8: failed t
o allocate an IPv4 address in the subnet 10.43.60.0/26, subnet-id 4, shared network
2021-11-05 20:35:33.696 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 14:02:ec:38:0a:a2], cid=[01:14:02:ec:38:0a:a2], tid=0x8: failed to alloc
ate an IPv4 address after 61 attempt(s)
2021-11-05 20:35:33.696 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 14:02:ec:38:0a:a2], cid=[01:14:02:ec:38:0a:a2], tid=0x8: Failed
to allocate an IPv4 address for client with classes: ALL, VENDOR_CLASS_CPQRIB3, UNKNOWN
2021-11-05 20:35:33.925 INFO [kea-dhcp4.leases/5416.140484751342016] DHCP4_LEASE_ALLOC [hwtype=1 2c:60:0c:d7:fd:18], cid=[01:2c:60:0c:d7:fd:18], tid=0xdff67c12: lease 10.43.25.8 has be
en allocated for 3600 seconds
2021-11-05 20:35:35.304 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_SUBNET [hwtype=1 94:57:a5:50:0e:56], cid=[01:94:57:a5:50:0e:56], tid=0x8: failed t
o allocate an IPv4 address in the subnet 10.43.60.0/26, subnet-id 4, shared network
2021-11-05 20:35:35.304 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 94:57:a5:50:0e:56], cid=[01:94:57:a5:50:0e:56], tid=0x8: failed to alloc
ate an IPv4 address after 61 attempt(s)
2021-11-05 20:35:35.304 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 94:57:a5:50:0e:56], cid=[01:94:57:a5:50:0e:56], tid=0x8: Failed
to allocate an IPv4 address for client with classes: ALL, VENDOR_CLASS_CPQRIB3, UNKNOWN
2021-11-05 20:35:36.171 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_SUBNET [hwtype=1 94:57:a5:50:0e:64], cid=[01:94:57:a5:50:0e:64], tid=0x8: failed t
o allocate an IPv4 address in the subnet 10.43.60.0/26, subnet-id 4, shared network
2021-11-05 20:35:36.171 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 94:57:a5:50:0e:64], cid=[01:94:57:a5:50:0e:64], tid=0x8: failed to alloc
ate an IPv4 address after 61 attempt(s)
2021-11-05 20:35:36.171 WARN [kea-dhcp4.alloc-engine/5416.140484751342016] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 94:57:a5:50:0e:64], cid=[01:94:57:a5:50:0e:64], tid=0x8: Failed
to allocate an IPv4 address for client with classes: ALL, VENDOR_CLASS_CPQRIB3, UNKNOWN
Contacting you How can ISC reach you to discuss this matter further? If you do not specify any means such as e-mail, jabber id or a telephone, we may send you a message on github with questions when we have them.
Email / Gitlab / Github are fine.