On 3/5/21 1:41 PM, Bruce Johnson wrote:
Turne out to be a dumdum mistake on my part. SELinux was set to
enforce…set it to permissive and voila! the .jnl file was created.
Ah.
That sounds like an SELinux policy problem. SELinux /should/ allow
named to create journal files.
A non-default loc
Turne out to be a dumdum mistake on my part. SELinux was set to enforce…set it
to permissive and voila! the .jnl file was created.
I coulda sworn I’d fixed that before...
> On Mar 5, 2021, at 12:39 PM, Grant Taylor via bind-users
> wrote:
>
> On 3/5/21 12:07 PM, Bruce Johnson wrote:
>> Fixin
named process is running as ’named’:
named 45631 1.0 11.8 411576 220744 ? Ssl 11:28 0:57
/usr/sbin/named -u named -c /etc/named.conf -t /var/named/chroot
if I run su --shell=/bin/sh named
I can create files in the directory the journal file should be.
On Mar 5, 2021, at 12:39
On 3/5/21 12:07 PM, Bruce Johnson wrote:
Fixing the permissions and restarting named got dynamic updating
working again, but new systems (ie names that are NOT already in
the Zone file ) are throwing errors about the journal file: error:
journal open failed: unexpected error
It seems like you
I”m running it as named-chroot, and named is rw permissions at the /var/named
This is the directory listing:
[root@mydns named]# ls -l
total 16
drwxr-x---. 7 named named 61 Oct 9 13:30 chroot
drwxrwx---. 2 named named 127 Feb 28 03:27 data
drwxrwx---. 2 named named 60 Mar 4 13:57 dynamic
d
Fixing the permissions and restarting named got dynamic updating working again,
but new systems (ie names that are NOT already in the Zone file ) are throwing
errors about the journal file: error: journal open failed: unexpected error
Mar 5 11:44:34 mydns named[45631]: client @0x7fa31f4178d0
1
6 matches
Mail list logo
