bind syslog messages
Cricket Liu
cricket at nxdomain.com
Mon Jan 27 22:51:49 UTC 2003
On Monday, January 27, 2003, at 01:57 PM, Brendan McSweeney wrote:
> this is from my syslog:
>
> Jan 27 03:09:22 Headlevel named[102]: db_load could not open:
> caching-example/named.ca: No such file or directory
> Jan 27 03:09:22 Headlevel named[102]: db_load could not open:
> caching-example/localhost.zone: No such file or directory
> Jan 27 03:09:22 Headlevel named[102]: db_load could not open:
> caching-example/named.local: No such file or directory
> Jan 27 03:09:22 Headlevel named[102]: db_load could not open:
> caching-example/named.ca: No such file or directory
>
> what does it mean, and how do i fix it?
Your named.conf file refers to several files in the caching-example
subdirectory of the name server's working directory, and those files
don't exist. To fix it, either create the files or fix named.conf so
that
it doesn't refer to those files anymore.
cricket
More information about the bind-users
mailing list