Maintained by: NLnet Labs

[Unbound-users] You have got to be kidding me: fatal error: Could not read config file

W.C.A. Wijngaards
Fri May 25 11:47:41 CEST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David,

On 05/25/2012 11:27 AM, David Benfell wrote:
> Hello all,
> 
> This is Arch Linux, so probably an upgrade did me in:
> 
> atlanta# rc.d start unbound :: Starting unbound daemon
> 
> [FAIL] atlanta# pacman -Ss unbound community/unbound 1.4.17-1
> [installed] Validating, recursive, and caching DNS resolver 
> atlanta# ls -ald /etc/unbound drwxr-xr-x 2 root root 1024 May 25
> 02:22 /etc/unbound atlanta# ls -al /etc/unbound total 81 drwxr-xr-x
> 2 root    root  1024 May 25 02:22 . drwxr-xr-x 83 root    root
> 4096 May 25 02:22 .. -rwx------  1 unbound root   759 Feb  3 07:57
> dnssec_root.key -rw-r--r--  1 root    root   350 Jan  8 17:49
> local-zone.conf -rw-r--r--  1 unbound root   759 Jan  8 17:49
> root.key -rw-r--r--  1 root    root 23455 May 18 23:47
> unbound.conf -rw-r--r--  1 root    root 20061 Jan  8 17:49
> unbound.conf.dpkg-dist -rw-r--r--  1 root    root 21209 May 24
> 06:40 unbound.conf.example -rw-r-----  1 root    root  1277 Jan  8
> 17:49 unbound_control.key -rw-r-----  1 root    root   802 Jan  8
> 17:49 unbound_control.pem -rw-r-----  1 root    root  1277 Jan  8
> 17:49 unbound_server.key -rw-r-----  1 root    root   790 Jan  8
> 17:49 unbound_server.pem atlanta# unbound 
> /etc/unbound/unbound.conf:572: error: syntax error read
> /etc/unbound/unbound.conf failed: 1 errors in configuration file 
> [1337937787] unbound[3676:0] fatal error: Could not read config
> file: /etc/unbound/unbound.conf
> 
> As you can see, the file exists. This *was* working until
> recently. Now I discover it is *not* working. So what's new that
> broke this?

What does it say on line 572 (and the lines right before it) ?

There should be no changes that break backwards compatibility.  Some
options have been added.

The error you see is from lex (flex), its lexical parser fails to
split the input into keywords and data values, so this is a syntax
error, not a grammar error or bad config value.

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPv1U9AAoJEJ9vHC1+BF+NnrQP/jDjVj5Tw30bf7ibCTKdDf5e
hHnpStv1Ru22TgRyVkNkoq2uRiBqIAAJ2YZTY90McBI43ddLe4jXfi2fjqaM7zEn
8EvLymWulhOl/6j7G/1xMFcE+7HzVZXYkkDFXLbKkXldHPF7W+NWv2SocjRL91T9
HXnreSE5ooZjNn7N4v05jxfhzcQkQ2jaiu2aHtTbcPLiFUE8Ow/AhzW+QilxXBQK
meEB9L3eU0jRqsrwyqzed/n6lpeoBMnYDCSUk+/CyaHSn5NazUW6tOP4K/r+f5Oa
EP4mjz+ZPc82zf51lbZTleOZSx2v1lP0vD7KOMpfKt8xRVBAwwsO1NCEtuT0Tx44
yfQeNyGXlItBec4RvRA5aW1hC4HUGhxAxKpfhXoUX4zcrll7I3T3Xi73xq62MTDJ
BLwT+Ltal8L2IIhdlE/7oIZ9icnKb9siia2CHVEPrxkXzKk/d8V22R5pI27UKjWS
a2bwPiBiIwVxDAYOIq3DsEOmZtenjbTecP9KJKebGOPyZ323XzVetgaDIcKucMnx
9q3yW6o7zqDWWXMMvYZETEVgCf3zqlthB3uCqArrqb4dHhv8dLrOcoN+oK8oEItV
ipHGrZKTETY/zbm+Ch46nvPOvo9uhLd6vaIK+6JaIWt8ixiKEVwELSvY3nEKjaTT
rG0zhBvIdbZHDhL16zMy
=n3bt
-----END PGP SIGNATURE-----