Server hangs at startup - issue with lock file

Chaigneau, Nicolas nicolas.chaigneau at capgemini.com
Mon Sep 22 07:33:39 UTC 2014


Hello,

So I've finally tested your fix with the tarball provided by Jeremy.

As far as I'm concerned, the problem is entirely fixed:
- The default location "${prefix}/var/run/kea" is correctly used
- The environment variable KEA_LOCKFILE_DIR is used when specified
- An error message is displayed when the directory doesn't exist "Unable to use interprocess sync lockfile (No such file or directory): (...)" 
(actually, it is displayed 25 times, not sure if that's what you intended. At least we can't miss it ;)


Thanks.


Regards,
Nicolas.



> On 08.09.2014 08:45, Chaigneau, Nicolas wrote:
> > I'll test your fix, just tell me when it's available.
> The proposed code fix is on branch trac3591. To get it, you can use the following commands:
> 
> git clone git://git.kea.isc.org/kea
> git checkout trac3591
> 
> This code creates lockfile in the ${prefix}/var/run/kea directory.
> However, you can enforce different location by setting up KEA_LOCKFILE_DIR variable. That variable should point out to a writeable directory and must not end with a slash. Also, it can be set to a special value "none", which will disable logging lockfile altogether.
> That is not recommended if you plan to have several processes log to the same output file.
> 
> Please do let me know if this works for you.
> 
> The ticket #3591 (http://kea.isc.org/ticket/3591) will now undergo regular review process. One of the ISC engineers will handle this.
> However, feel free to comment on it if you have any comments or suggestions.
> 
> Thanks for reporting this issue and for testing this fix, Tomek
> 
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.



More information about the kea-dev mailing list