From mcnally at isc.org Wed Jul 1 17:56:54 2020 From: mcnally at isc.org (Michael McNally) Date: Wed, 1 Jul 2020 09:56:54 -0800 Subject: [stork-users] Stork 0.9.0 is now available Message-ID: <2285af44-37d1-1282-0ab1-a1fdb356441b@isc.org> Stork 0.9.0 is a new development release of the Stork monitoring and configuration dashboard and it can be downloaded from: https://www.isc.org/download Documentation for Stork is available at https://stork.readthedocs.io. ----- # Stork 0.9.0, July 1st, 2020, Release Notes Welcome to the Stork 0.9.0 release. This is a development release of the Stork project, which is a modern, responsive, and scalable dashboard for Kea and BIND 9 with a well-defined REST API interface. The long-term goal of the project is to provide a monitoring and management solution for BIND 9 and Kea DHCP. This release does not feature any major new features. Instead, the team decided to spend some time fixing bugs and generally improving the quality of the software. The bug fixes and changes introduced in this version are: 1. **Dashboard tweaks**. Several small adjustments were made in the Stork dashboard; the most notable one is that it now shows pool utilization as a progress bar. #235 2. **Build improvements**. A workaround for building in Docker running on Ubuntu 20.04 was added (#323), the database setup and cleanup for building and running unit-tests were improved (#322), and the binaries can now return their own compilation version: try `stork-server --version` or `stork-agent -v` (#265). 3. **BIND 9 Prometheus improvements**. BIND 9 handling routines now correctly unregister all collectors (#326), and do not log an error on missing BIND 9 stats (#319). 4. **Security hardening**. Issues with the initial retrieval of user groups has been fixed (#331), the traffic generators used in the demo are functional again (#329), and the 403 (access forbidden) error now has its own landing page (#327). 5. **Bugfixes**. A problem with showing a blank page after logging in has been fixed (#330), pulling host reservations from a Kea server should now work better (#305), and we have implemented our own DefaultRegisterer (#261). ## Release Model Stork has monthly development releases on the first Wednesday of each month (with some exceptions around holidays), although we sometimes delay it a bit for last-minute changes. We encourage users to test the development releases and report back their findings on the stork-users mailing list, available at https://lists.isc.org/mailman/listinfo/stork-users. This text references issue numbers. For more details, visit the Stork GitLab page at https://gitlab.isc.org/isc-projects/stork/issues. ## License This version of Stork is released under the Mozilla Public License, version 2.0. https://www.mozilla.org/en-US/MPL/2.0 ## Download The easiest way to install the software is to use native deb or RPM packages. They can be downloaded from: https://cloudsmith.io/~isc/repos/stork/ The Stork source and PGP signature for this release may be downloaded from: https://downloads.isc.org/isc/stork The signature was generated with the ISC code signing key which is available at: https://www.isc.org/pgpkey ISC provides documentation in the Stork Administrator Reference Manual. It is currently available only in the source form in the docs/ directory, and the Sphinx tool is required to build it. This is expected to change in a future release. We ask users of this software to please let us know how it worked for you and what operating system you tested on. Feel free to share your feedback on the stork-users mailing list (https://lists.isc.org/mailman/listinfo/stork-users). We would also like to hear whether the documentation is adequate and accurate. Please open tickets in the Stork GitLab project for bugs, documentation omissions and errors, and enhancement requests. We want to hear from you even if everything worked. ## Support Professional support for Stork will become available once it reaches the 1.0 milestone. Existing ISC customers that consider themselves *very* early adopters may get involved in the development process, including roadmap, features planning, and early testing, but the software maturity level does not constitute a typical professional service before the 1.0 milestone. Free best-effort support is provided by our user community via a mailing list. Information on all public email lists is available at https://www.isc.org/mailinglists/. If you have any comments or questions about working with Stork, please share them to the stork-users list (https://lists.isc.org/mailman/listinfo/stork-users). Bugs and feature requests may be submitted via GitLab at https://gitlab.isc.org/isc-projects/stork/issues. ## Changes The following summarizes changes and important upgrades since the Stork 0.8.0 release. * 76 [func] marcin Pool utilization in the Stork dashboard is shown with a progress bar. (Gitlab #235) * 75 [bug] matthijs BIND exporter did not unregister all Prometheus collectors on shutdown. (Gitlab #326) * 74 [bug] marcin Fixed a security problem whereby an unlogged user had access to some restricted pages. If the unlogged user tries to access a restricted page, the user is redirected to the login page. If the user tries to access a page without proper privileges, the HTTP 403 page is displayed. (Gitlab #119) * 73 [func] marcin Monitor communication issues between Stork and the applications. If there is a communication problem with any app it is highlighted via appropriate icon and a text that describes the problem. The server logs were adjusted to indicate if the communication issue is new or has been occurring for a longer period of time. (Gitlab #305) * 72 [func] tomek Implemented version reporting in agent and server. (Gitlab #265) Thank you again to everyone who assisted us in making this release possible. We look forward to receiving your feedback. From jtinsley at lrecok.coop Wed Jul 15 20:00:06 2020 From: jtinsley at lrecok.coop (Jordan Tinsley) Date: Wed, 15 Jul 2020 15:00:06 -0500 Subject: [stork-users] Stuck in Setup Message-ID: Hello, I am stuck in the middle of setup of Stork on Centos 7.? I am following the Stork Latest Documentation for installing from Centos Packages.? I have postgresql configured properly (I believe) and have the server.env file for Stork configured correctly.? However, I am stuck with the following error message when I try to start the isc-stork-server service - Jul 15 14:41:55 kea-stork systemd: Started ISC Stork Server. Jul 15 14:41:55 kea-stork stork-server: #033[36mINFO#033[0m[2020-07-15 14:41:55]?????? connection.go:29 checking connection to database Jul 15 14:41:55 kea-stork stork-server: #033[31mFATA#033[0m[2020-07-15 14:41:55]???????????? main.go:22 unexpected error: ERROR #42601 syntax error at or near "AS" Jul 15 14:41:55 kea-stork stork-server: problem with migrating database Jul 15 14:41:55 kea-stork stork-server: isc.org/stork/server/database.Migrate Jul 15 14:41:55 kea-stork stork-server: /build/backend/server/database/migrations.go:55 Jul 15 14:41:55 kea-stork stork-server: isc.org/stork/server/database.MigrateToLatest Jul 15 14:41:55 kea-stork stork-server: /build/backend/server/database/migrations.go:64 Jul 15 14:41:55 kea-stork stork-server: isc.org/stork/server/database.NewPgDB Jul 15 14:41:55 kea-stork stork-server: /build/backend/server/database/connection.go:62 Jul 15 14:41:55 kea-stork stork-server: isc.org/stork/server.NewStorkServer Jul 15 14:41:55 kea-stork stork-server: /build/backend/server/server.go:103 Jul 15 14:41:55 kea-stork stork-server: main.main Jul 15 14:41:55 kea-stork stork-server: /build/backend/cmd/stork-server/main.go:20 Jul 15 14:41:55 kea-stork stork-server: runtime.main Jul 15 14:41:55 kea-stork stork-server: /build/tools/1.13.5/go/src/runtime/proc.go:203 Jul 15 14:41:55 kea-stork stork-server: runtime.goexit Jul 15 14:41:55 kea-stork stork-server: /build/tools/1.13.5/go/src/runtime/asm_amd64.s:1357 Jul 15 14:41:55 kea-stork systemd: isc-stork-server.service: main process exited, code=exited, status=1/FAILURE Jul 15 14:41:55 kea-stork systemd: Unit isc-stork-server.service entered failed state. Jul 15 14:41:55 kea-stork systemd: isc-stork-server.service failed. Thanks! From ko at sv01.de Sat Jul 18 23:42:44 2020 From: ko at sv01.de (Kevin Olbrich) Date: Sun, 19 Jul 2020 01:42:44 +0200 Subject: [stork-users] Default admin account does not work on fresh installation Message-ID: Hi! I did a fresh install using the prebuilt images on debian buster. After setting up PG and isc-stork-server and trying to login, this is being logged: Jul 19 01:33:23 dhcp02.intra.srvfarm.net systemd[1]: Started ISC Stork Server. Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] connection.go:29 checking connection to database Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] connection.go:77 connected to database 127.0.0.1:5432, schema version: 25 Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] eventcenter.go:49 Started EventCenter Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:38 starting BIND 9 Stats Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:71 started BIND 9 Stats Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:38 starting Kea Stats Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:71 started Kea Stats Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:38 starting Kea Hosts Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:71 started Kea Hosts Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:38 starting Kea Status Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] puller.go:71 started Kea Status Puller Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] eventcenter.go:109 event 'started Stork server' Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] main.go:25 Starting Stork Server, version 0.9.0, build date 2020-07-01 08:23 Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] middleware.go:48 installed file server middleware Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] middleware.go:68 installed SSE middleware Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] middleware.go:19 installed logging middleware Jul 19 01:33:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:23] restservice.go:240 started serving Stork Server address="http://[::]:8080" Jul 19 01:33:42 dhcp02.intra.srvfarm.net stork-server[13659]: ERRO[2020-07-19 01:33:42] users.go:71 error while creating new session identifier: pq: password authentication failed for user "stork" Jul 19 01:33:42 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:42] middleware.go:42 served request method=POST path="/api/sessions?useremail=admin&userpassword=admin" remote="1 Jul 19 01:33:43 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:43] middleware.go:42 served request method=GET path="/login?returnUrl=%2F" remote="192.168.81.221:58602" took="95 Jul 19 01:33:44 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:44] middleware.go:42 served request method=GET path=/api/version remote="192.168.81.221:58602" took="131.967?s" Jul 19 01:33:44 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:44] middleware.go:42 served request method=GET path=/api/version remote="192.168.81.221:58608" took="112.311?s" Jul 19 01:33:44 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:44] middleware.go:42 served request method=GET path=/favicon.ico remote="192.168.81.221:58608" took=2.53726ms Jul 19 01:33:46 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:46] middleware.go:42 served request method=GET path=/api/version remote="192.168.81.221:58608" took="66.381?s" Jul 19 01:33:46 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:46] middleware.go:42 served request method=GET path=/api/version remote="192.168.81.221:58608" took="39.518?s" Jul 19 01:33:50 dhcp02.intra.srvfarm.net stork-server[13659]: ERRO[2020-07-19 01:33:50] users.go:71 error while creating new session identifier: pq: password authentication failed for user "stork" Jul 19 01:33:50 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:50] middleware.go:42 served request method=POST path="/api/sessions?useremail=admin&userpassword=admin" remote="1 Jul 19 01:33:53 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:33:53] status.go:333 completed pulling DHCP status from Kea apps: 0/0 succeeded Jul 19 01:34:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:34:23] statspuller.go:63 completed pulling stats from BIND 9 apps: 0/0 succeeded Jul 19 01:34:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:34:23] status.go:333 completed pulling DHCP status from Kea apps: 0/0 succeeded Jul 19 01:34:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:34:23] statspuller.go:101 completed pulling lease stats from Kea apps: 0/0 succeeded Jul 19 01:34:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:34:23] host.go:100 completed pulling hosts from Kea apps: 0/0 succeeded Jul 19 01:34:53 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:34:53] status.go:333 completed pulling DHCP status from Kea apps: 0/0 succeeded Jul 19 01:35:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:35:23] statspuller.go:63 completed pulling stats from BIND 9 apps: 0/0 succeeded Jul 19 01:35:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:35:23] statspuller.go:101 completed pulling lease stats from Kea apps: 0/0 succeeded Jul 19 01:35:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:35:23] status.go:333 completed pulling DHCP status from Kea apps: 0/0 succeeded Jul 19 01:35:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:35:23] host.go:100 completed pulling hosts from Kea apps: 0/0 succeeded Jul 19 01:35:42 dhcp02.intra.srvfarm.net stork-server[13659]: ERRO[2020-07-19 01:35:42] users.go:71 error while creating new session identifier: pq: password authentication failed for user "stork" Jul 19 01:35:42 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:35:42] middleware.go:42 served request method=POST path="/api/sessions?useremail=admin&userpassword=admin" remote="1 Jul 19 01:35:53 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:35:53] status.go:333 completed pulling DHCP status from Kea apps: 0/0 succeeded Jul 19 01:36:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:36:23] statspuller.go:63 completed pulling stats from BIND 9 apps: 0/0 succeeded Jul 19 01:36:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:36:23] statspuller.go:101 completed pulling lease stats from Kea apps: 0/0 succeeded Jul 19 01:36:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:36:23] status.go:333 completed pulling DHCP status from Kea apps: 0/0 succeeded Jul 19 01:36:23 dhcp02.intra.srvfarm.net stork-server[13659]: INFO[2020-07-19 01:36:23] host.go:100 completed pulling hosts from Kea apps: 0/0 succeeded ... As the schema has been loaded, db credentials should be fine. Where is this authentication failed error coming from? Kind regards Kevin