Journal open failed.

kalyanasundaram S s.kalyanasundaram at
Thu Jun 15 12:56:32 UTC 2006

> -----Original Message-----
> From: mark_andrews at
> Sent: Thu, 15 Jun 2006 17:19:50 +1000
> To: stefan.puiu at
> Subject: Re: Journal open failed.
> 	See the FAQ answer to
> Q: I'm running BIND on Red Hat Enterprise Linux or Fedora Core -
>         Why can't named update slave zone database files?
> 	Why can't named create DDNS journal files or update the master
> 	zones from journals?
> 	Why can't named create custom log files?
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at
is that SELinux policy applied to SLES also?
i did not had any directory /var/named/slaves
  so just simply create and placed the file and did "rcnamed start" it said journal not found /var/named/slaves/ I am sure i have not done any spelling mistake

2. Then i copied the entire /var/lib/named as /var/named
  changed /etc/named.conf for the option directory -> "/var/named"
   in zone declaration i have made file "slaves/"
   bind-chroot is installed but there is no ROOTDIR variable in /etc/sysconfig/named.
   so i made it at the bootm ROOTDIR="" so that /var/named/slaves will be available..
   and tried to run using "rcnamed start" it says unable to change the directory /var/named 
   but it is available too.. i checked with mode 777 on the named directory also. but still same problem.

what mistake i am doing? shall i post my configuration files?..
is that SELinux security policy applies to SLES also?
somehow i want to run it. i am new to this. let me make it first then think for the security.

More information about the bind-users mailing list