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]: automatic empty zone: 9.E.F.IP6.ARPA Feb 04 23:11:06 fw12 named[6444]: automatic empty zone: A.E.F.IP6.ARPA Feb 04 23:11:06 fw12 named[6444]: automatic empty zone: B.E.F.IP6.ARPA Feb 04 23:11:06 fw12 named[6444]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Feb 04 23:11:06 fw12 named[6444]: automatic empty zone: EMPTY.AS112.ARPA Feb 04 23:11:06 fw12 named[6444]: automatic empty zone: HOME.ARPA Feb 04 23:11:06 fw12 named[6444]: none:98: 'max-cache-size 90%' - setting to 3097MB (out of 3441MB) Feb 04 23:11:06 fw12 named[6444]: configuring command channel from '/etc/rndc.key' Feb 04 23:11:06 fw12 named[6444]: command channel listening on 127.0.0.1#953 Feb 04 23:11:06 fw12 named[6444]: configuring command channel from '/etc/rndc.key' 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) Feb 04 23:11:06 fw12 systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE Feb 04 23:11:06 fw12 systemd[1]: named.service: Failed with result 'exit-code'. Feb 04 23:11:06 fw12 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). so, 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 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" The only "RO" i can see (dont ask me why) is: tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64) Any suggestions are very welcome... hans