stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2023-12-12T14:31:05Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/1262stork-tool can't connect to Postgres with unix socket2023-12-12T14:31:05Zmikygeestork-tool can't connect to Postgres with unix socketHello,
I execute this command line but I get this error.
```
# ./backend/cmd/stork-tool/stork-tool db-init --db-host=/tmp/.s.PGSQL.5432 --db-name storkdatabase --db-user storkuser --db-password storkpassword
INFO[2023-12-12 03:09:44] ...Hello,
I execute this command line but I get this error.
```
# ./backend/cmd/stork-tool/stork-tool db-init --db-host=/tmp/.s.PGSQL.5432 --db-name storkdatabase --db-user storkuser --db-password storkpassword
INFO[2023-12-12 03:09:44] main.go:134 SQL queries tracing set to none
INFO[2023-12-12 03:09:44] connection.go:90 Checking connection to database
WARN[2023-12-12 03:09:44] connection.go:122 Problem connecting to db, trying again in 2 seconds, 1/10 error="unable to connect to the database using provided settings: dial tcp: lookup /tmp/.s.PGSQL.5432: no such host"
```
So I try to use a unix socket but stork says "dial tcp"
On this page
https://stork.readthedocs.io/en/latest/man/stork-tool.8.html
I see
```
--db-host=
Specifies the name of the host, IP address **or a socket path for the database connection**. The default value depends on the system.
```https://gitlab.isc.org/isc-projects/stork/-/issues/1236stork-demo.sh is failing to build the web ui for stork2023-12-07T16:49:30Zvarsrajastork-demo.sh is failing to build the web ui for stork---
name: Bug report
about: store-demo.sh fails to build the web ui for stork
---
**Describe the bug**
Trying to build the stork server, web-ui web-apache docker containers . Checked out the latest code and tried to run the stork-dem...---
name: Bug report
about: store-demo.sh fails to build the web ui for stork
---
**Describe the bug**
Trying to build the stork server, web-ui web-apache docker containers . Checked out the latest code and tried to run the stork-demo.sh script that builds these images. it is exiting with error to build the web-ui image.
**Expected behavior**
Able to see the stork demo to start running.
[stork-demo-error.txt](/uploads/d0b03d0046b4202bd0a5c440896b549a/stork-demo-error.txt)
**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.https://gitlab.isc.org/isc-projects/stork/-/issues/1112(60) SSL certificate problem: unable to get local issuer certificate (ERR_BAD...2023-06-28T15:33:32ZFrancisco Ordoñez(60) SSL certificate problem: unable to get local issuer certificate (ERR_BAD_SSL_CLIENT_AUTH_CERT)HI,
I am using KEA as DHCP server and Stork as Dasboard, when I try to use RESTAPI in STORK it shows me the following error when accessing:
https://localhost:8080
ERR_BAD_SSL_CLIENT_AUTH_CERT
The configuration I have in /etc/stork/ser...HI,
I am using KEA as DHCP server and Stork as Dasboard, when I try to use RESTAPI in STORK it shows me the following error when accessing:
https://localhost:8080
ERR_BAD_SSL_CLIENT_AUTH_CERT
The configuration I have in /etc/stork/server.env for restapi is the following:
### REST API settings
STORK_REST_HOST=192.168.179.146
STORK_REST_PORT=8080
STORK_REST_TLS_CERTIFICATE=/etc/stork/srvcert.pem
STORK_REST_TLS_PRIVATE_KEY=/etc/stork/srvkey.pem
STORK_REST_TLS_CA_CERTIFICATE=/etc/stork/cacert.pem
STORK_REST_STATIC_FILES_DIR=/usr/share/stork/www
I have created the certificates as follows:
stork-tool cert-export --db-user stork --db-password "passw" --db-host localhost --db-name stork -f srvcert -o srvcert.pem
stork-tool cert-export --db-user stork --db-password "passw" --db-host localhost --db-name stork -f srvkey -o srvkey.pem
stork-tool cert-export --db-user stork --db-password "passw" --db-host localhost --db-name stork -f cacert -o cacert.pem
It is the first time that I try to use restapi on stork, does anyone have any idea what I could be doing wrong, I use debian 11https://gitlab.isc.org/isc-projects/stork/-/issues/1040Kea DHCP with Stork IP reservations in database2023-05-30T13:36:01ZGabriel GILKea DHCP with Stork IP reservations in databaseHi, I'm having an issue with my Kea configuration when I start my services my server distributes IP addresses but when I log into my Stork server I can't see them.
Any ideas?
Thanks,Hi, I'm having an issue with my Kea configuration when I start my services my server distributes IP addresses but when I log into my Stork server I can't see them.
Any ideas?
Thanks,https://gitlab.isc.org/isc-projects/stork/-/issues/1026Refresh: failure trying primary2023-04-25T11:48:54ZDaniel A. RodriguezRefresh: failure trying primarySecondary getting error ("connection refused") when trying to refresh a zone
- BIND9 version: BIND 9.18.12-1~bpo11+1-Debian
- Kernel version: 6.1.0-0.deb11.5-amd64
- OS: Debian 11 x64
Several kernels were tested with the same result...Secondary getting error ("connection refused") when trying to refresh a zone
- BIND9 version: BIND 9.18.12-1~bpo11+1-Debian
- Kernel version: 6.1.0-0.deb11.5-amd64
- OS: Debian 11 x64
Several kernels were tested with the same result
linux-image-5.10.0-20-amd64
linux-image-5.10.0-21-amd64
linux-image-6.1.0-0.deb11.5-amd64https://gitlab.isc.org/isc-projects/stork/-/issues/936connection refused: stork machine registration2023-02-14T16:42:50ZAdam Chaitconnection refused: stork machine registrationWhen I run stork-agent register --server-url http://127.0.0.1 i get the following returned and I can't figure out how to resolve the "connection refused":
>>>> Server access token (optional):
>>>> IP address or FQDN of the host with Sto...When I run stork-agent register --server-url http://127.0.0.1 i get the following returned and I can't figure out how to resolve the "connection refused":
>>>> Server access token (optional):
>>>> IP address or FQDN of the host with Stork Agent (for the Stork Server connection) [kea]:
>>>> Port number that Stork Agent will listen on [8080]:
INFO[2023-01-12 16:58:44] register.go:160 Agent token stored in /var/lib/stork-agent/tokens/agent-token.txt
INFO[2023-01-12 16:58:44] register.go:161 Agent key, agent token, and CSR (re)generated
INFO[2023-01-12 16:58:44] register.go:449 =============================================================================
INFO[2023-01-12 16:58:44] register.go:450 AGENT TOKEN: 71DACCA3209973F663246FE581CBFCE9FC9F000B0EF19A6B50030CCE35B35F61
INFO[2023-01-12 16:58:44] register.go:451 =============================================================================
INFO[2023-01-12 16:58:44] register.go:454 Authorize the machine in the Stork web UI
INFO[2023-01-12 16:58:44] register.go:471 Try to register agent in Stork Server
ERRO[2023-01-12 16:58:44] register.go:474 problem registering machine: Post "http://127.0.0.1/api/machines": dial tcp 127.0.0.1:80: connect: connection refused
FATA[2023-01-12 16:58:44] main.go:134 Registration failed1.10Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/799stork-agent bind exporter frequently errors on named cwd detection2022-07-26T08:15:07ZJens Krabbenhoeftstork-agent bind exporter frequently errors on named cwd detection**Describe the bug**
We have added the stork-agent to standard ISC bind containers (`internetsystemsconsortium/bind9:9.18`) and run them side by side with the named process. While testing we found that every 10 seconds following error m...**Describe the bug**
We have added the stork-agent to standard ISC bind containers (`internetsystemsconsortium/bind9:9.18`) and run them side by side with the named process. While testing we found that every 10 seconds following error messages get created (where 8 is the named pid):
```
time="2022-07-04 06:56:31" level="warning" msg="Cannot get process current working directory: readlink /proc/8/cwd: permission denied" file=" monitor.go:213 "
time="2022-07-04 06:56:41" level="warning" msg="Cannot get process current working directory: readlink /proc/8/cwd: permission denied" file=" monitor.go:213 "
time="2022-07-04 06:56:51" level="warning" msg="Cannot get process current working directory: readlink /proc/8/cwd: permission denied" file=" monitor.go:213 "
time="2022-07-04 06:57:01" level="warning" msg="Cannot get process current working directory: readlink /proc/8/cwd: permission denied" file=" monitor.go:213 "
time="2022-07-04 06:57:11" level="warning" msg="Cannot get process current working directory: readlink /proc/8/cwd: permission denied" file=" monitor.go:213 "
time="2022-07-04 06:57:21" level="warning" msg="Cannot get process current working directory: readlink /proc/8/cwd: permission denied" file=" monitor.go:213 "
```
**Expected behavior**
No error message gets logged.
**Additional Information**
There is a bug for the same error message in issue #274 - unfortunately the solution setting CAP_SYS_PTRACE does not work on unprivileged docker containers. cwd is not readable unless starting the container privileged (and cap_sys_ptrace is not working on unprivileged containers either).
**Environment:**
- BIND9 version: 9.18.4-1+ubuntu22.04.1+isc+1
- Stork: 1.4.0
- OS: Ubuntu 22.04 LTS (docker container `internetsystemsconsortium/bind9:9.18`)1.6https://gitlab.isc.org/isc-projects/stork/-/issues/706Download troubleshooting info doesn't work2022-07-12T08:31:04ZTomek MrugalskiDownload troubleshooting info doesn't workI've been playing with the Stork demo on master (ea964f549acca39037363fcd7dbf67ff24d0e024). The demo was running on for a while and then I've tried to download the troubleshooting info and it didn't work. Here's what I saw:
![stork-down...I've been playing with the Stork demo on master (ea964f549acca39037363fcd7dbf67ff24d0e024). The demo was running on for a while and then I've tried to download the troubleshooting info and it didn't work. Here's what I saw:
![stork-download-troubleshooting-info](/uploads/b2a07ebd65c22a6b10ae7aad28824fbb/stork-download-troubleshooting-info.png).
My setup was:
- 192.168.1.99 - ubuntu 21.04, running the demo.
- 192.168.1.101 - ubuntu 21.10, the laptop running the firefox that was showing the demo.1.5Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/524Agent registration over HTTPS2021-12-15T13:27:00ZMaria HrabosovaAgent registration over HTTPSI'm using Stork 0.15.0. I installed both server and agent but I failed to register the agent in the server. I'm using HTTPS and the server complains that the agent didn't provide a client certificate. As far as I understand from the sour...I'm using Stork 0.15.0. I installed both server and agent but I failed to register the agent in the server. I'm using HTTPS and the server complains that the agent didn't provide a client certificate. As far as I understand from the source code, the client certificate is only generated during the registration process, so it's not there yet during the client-authenticated TLS handshake in the beginning of the registration. If my understanding of the process is correct, I think it should be changed somehow so that it is possible to register over HTTPS.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/585Stork not pulling correct HA status2021-12-06T14:10:38ZGreg WintonStork not pulling correct HA statusI am running KEA 1.8.3 and stork 0.20.0.
Stork server is running on "eventsdhcp2" with an agent installed on "eventsdhcp1" and "eventsdhcp2" (port 8090 on Server 2) for monitoring.
When I kill the network port to "eventsdhcp1" I can se...I am running KEA 1.8.3 and stork 0.20.0.
Stork server is running on "eventsdhcp2" with an agent installed on "eventsdhcp1" and "eventsdhcp2" (port 8090 on Server 2) for monitoring.
When I kill the network port to "eventsdhcp1" I can see that "eventsdhcp2" takes over successfully and starts dishing out DHCP as expected. But Stork stops refreshing for a long time and when it eventually does refresh it shows the wrong information about HA status. Sometimes it will show "eventsdhcp1" as still online and "eventsdhcp2" as being unavailable. Sometimes it shows that both are still online BUT both are responding to DHCP traffic, but in reality "eventsdhcp1" is actually offline and "eventsdhcp2" has taken over as expected.
The only thing that seems to sort it out is restarting the stork server on "eventsdhcp2".
Anyone come across this before and know where I could be going wrong?
In the pictures below, both servers are actually back online and functioning as expected, with "eventsdhcp1" as the primary and "eventsdhcp2" sitting as the backup.
![1](/uploads/39e8e2a271a8100ea5fce1ee3eee2cba/1.JPG)
![2](/uploads/2c6f2dcb59c81313f9171e7affa42983/2.JPG)analysis-in-progressMarcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/580Error while reading host reservations2021-11-03T10:14:38ZFabian KretschmerError while reading host reservationsHi,
we are facing a problem reading the host reservations in Stork 0.19.0 with the kea premium hook host_cmds library (tested with compiled kea 1.8.2 and 1.9.11).
Using the API, multiple hosts reservations were successfully added to a M...Hi,
we are facing a problem reading the host reservations in Stork 0.19.0 with the kea premium hook host_cmds library (tested with compiled kea 1.8.2 and 1.9.11).
Using the API, multiple hosts reservations were successfully added to a MySQL database backend. The Library is successfully loaded, the kea server is registered in stork and the agent is running, so everything looks fine until here.
At the DHCP host reservation page in stork no reservations are displayed. At this time, an Error is logged in stork and kea, please have a look at the logs below. In both Kea versions they are looking the same and the error is reproducible.
Please let me know, if you need any additional informations, any help would be appreciated.
Kind regards,
Fabian
**Environment:**
- Kea version: 1.8.2 / 1.9.11 with Stork 0.19.0
- OS: Ubuntu 18.04 Docker Container
- Which hooks where loaded in: libdhcp_host_cmds.so, libdhcp_stat_cmds.so, libdhcp_lease_cmds.so
**Logs:**
The reservation-add command logs looks like:
```
INFO COMMAND_RECEIVED Received command 'reservation-add'
INFO HOST_CMDS_RESERV_ADD reservation-add command successful (parameters: { "reservation": { "boot-file-name": "bootfile.efi", "hostname": "HOST1", "hw-address": "00:11:22:33:44:55", "ip-address": "192.168.10.100", "subnet-id": 10, "user-context": "{key': 'value'}" } })
INFO CTRL_AGENT_COMMAND_FORWARDED command reservation-add successfully forwarded to the service dhcp4
```
Kea Server:
`ERROR HOOKS_CALLOUT_ERROR error returned by callout on hook $reservation_get_page registered by library with index 3 (callout address 0x7ff88302e410) (callout duration 18.124 ms)`
Stork Server:
```
INFO[2021-09-03 07:38:44] eventcenter.go:117 event 'communication with <daemon id="12" name="dhcp4" appId="3" appType="kea"> of <app id="3" name="kea@172.17.0.3" type="kea" version="1.9.11"> failed'
ERRO[2021-09-03 07:38:44] host.go:87 error occurred while fetching hosts from app 3: error returned by Kea in response to reservation-get-page command
isc.org/stork/server/apps/kea.(*HostDetectionIterator).sendReservationGetPage
/tmp/build/backend/server/apps/kea/host.go:254
isc.org/stork/server/apps/kea.(*HostDetectionIterator).DetectHostsPageFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:356
isc.org/stork/server/apps/kea.updateHostsFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:536
isc.org/stork/server/apps/kea.(*HostsPuller).pullData
/tmp/build/backend/server/apps/kea/host.go:84
isc.org/stork/server/agentcomm.(*PeriodicPuller).pullerLoop
/tmp/build/backend/server/agentcomm/puller.go:169
runtime.goexit
/tmp/build/tools/1.15.5/go/src/runtime/asm_amd64.s:1374
problem with sending reservation-get-page command upon attempt to detect host reservations over the host_cmds hooks library
INFO[2021-09-03 07:38:44] host.go:100 completed pulling hosts from Kea apps: 0/1 succeeded
ERRO[2021-09-03 07:38:44] puller.go:172 errors were encountered while pulling data from apps: error returned by Kea in response to reservation-get-page command
isc.org/stork/server/apps/kea.(*HostDetectionIterator).sendReservationGetPage
/tmp/build/backend/server/apps/kea/host.go:254
isc.org/stork/server/apps/kea.(*HostDetectionIterator).DetectHostsPageFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:356
isc.org/stork/server/apps/kea.updateHostsFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:536
isc.org/stork/server/apps/kea.(*HostsPuller).pullData
/tmp/build/backend/server/apps/kea/host.go:84
isc.org/stork/server/agentcomm.(*PeriodicPuller).pullerLoop
/tmp/build/backend/server/agentcomm/puller.go:169
runtime.goexit
/tmp/build/tools/1.15.5/go/src/runtime/asm_amd64.s:1374
problem with sending reservation-get-page command upon attempt to detect host reservations over the host_cmds hooks library
INFO[2021-09-03 06:37:47] eventcenter.go:117 event 'communication with <daemon id="3" name="dhcp4" appId="1" appType="kea"> of <app id="1" name="kea@172.17.0.3" type="kea" version="1.8.2"> failed'
ERRO[2021-09-03 06:37:47] host.go:87 error occurred while fetching hosts from app 1: error returned by Kea in response to reservation-get-page command
isc.org/stork/server/apps/kea.(*HostDetectionIterator).sendReservationGetPage
/tmp/build/backend/server/apps/kea/host.go:254
isc.org/stork/server/apps/kea.(*HostDetectionIterator).DetectHostsPageFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:356
isc.org/stork/server/apps/kea.updateHostsFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:536
isc.org/stork/server/apps/kea.(*HostsPuller).pullData
/tmp/build/backend/server/apps/kea/host.go:84
isc.org/stork/server/agentcomm.(*PeriodicPuller).pullerLoop
/tmp/build/backend/server/agentcomm/puller.go:169
runtime.goexit
/tmp/build/tools/1.15.5/go/src/runtime/asm_amd64.s:1374
problem with sending reservation-get-page command upon attempt to detect host reservations over the host_cmds hooks library
INFO[2021-09-03 06:37:47] host.go:100 completed pulling hosts from Kea apps: 0/1 succeeded
ERRO[2021-09-03 06:37:47] puller.go:172 errors were encountered while pulling data from apps: error returned by Kea in response to reservation-get-page command
isc.org/stork/server/apps/kea.(*HostDetectionIterator).sendReservationGetPage
/tmp/build/backend/server/apps/kea/host.go:254
isc.org/stork/server/apps/kea.(*HostDetectionIterator).DetectHostsPageFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:356
isc.org/stork/server/apps/kea.updateHostsFromHostCmds
/tmp/build/backend/server/apps/kea/host.go:536
isc.org/stork/server/apps/kea.(*HostsPuller).pullData
/tmp/build/backend/server/apps/kea/host.go:84
isc.org/stork/server/agentcomm.(*PeriodicPuller).pullerLoop
/tmp/build/backend/server/agentcomm/puller.go:169
runtime.goexit
/tmp/build/tools/1.15.5/go/src/runtime/asm_amd64.s:1374
problem with sending reservation-get-page command upon attempt to detect host reservations over the host_cmds hooks library
```
Edit: Here's a more verbose (debuglevel 99) output from the kea server:
```
WARN[2021-09-07 13:32:42] promkeaexporter.go:368 problem with connecting to dhcp daemon: unable to forward command to the dhcp6 service: No such file or directory. The server is likely to be offline
DEBUG DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: reclaim-expired-leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = 100 leases or 250 milliseconds)
DEBUG DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.581 ms
DEBUG ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
DEBUG DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
DEBUG DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: flush-reclaimed-leases
DEBUG ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE begin deletion of reclaimed leases expired more than 3600 seconds ago
DEBUG DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than 3600 seconds ago
DEBUG DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted 0 reclaimed leases from the database
DEBUG ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0 expired-reclaimed leases
DEBUG DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
INFO COMMAND_RECEIVED Received command 'reservation-get-page'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 128 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'reservation-get-page'
DEBUG HOOKS_CALLOUTS_BEGIN begin all callouts for hook $reservation_get_page
DEBUG HOOKS_CALLOUT_CALLED hooks library with index 3 has called a callout on hook $reservation_get_page that has address 0x7f176473c4a0 (callout duration: 4.296 ms)
DEBUG HOOKS_CALLOUTS_COMPLETE completed callouts for hook $reservation_get_page (total callouts duration: 4.296 ms)
DEBUG COMMAND_SOCKET_WRITE Sent response of 92 bytes (0 bytes left to send) over command socket 23
INFO CTRL_AGENT_COMMAND_FORWARDED command reservation-get-page successfully forwarded to the service dhcp4
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO[2021-09-07 13:32:50] agent.go:375 Compressing response from 96 B to 108 B, ratio 112%
INFO COMMAND_RECEIVED Received command 'stat-lease4-get'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 56 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'stat-lease4-get'
DEBUG HOOKS_CALLOUTS_BEGIN begin all callouts for hook $stat_lease4_get
INFO STAT_CMDS_LEASE4_GET stat-lease4-get command successful, parameters: [all subnets] rows found: 1
DEBUG HOOKS_CALLOUT_CALLED hooks library with index 2 has called a callout on hook $stat_lease4_get that has address 0x7f17649600c0 (callout duration: 0.431 ms)
DEBUG HOOKS_CALLOUTS_COMPLETE completed callouts for hook $stat_lease4_get (total callouts duration: 0.431 ms)
INFO CTRL_AGENT_COMMAND_FORWARDED command stat-lease4-get successfully forwarded to the service dhcp4
DEBUG COMMAND_SOCKET_WRITE Sent response of 303 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO[2021-09-07 13:32:50] agent.go:375 Compressing response from 307 B to 212 B, ratio 69%
INFO COMMAND_RECEIVED Received command 'statistic-get'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 96 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'statistic-get'
DEBUG COMMAND_SOCKET_WRITE Sent response of 90 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command statistic-get successfully forwarded to the service dhcp4
INFO[2021-09-07 13:32:50] agent.go:375 Compressing response from 94 B to 110 B, ratio 117%
INFO COMMAND_RECEIVED Received command 'reservation-get-page'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 129 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'reservation-get-page'
DEBUG HOOKS_CALLOUTS_BEGIN begin all callouts for hook $reservation_get_page
ERROR HOOKS_CALLOUT_ERROR error returned by callout on hook 3 registered by library with index $reservation_get_page (callout address 0x7f176473c4a0) (callout duration 15.274 ms)
DEBUG HOOKS_CALLOUTS_COMPLETE completed callouts for hook $reservation_get_page (total callouts duration: 15.274 ms)
INFO CTRL_AGENT_COMMAND_FORWARDED command reservation-get-page successfully forwarded to the service dhcp4
DEBUG COMMAND_SOCKET_WRITE Sent response of 657 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO[2021-09-07 13:32:50] agent.go:375 Compressing response from 661 B to 365 B, ratio 55%
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 86 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_WRITE Sent response of 1759 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command statistic-get-all successfully forwarded to the service dhcp4
WARN[2021-09-07 13:32:52] promkeaexporter.go:368 problem with connecting to dhcp daemon: unable to forward command to the dhcp6 service: No such file or directory. The server is likely to be offline
DEBUG DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: reclaim-expired-leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = 100 leases or 250 milliseconds)
DEBUG DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 1.478 ms
DEBUG ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
DEBUG DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
INFO COMMAND_RECEIVED Received command 'version-get'
INFO[2021-09-07 13:32:59] agent.go:375 Compressing response from 116 B to 125 B, ratio 107%
INFO COMMAND_RECEIVED Received command 'config-get'
INFO[2021-09-07 13:32:59] agent.go:375 Compressing response from 683 B to 314 B, ratio 45%
INFO COMMAND_RECEIVED Received command 'version-get'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 67 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'version-get'
DEBUG COMMAND_SOCKET_WRITE Sent response of 205 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command version-get successfully forwarded to the service dhcp4
INFO[2021-09-07 13:32:59] agent.go:375 Compressing response from 482 B to 273 B, ratio 56%
INFO COMMAND_RECEIVED Received command 'status-get'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 60 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'status-get'
DEBUG COMMAND_SOCKET_WRITE Sent response of 107 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command status-get successfully forwarded to the service dhcp4
INFO[2021-09-07 13:32:59] agent.go:375 Compressing response from 249 B to 196 B, ratio 78%
INFO COMMAND_RECEIVED Received command 'config-get'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 66 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'config-get'
DEBUG COMMAND_SOCKET_WRITE Sent response of 3167 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command config-get successfully forwarded to the service dhcp4
WARN[2021-09-07 13:32:59] kea.go:69 skipped refreshing viewable log files because config-get returned non success result
WARN[2021-09-07 13:32:59] kea.go:69 skipped refreshing viewable log files because config-get returned non success result
INFO[2021-09-07 13:32:59] agent.go:375 Compressing response from 3444 B to 1296 B, ratio 37%
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 86 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_WRITE Sent response of 1759 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command statistic-get-all successfully forwarded to the service dhcp4
WARN[2021-09-07 13:33:02] promkeaexporter.go:368 problem with connecting to dhcp daemon: unable to forward command to the dhcp6 service: No such file or directory. The server is likely to be offline
DEBUG DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: reclaim-expired-leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = 100 leases or 250 milliseconds)
DEBUG DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.633 ms
DEBUG ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
DEBUG DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 86 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_WRITE Sent response of 1759 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command statistic-get-all successfully forwarded to the service dhcp4
WARN[2021-09-07 13:33:12] promkeaexporter.go:368 problem with connecting to dhcp daemon: unable to forward command to the dhcp6 service: No such file or directory. The server is likely to be offline
DEBUG DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: flush-reclaimed-leases
DEBUG ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE begin deletion of reclaimed leases expired more than 3600 seconds ago
DEBUG DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than 3600 seconds ago
DEBUG DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted 0 reclaimed leases from the database
DEBUG ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0 expired-reclaimed leases
DEBUG DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
DEBUG DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: reclaim-expired-leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = 100 leases or 250 milliseconds)
DEBUG DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
DEBUG ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.626 ms
DEBUG ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
DEBUG DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_CONNECTION_OPENED Opened socket 23 for incoming command connection
DEBUG COMMAND_SOCKET_READ Received 86 bytes over command socket 23
INFO COMMAND_RECEIVED Received command 'statistic-get-all'
DEBUG COMMAND_SOCKET_WRITE Sent response of 1759 bytes (0 bytes left to send) over command socket 23
DEBUG COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 23 for existing command connection
INFO CTRL_AGENT_COMMAND_FORWARDED command statistic-get-all successfully forwarded to the service dhcp4
WARN[2021-09-07 13:33:22] promkeaexporter.go:368 problem with connecting to dhcp daemon: unable to forward command to the dhcp6 service: No such file or directory. The server is likely to be offline
```0.22https://gitlab.isc.org/isc-projects/stork/-/issues/532Stork web gui failing on port 80, but working when specify 8080.2021-09-07T13:56:36ZNicolas EStork web gui failing on port 80, but working when specify 8080.Hello, and thank you for all this work and doc.
I'm using Kea+Stork since 1.9.2 and it's working fine.
Recently, I upgraded to 1.9.6 and though I went through the Stork agent registering quite seemlessly, I'm noticing that the Stork web...Hello, and thank you for all this work and doc.
I'm using Kea+Stork since 1.9.2 and it's working fine.
Recently, I upgraded to 1.9.6 and though I went through the Stork agent registering quite seemlessly, I'm noticing that the Stork web gui, served by nginx, is now only operational through http://mycompany-kea-nginx-server.com:8080 when it was previously OK through http://mycompany-kea-nginx-server.com
This is not a big deal, but I didn't change the nginx setup when upgrading.
When using the (ommitted by default) port 80 URL, I'm reaching the login page, but I'm seeing lots of errors in the browser console, and the kea version cannot be displayed ("unknown"). Though, I can enter in the web gui, I see the usual menus, but every local data is missing.
I see no error in the logs files of nginx neither stork server or agent.
The only errors I see are from the browser dev console : [1].
For a nginx config file, I'm using the file provided in the stork example directory, coming with the Debian 10 package.
I wanted to know what has changed around this subject and if there is a way to recover the simplest previous URL?
Thank you
Nicolas
[1] The browser errors :
```
problem with getting settings
Object { headers: {…}, status: 400, statusText: "Bad Request", url: "http://cti-dhcp-prd01.sitpi.lan/api/settings", ok: false, name: "HttpErrorResponse", message: "Http failure response for http://cti-dhcp-prd01.sitpi.lan/api/settings: 400 Bad Request", error: {…} }
main-es2015.5726ecb1650428b6badd.js:1:2678830
ERROR
Object { headers: {…}, status: 400, statusText: "Bad Request", url: "http://cti-dhcp-prd01.sitpi.lan/api/version", ok: false, name: "HttpErrorResponse", message: "Http failure response for http://cti-dhcp-prd01.sitpi.lan/api/version: 400 Bad Request", error: {…} }
main-es2015.5726ecb1650428b6badd.js:1:2036800
GEThttp://cti-dhcp-prd01.sitpi.lan/assets/stork-logo-big.png
[HTTP/1.1 200 OK 74ms]
GEThttp://cti-dhcp-prd01.sitpi.lan/open-sans-v15-latin-regular.ec806460121999bcfb12.woff2
[HTTP/1.1 200 OK 164ms]
GEThttps://fonts.gstatic.com/s/mansalva/v4/aWB4m0aacbtDfvq5NKliKY8.woff2
[HTTP/1.1 200 Connection established 380ms]
GEThttp://cti-dhcp-prd01.sitpi.lan/primeicons.04701ca33ce96d325419.ttf
[HTTP/1.1 200 OK 274ms]
XHRGEThttp://cti-dhcp-prd01.sitpi.lan/api/version
[HTTP/1.1 400 Bad Request 84ms]
XHRGEThttp://cti-dhcp-prd01.sitpi.lan/api/apps-stats
[HTTP/1.1 400 Bad Request 81ms]
Object { headers: {…}, status: 400, statusText: "Bad Request", url: "http://cti-dhcp-prd01.sitpi.lan/api/version", ok: false, name: "HttpErrorResponse", message: "Http failure response for http://cti-dhcp-prd01.sitpi.lan/api/version: 400 Bad Request", error: {…} }
```0.20Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/195Can the DHCPv4 and DHCPv6 be different apps in Stork?2020-09-04T15:08:03ZVicky Riskvicky@isc.orgCan the DHCPv4 and DHCPv6 be different apps in Stork?I know we are not nitpicking the UI yet, but ... I wanted to at least lodge this request.
In the screen shot below, Kea almost always looks RED like there is an alert, because not all Kea apps are running. Can we just list, DHCPv4 or Ke...I know we are not nitpicking the UI yet, but ... I wanted to at least lodge this request.
In the screen shot below, Kea almost always looks RED like there is an alert, because not all Kea apps are running. Can we just list, DHCPv4 or Kea DHCPv4 there, instead of Kea(red) because DHCPV6 isn't running? And of course, DHCPv6 or Kea DHCPv6 if that was running?
![Screen_Shot_2020-03-09_at_1.21.14_PM](/uploads/b8bc0c27b3894426fe63393bede1f5cd/Screen_Shot_2020-03-09_at_1.21.14_PM.png)0.11Vicky Riskvicky@isc.orgVicky Riskvicky@isc.org