Hi, I checked the formatting of the conf file – ARRGH! It was all over the place so I have started again using a more friendly editor (ATOM)
I also installed kea via RPM – v1.0 only available in CentOs repositories though. I could get it to start using the basic config but as soon as I tried to edit it for MySQL rather than memfile it came up with errors when I tried to run it. I have re-formatted the conf file to make sure all the braces and brackets are in place but still no joy. Lawrence McBride Head of Voice and Data Networks NHS Informatics Merseyside a Saturn House, Knowsley Business Park, Liverpool. L34 9GJ t 0151 296 7668 m 07795 370190 e [email protected] Say hello to us online at www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> or follow us on twitter @nhsimerseyside [Exceptionalsize14] Advance Notification of absence: 17th of August to 6th of September 2018 From: Jason Guy [mailto:[email protected]] Sent: 25 July 2018 18:39 To: McBride Lawrence <[email protected]> Cc: [email protected]; KEA-Users ([email protected]) <[email protected]> Subject: Re: [Kea-users] DHCP4 not starting or writing log file Here are a couple of other ideas: - Have you tried starting the services with the default kea-dhcp4.conf, or perhaps the minimum possible configuration? - If the config was edited in windows, it may have hidden characters. Perhaps execute dos2unix on the configuration file? - Maybe an error in your json formatting? I am not sure what else would cause a seg fault that is kea specific. If it is the config causing it, it would likely be a bug. It is possible there is something about the host you are running on: - lacking something in the architecture 64-bit binary running on 32-bit CPU - some other memory access type of issue. - If it is a VM, the virtual hardware may be running into a problem. Hope this helps, Jason On Wed, Jul 25, 2018 at 6:59 AM McBride Lawrence <[email protected]<mailto:[email protected]>> wrote: Hi Jason, Unfortunately that did not work either. I have searched through as many forums as I can for this and can’t seem to get any closer to an answer. I have just tried running the server directly and got the following: [mcbridl@im-netdhcp1 sbin]$ sudo kea-dhcp4 -c /opt/kea/etc/kea/kea-dhcp4.conf Segmentation fault [mcbridl@im-netdhcp1 sbin]$ Lawrence McBride Head of Voice and Data Networks NHS Informatics Merseyside a Saturn House, Knowsley Business Park, Liverpool. L34 9GJ t 0151 296 7668 m 07795 370190 e [email protected]<mailto:[email protected]> Say hello to us online at www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> or follow us on twitter @nhsimerseyside [Exceptionalsize14] Advance Notification of absence: 17th of August to 6th of September 2018 From: Jason Guy [mailto:[email protected]<mailto:[email protected]>] Sent: 19 July 2018 13:33 To: McBride Lawrence <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; KEA-Users ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>> Subject: Re: [Kea-users] DHCP4 not starting or writing log file Hi Lawrence, I see, you are running this with keactrl. In that case, you should be able to do this: sudo KEA_LOGGER_DESTINATION=/var/log/kea/dhcp4.log keactrl start -s dhcp4 I don't use centos/rhel normally, so I hope this works. Jason On Thu, Jul 19, 2018 at 6:37 AM McBride Lawrence <[email protected]<mailto:[email protected]>> wrote: Hi Jason, So, if I’m understanding you correctly, you suggest creating a service for the dhcp4 server and modifying the kea-dhcp4-server.service file to suit? Lawrence McBride Head of Voice and Data Networks NHS Informatics Merseyside a Saturn House, Knowsley Business Park, Liverpool. L34 9GJ t 0151 296 7668 m 07795 370190 e [email protected]<mailto:[email protected]> Say hello to us online at www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> or follow us on twitter @nhsimerseyside Advance Notification of absence: 17th of August to 6th of September 2018 From: Jason Guy [mailto:[email protected]<mailto:[email protected]>] Sent: 18 July 2018 14:00 To: McBride Lawrence <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; KEA-Users ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>> Subject: Re: [Kea-users] DHCP4 not starting or writing log file Hi Lawrence, For the Debian package, I set these in the systemd service file. If you want to have a look, I am sure you can adjust these the same way, since CentOS uses systemd as well. Here is a link to the kea-ctrl-agent.service<https://salsa.debian.org/debian/isc-kea/blob/master/debian/kea-ctrl-agent.service> file for the debian package. This goes back to the idea I mentioned a few months ago on this list, it would probably be better to have a variable file in /etc/default or /etc/sysconfig (in centos). Here it would allow users to customize the destinations easier. The service simply sources these files to dynamically set the env variables. Cheers, Jason On Wed, Jul 18, 2018 at 6:39 AM McBride Lawrence <[email protected]<mailto:[email protected]>> wrote: Right, I tried export KEA_LOGGER_DESTINATION=stdout as root and then keactrl start -s dhcp4 but I'm still not receiving any error messages. Was my export the correct way to set the variable? Lawrence McBride Head of Voice and Data Networks NHS Informatics Merseyside a Saturn House, Knowsley Business Park, Liverpool. L34 9GJ t 0151 296 7668 m 07795 370190 e [email protected]<mailto:[email protected]> Say hello to us online at www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> or follow us on twitter @nhsimerseyside Advance Notification of absence: 17th of August to 6th of September 2018 -----Original Message----- From: McBride Lawrence Sent: 18 July 2018 11:35 To: 'Marcin Siodelski' <[email protected]<mailto:[email protected]>>; Jason Guy <[email protected]<mailto:[email protected]>> Cc: KEA-Users ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>> Subject: RE: [Kea-users] DHCP4 not starting or writing log file Thanks for that tip. I can see the kea.log file and the lockfile are present in the default dir you mentioned as I successfully got the kea-ctrl-agent to work and there are messages in the file. Where do I set the KEA_LOGGER_DESTINATION environment variable? If I can set it stdout the I should get info on the cli after I issue the start command. Lawrence McBride Head of Voice and Data Networks NHS Informatics Merseyside a Saturn House, Knowsley Business Park, Liverpool. L34 9GJ t 0151 296 7668 m 07795 370190 e [email protected]<mailto:[email protected]> Say hello to us online at www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> or follow us on twitter @nhsimerseyside Advance Notification of absence: 17th of August to 6th of September 2018 -----Original Message----- From: Marcin Siodelski [mailto:[email protected]<mailto:[email protected]>] Sent: 17 July 2018 16:29 To: McBride Lawrence <[email protected]<mailto:[email protected]>>; Jason Guy <[email protected]<mailto:[email protected]>> Cc: KEA-Users ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>> Subject: Re: [Kea-users] DHCP4 not starting or writing log file One of the problems with logging configuration is that until you successfully configure the server it can't really use the log file location specified in the Kea configuration file. Instead it will use default locations. The following section of the Kea User's Guide: https://jenkins.isc.org/job/Kea_doc/guide/kea-guide.html#logging-during-startup describes how to influence where the default logging goes. This may help you determine why the server is not starting. The location of the default log file being used before the server configures is prefix/var/kea/kea.log, where prefix is where Kea server is installed. After the server is started and configured successfully, the logging should go to the locations specified in the Kea config files. Marcin Siodelski ISC Engineering On 17.07.2018 16:49, McBride Lawrence wrote: > Centos 7.4 > > > > *Lawrence McBride* > > Head of Voice and Data Networks > > > > *NHS Informatics Merseyside* > > *a *Saturn House, Knowsley Business Park, Liverpool. L34 9GJ > > *t *0151 296 7668 > > *m *07795 370190** > > *e > *[email protected]<mailto:[email protected]> > > > > Say helloto us online at www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> > <http://www.imerseyside.nhs.uk>or follow uson twitter @nhsimerseyside > > > > Exceptionalsize14 > > * * > > Advance Notification of absence: > > 17^th of August to 6^th of September 2018 > > > > *From:*Jason Guy > [mailto:[email protected]<mailto:[email protected]>] > *Sent:* 17 July 2018 15:35 > *To:* McBride Lawrence > <[email protected]<mailto:[email protected]>> > *Cc:* KEA-Users ([email protected]<mailto:[email protected]>) > <[email protected]<mailto:[email protected]>> > *Subject:* Re: [Kea-users] DHCP4 not starting or writing log file > > > > Was this installed from the Debian Sid repo, or is this on RHEL/CentOS? > > > > Thanks, > Jason > > > > On Tue, Jul 17, 2018 at 10:18 AM McBride Lawrence > <[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>> > wrote: > > Hi, > > > > Sorry, > > > > Version 1.4 > > File and dir exist > > I am starting the services as root > > > > *Lawrence McBride* > > Head of Voice and Data Networks > > > > *NHS Informatics Merseyside* > > *a *Saturn House, Knowsley Business Park, Liverpool. L34 9GJ > > *t *0151 296 7668 > > *m *07795 370190 > > *e > *[email protected]<mailto:[email protected]> > > <mailto:[email protected]<mailto:[email protected]>> > > > > Say helloto us online at > www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> > <http://www.imerseyside.nhs.uk>or follow uson twitter > @nhsimerseyside > > > > Exceptionalsize14 > > * * > > Advance Notification of absence: > > 17^th of August to 6^th of September 2018 > > > > *From:*Jason Guy > [mailto:[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>] > *Sent:* 17 July 2018 14:38 > *To:* McBride Lawrence > <[email protected]<mailto:[email protected]> > > <mailto:[email protected]<mailto:[email protected]>>> > *Cc:* KEA-Users ([email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>) > <[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>> > *Subject:* Re: [Kea-users] DHCP4 not starting or writing log file > > > > Hi Lawrence, > > > > First, what version of Kea are you using? > > Does the log directory exist? I am not sure if kea will create the > directory, as well as the file. > > Finally, make sure to start the service as root or using sudo. > > > > Jason > > > > On Tue, Jul 17, 2018 at 6:02 AM McBride Lawrence > > <[email protected]<mailto:[email protected]> > > <mailto:[email protected]<mailto:[email protected]>>> > wrote: > > Hi, > > > > I am starting just the dhcp4 server with the following command: > > > > keactrl start -s dhcp4 > > > > I get a corresponding message to say it is starting: > > > > INFO/keactrl: Starting /opt/kea/sbin/kea-dhcp4 -c > /opt/kea/etc/kea/kea-dhcp4.conf > > > > However, it doesn’t start as the status output shows: > > > > keactrl status > > DHCPv4 server: inactive > > DHCPv6 server: inactive > > DHCP DDNS: inactive > > Control Agent: inactive > > Kea DHCPv4 configuration file: /opt/kea/etc/kea/kea-dhcp4.conf > > Kea DHCPv6 configuration file: /opt/kea/etc/kea/kea-dhcp6.conf > > Kea DHCP DDNS configuration file: > /opt/kea/etc/kea/kea-dhcp-ddns.conf > > Kea Control Agent configuration file: > /opt/kea/etc/kea/kea-ctrl-agent.conf > > keactrl configuration file: /opt/kea/etc/kea/keactrl.conf > > > > > > I get no log output either so have no idea what is going on – > logging config below: > > > > "loggers": [ > > { > > // This section affects kea-dhcp4, which is the base > logger for DHCPv4 > > // component. It tells DHCPv4 server to write all log > messages (on > > // severity INFO or more) to a file. > > "name": "kea-dhcp4", > > "output_options": [ > > { > > "output": "/opt/kea/var/log/kea-dhcp4.log" > > // This governs whether the log output is > flushed to disk after > > // every write. > > // "flush": false, > > // This specifies the maximum size of the file > before it is > > // rotated. File size is set to 10MB > (10240000) > > "maxsize": 10240000, > > // This specifies the maximum number of rotated > files to keep. > > "maxver": 8 > > } > > ], > > > > *Lawrence McBride* > > Head of Voice and Data Networks > > > > *NHS Informatics Merseyside* > > *a *Saturn House, Knowsley Business Park, Liverpool. L34 9GJ > > *t *0151 296 7668 > > *m *07795 370190 > > *e > *[email protected]<mailto:[email protected]> > > <mailto:[email protected]<mailto:[email protected]>> > > > > Say helloto us online at > www.imerseyside.nhs.uk<http://www.imerseyside.nhs.uk> > <http://www.imerseyside.nhs.uk>or follow uson twitter > @nhsimerseyside > > > > > > * * > > Advance Notification of absence: > > 17^th of August to 6^th of September 2018 > > > > _______________________________________________ > Kea-users mailing list > [email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>> > https://lists.isc.org/mailman/listinfo/kea-users > > > > _______________________________________________ > Kea-users mailing list > [email protected]<mailto:[email protected]> > https://lists.isc.org/mailman/listinfo/kea-users >
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
