[kea-dev] Kea0.9 tarball - lockfile problem

[Angelo Failla]

Hi,

We have started looking into migrating from bind10 to kea0.9 here at FB and I have a question about a problem I’ve noticed with lock file feature.
If I start the server it exits with status code 1:

$ _build/opt/syseng/kea/server/kea-dhcp4 -c syseng/kea/server/example.config.json
[Exit code 1 @ 08:19:42]

The current configuration file is this one (don’t worry about 0.0.0.0/0, we use a hook library to deal with everything, the "hooks-libraries": [ "” ] is needed because we compile all binaries statically at FB so the hook library is already embedded into the binary):

$ cat syseng/kea/server/example.config.json
{

"Dhcp4": {
    "hooks-libraries": [ "" ],
    "interfaces": [ ],
    "valid-lifetime": 4000,
    "renew-timer": 1000,
    "rebind-timer": 2000,
    "subnet4": [{
       "pool": "0.0.0.0-255.255.255.255",
       "subnet": "0.0.0.0/0"
    }]
},

"Logging": {
  "loggers": [
    {
     "name": "kea",
     "output_options": [{"output": "stdout"}],
     "severity": "INFO",
     "debuglevel": 0
    }
  ]
}

}


stracing the process it seems to be looking for a lock file in the build directory...

$ strace _build/opt/syseng/kea/server/kea-dhcp4 -c syseng/kea/server/example.config.json 2>&1 | grep engshare
open("/home/engshare/third-party2/kea/0.9/src/build-gcc-4.8.1-glibc-2.17-fb/no-pic/logger_lockfile", O_RDWR|O_CREAT, 0660) = -1 ENOENT (No such file or directory)
open("/home/engshare/third-party2/kea/0.9/src/build-gcc-4.8.1-glibc-2.17-fb/no-pic/logger_lockfile", O_RDWR|O_CREAT, 0660) = -1 ENOENT (No such file or directory)
open("/home/engshare/third-party2/kea/0.9/src/build-gcc-4.8.1-glibc-2.17-fb/no-pic/logger_lockfile", O_RDWR|O_CREAT, 0660) = -1 ENOENT (No such file or directory)
open("/home/engshare/third-party2/kea/0.9/src/build-gcc-4.8.1-glibc-2.17-fb/no-pic/logger_lockfile", O_RDWR|O_CREAT, 0660) = -1 ENOENT (No such file or directory)

I read about a KEA_LOCKFILE_DIR env variable in the ChangeLog:

838.  [bug]   tomek
  Kea components now use the KEA_LOCKFILE_DIR environment variable
  to specify the directory of the logging lockfile. Locking can be
  disabled completely by setting the variable to 'none'.
  (Trac #3591, git d4556e1d21766b94f2f0cda59df15e47e6f2676e)

I tried setting that to ‘none’ but it didn’t help:

$ export KEA_LOCKFILE_DIR='/tmp/'
[Exit code 0 @ 08:24:04]
$ sudo _build/opt/syseng/kea/server/kea-dhcp4 -c syseng/kea/server/example.config.json 2>&1 | grep engshare
[Exit code 1 @ 08:24:11]

Any idea?
--
Angelo Failla
Cluster Ops - Dublin
Pallotron at fb.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-dev/attachments/20141015/c0495d27/attachment.html>