Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

On 10-06-2022 17:21, Reindl Harald wrote: My apologies if I offended you. seriously - about what magic are you talking? do you even know what a pidfile is? it's a simple textfile where the process writes it's PID and PIDFile forces systemd to read that file and use the content as "Main PID"

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

Am 10.06.22 um 17:07 schrieb Sandro: On 10-06-2022 16:02, Reindl Harald wrote: come on! the OP clearly stated the only problem is the "PIDFile" line in the systemd-unit and so what named writes or not is completly irrelevant "PIDFile" for systemd has nothing to do with "pid-file" of named

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

On 10-06-2022 16:02, Reindl Harald wrote: come on! the OP clearly stated the only problem is the "PIDFile" line in the systemd-unit and so what named writes or not is completly irrelevant "PIDFile" for systemd has nothing to do with "pid-file" of named :facepalm: Indeed. I was led down

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

Am 10.06.22 um 15:56 schrieb Sandro: On 10-06-2022 15:27, Reindl Harald wrote: Am 10.06.22 um 15:22 schrieb Sandro: On 10-06-2022 12:53, Reindl Harald wrote: if it would be useful my "ExecReload=/usr/bin/kill -HUP $MAINPID" won't work for nearly 10 years without "PIDFile" (no i won't use

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

On 10-06-2022 15:27, Reindl Harald wrote: Am 10.06.22 um 15:22 schrieb Sandro: On 10-06-2022 12:53, Reindl Harald wrote: if it would be useful my "ExecReload=/usr/bin/kill -HUP $MAINPID" won't work for nearly 10 years without "PIDFile" (no i won't use and configure rndc - keep it simple)

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

Am 10.06.22 um 15:22 schrieb Sandro: On 10-06-2022 12:53, Reindl Harald wrote: if it would be useful my "ExecReload=/usr/bin/kill -HUP $MAINPID" won't work for nearly 10 years without "PIDFile" (no i won't use and configure rndc - keep it simple) That's a personal choice, but probably not

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

On 10-06-2022 10:52, Søren Andersen wrote: I've installed a fresh BIND on a RHEL 8.6 system with enforcing SElinux, and when I try to start BIND with the provided systemd unit file it just waits and timeout, and also logs these errors in /var/log/message Jun 10 10:09:25 systemd[1]:

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

Am 10.06.22 um 12:59 schrieb Søren Andersen: I think the source of the systemd unit file is from: https://gitlab.isc.org/isc-packages/rpms/bind/-/blob/main/named.service.in (And I'm using ISC's repo) Perhaps 

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

I think the source of the systemd unit file is from: https://gitlab.isc.org/isc-packages/rpms/bind/-/blob/main/named.service.in (And I'm using ISC's repo) Perhaps Michał Kępień have any idea? 

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

Am 10.06.22 um 10:52 schrieb Søren Andersen: I've installed a fresh BIND on a RHEL 8.6 system with enforcing SElinux, and when I try to start BIND with the provided systemd unit file it just waits and timeout, and also logs these errors in /var/log/message Jun 10 10:09:25 systemd[1]:

re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

Hello, I've installed a fresh BIND on a RHEL 8.6 system with enforcing SElinux, and when I try to start BIND with the provided systemd unit file it just waits and timeout, and also logs these errors in /var/log/message Jun 10 10:09:25 systemd[1]: isc-bind-named.service: Can't convert PID files