Bind failed to start after recent update
Hi all,
on the first of february, i did my weekly update on my tumbleweed box.
All seemed to go well, atleast no alarming messages.
However, since then, bind fails to startup.
Normally this is caused by a typo in the config file, or a silly mistake
in one of the zone-files.
This however, am in not able to pin-point.
journalctl tells me:
Hi On 2/5/21 9:09 AM, suse@a-domani.nl wrote:
Hi all,
on the first of february, i did my weekly update on my tumbleweed box. All seemed to go well, atleast no alarming messages.
However, since then, bind fails to startup. Normally this is caused by a typo in the config file, or a silly mistake in one of the zone-files. This however, am in not able to pin-point.
In future please use the support mailing list for such posts or file a bugreport if you believe its a bug. Thanks -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 04/02/2021 23.39, suse@a-domani.nl wrote:
Hi all,
on the first of february, i did my weekly update on my tumbleweed box. All seemed to go well, atleast no alarming messages.
However, since then, bind fails to startup. Normally this is caused by a typo in the config file, or a silly mistake in one of the zone-files. This however, am in not able to pin-point.
journalctl tells me:
...
Feb 04 23:11:06 fw12 named[6444]: command channel listening on ::1#953 Feb 04 23:11:06 fw12 named[6444]: stdio.c:27: unexpected error: Feb 04 23:11:06 fw12 named[6444]: unable to convert errno to isc_result: 30: Read-only file system Feb 04 23:11:06 fw12 named[6444]: isc_stdio_open '/var/log/bind.log' failed: unexpected error Feb 04 23:11:06 fw12 named[6444]: configuring logging: unexpected error Feb 04 23:11:06 fw12 named[6444]: loading configuration: unexpected error Feb 04 23:11:06 fw12 named[6444]: exiting (due to fatal error)
...
I know that the logfile is written to:
/var/lib/named/log # ll total 198736 -rw-rw-rw- 1 named named 1 Feb 4 23:32 bind.log -rw-r--r-- 1 named named 104857661 Feb 1 18:27 bind.log.0 And that file is appendable, so THAT file is not on a "Read-only file system"
It may mean "/var/lib/named/var/log/", there is a chroot. Also, check apparmour. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
"bind-chrootenv" is no more. "named" and "lwresd" are now secured by systemd's own mechanisms. Can you try to add "/var/log" to the list of "ReadWritePaths" in /usr/lib/systemd/system/named.service Thanks, Josef
participants (4)
-
Carlos E.R.
-
Josef Möllers
-
Simon Lees
-
suse@a-domani.nl