Server hangs at startup - issue with lock file and NFS ?
nicolas.chaigneau at capgemini.com
Tue Sep 2 15:00:39 UTC 2014
I have followed the procedure described in http://kea.isc.org/docs/kea-guide.html
I build as follows:
Then I start the server with:
/opt/application/mwpdhcp/products/kea/0.9-beta1/sbin/kea-dhcp4 -c kea.conf -d
Shouldn't the lock file be in "prefix", rather than the build directory ?
Anyway, I've rebuilt with a local copy of the sources, instead of using a NFS.
The server now starts correctly (well almost - my configuration is incorrect; but the server doesn't hang anymore).
De : Jeremy C. Reed [mailto:jreed at isc.org]
Envoyé : mardi 2 septembre 2014 16:42
À : Chaigneau, Nicolas
Cc : kea-dev at lists.isc.org
Objet : Re: Server hangs at startup - issue with lock file and NFS ?
On Tue, 2 Sep 2014, Chaigneau, Nicolas wrote:
> I'm working on a Linux RHEL6 (2.6.32-358.6.2.el6.x86_64) VM.
> Googling a bit, I found other people had similar issues with fcntl:
> "fcntl system call hangs when using F_SETLK with NFS file"
I cannot find any recent issue reports with locking on NFS. Anyone have recent links?
Anyways, we should be able to have the same functionality for this without using the locking. In addition, maybe the routine is not needed with newer log4cplus.
> I believe the lock file should not be created in the sources directory.
That should only be for testing purposes. How did you run kea? (which should identify why it use the source directory)
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