Hi Bill:
Did you build from the beta tar ball? 'kea-admin' is a shell script
that gets generated from 'kea-admin.in' during the configure process.
During
this generation the values supplied to configure, such as --prefix are
used to construct the paths to scripts and what not. If you used our
tar ball and did a configure, then make install, the paths would have
to match. T
The only explanation I have is that the value given to the configure
script with --prefix is not where everything was installed.
Thomas
On 05/21/2018 01:27 PM, Bill Pye wrote:
Hi Thomas
Sorry about the delay, this has been slightly tortuous for me and the error
seems to remain.
I ran the command you supplied with my for the 'lease-update' and it runs and
gives the following output: Lease DB version reported before upgrade: mysql:
[Warning] Using a password on the command line interface can be insecure.
5.1
Processing /usr/share/kea/scripts/mysql/upgrade_1.0_to_2.0.sh file...
/usr/share/kea/scripts/mysql/upgrade_1.0_to_2.0.sh: line 8:
/builddir/build/BUILD/kea-1.4.0-beta/src/bin/admin/admin-utils.sh: No such file
or directory
-- all the intervening scripts show the same message--
Processing /usr/share/kea/scripts/mysql/upgrade_5.2_to_6.0.sh file...
/usr/share/kea/scripts/mysql/upgrade_5.2_to_6.0.sh: line 8:
/builddir/build/BUILD/kea-1.4.0-beta/src/bin/admin/admin-utils.sh: No such file
or directory
Lease DB version reported after upgrade: mysql: [Warning] Using a password on
the command line interface can be insecure.
5.1
I then specified the correct directory on the command line: "-d /usr/share/kea/scripts"
and that still fails with the same error, I assume this isn't picking up the correct
"prefix".
Regards
Bill
----- Original Message -----
From: "Thomas Markwalder" <[email protected]>
To: "kea-users" <[email protected]
Sent: Monday, 21 May, 2018 15:51:04
Subject: Re: [Kea-users] Kea-1.4.0-beta CentOS rpm
Hey Bill:
I updated our release notes and have created ticket #5629 to add a
version-check-and-error to our MySQL DB code. Our PostgreSQL code
checks upon connect but somehow that got missed in our MySQL code. Once
that's in you'll get a much more helpful message telling you that the
schema version is wrong.
Also, I mis-stated the kea-admin command it should be "lease-upgrade"
not "upgrade":
$ kea-admin lease-upgrade mysql -u database-user -p database-password -n
database-name
Cheers,
Thomas
On 05/21/2018 09:26 AM, Bill Pye wrote:
Hi Thomas
I thought it must be something obvious, my apologies if I missed it. I did
search the documentation but didn't find anything, I'll give that a try shortly
and post the results but I'm sure it will work. :)
Regards
Bill
----- Original Message -----
From: "Thomas Markwalder" <[email protected]>
To: "kea-users" <[email protected]>
Sent: Monday, 21 May, 2018 14:58:47
Subject: Re: [Kea-users] Kea-1.4.0-beta CentOS rpm
Hi Bill:
You need to upgrade your database:
$ kea-admin upgrade mysql -u database-user -p database-password -n
database-name
We need to make this prominently clear in the release notes.
Regards,
Thomas Markwalder
ISC Software Engineering
On 05/21/2018 08:55 AM, Bill Pye wrote:
Hi Rasmus
Thanks for providing this beta. :)
I've just installed this on a test server and I've hit a problem, when I start
kea I'm seeing this message:
May 21 14:45:17 centosdev.phoenix-systems.uk.com kea-dhcp4[62043]: 2018-05-21
14:45:17.023 ERROR [kea-dhcp4.dhcp4/62043] DHCP4_INIT_FAIL failed to initialize
Kea server: configuration error using file '/etc/kea/kea-dhcp4.conf': Unable to
open database: unable to prepare MySQL statement <SELECT subnet_id, state,
leases as state_count FROM lease4_stat ORDER BY subnet_id, state>, reason:
Table 'kea.lease4_stat' doesn't exist
I'm using a centos 7.5 server (up to date) with a Percona Server (the latest
5.7) for the lease info, if that makes any difference. First of all I tried to
use an existing DB, it fails with the above error. I've also tried this with a
clean install and a clean DB created manually and also initialized with
"kea-admin lease-init" - it still failed with the same error.
Am I missing something obvious that might be causing this problem or should I
file this as a bug?
Regards
Bill
----- Original Message -----
From: "Rasmus Edgar" <[email protected]>
To: "kea-users" <[email protected]>
Sent: Monday, 21 May, 2018 09:23:23
Subject: [Kea-users] Kea-1.4.0-beta CentOS rpm
Hi,
I've updated my copr Kea repo with a build of Kea-1.4.0-beta:
https://copr.fedorainfracloud.org/coprs/redgar/kea/
The srpm and spec file can be found here:
https://github.com/RasmusEdgar/kea-centos-srpms
I had an issue with building kea-1.4.0-beta using boost-devel 1.53 that
EPEL provides, which does not include boost/asio/coroutine.hpp. In order
to get it build I used the following boost repo:
https://www.softwarecollections.org/en/scls/denisarnaud/boost157/epel-7-x86_64/download/denisarnaud-boost157-epel-7-x86_64.noarch.rpm
Boost157-devel is also needed to install kea-1.4.0-beta.
Boost157 libraries and headers will not conflict with boost 1.53.
Best regards,
Rasmus Edgar
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
