rwysocki_bones

It came online! i've set the files to 664 but folder to 777 and it works now.\ Thanks

I've run the chown and chmod on the docker container, output from named: 06-Jun-2022 07:47:50.274 general: info: loading configuration from '/etc/bind/named.conf' 06-Jun-2022 07:47:50.275 general: error: directory '/etc/bind' is not writable 06-Jun-2022 07:47:50.275 config: error: /etc/bind/named.conf:6: parsing failed: permission denied 06-Jun-2022 07:47:50.276 general: critical: loading configuration: permission denied 06-Jun-2022 07:47:50.276 general: critical: exiting (due to fatal error) and ls -la after: #ls -la /etc/bind total 8 drwxr-xr-x 1 99 users 42 Jun 3 02:43 . drwxr-xr-x 1 root root 746 Jun 6 01:02 .. -rw-rw-r-- 1 root root 170 Jun 3 02:43 local.hosts -rw-rw-r-- 1 root root 513 Jun 3 02:38 named.conf and from the UNRAID cli: # ls /mnt/user/appdata/bind9/ -la total 8 drwxr-xr-x 1 nobody users 42 Jun 3 02:43 ./ drwxrwxrwx 1 nobody users 230 Jun 6 05:02 ../ -rw-rw-r-- 1 root root 170 Jun 3 02:43 local.hosts -rw-rw-r-- 1 root root 513 Jun 3 02:38 named.conf should i chown the bind9 folder as root:root?

# ls -la /etc/bind drwxr-xr-x 1 99 users 42 Jun 3 02:43 . drwxr-xr-x 1 root root 746 Jun 6 01:02 .. -rw-r--r-- 1 99 users 170 Jun 3 02:43 local.hosts -rw-r--r-- 1 99 users 513 Jun 3 02:38 named.conf Yes I have, I've fully reinstalled the application and removed the bind9 folder from appdata then installed the container from CA and then go to GUI and set it up

Progress! running your command gave me this in the log file, so it must be permissions issue, I am unsure what's wrong tho, I've noticed some of my appdata folders are root:root and some are nobody:users. 06-Jun-2022 01:04:36.847 general: error: directory '/etc/bind' is not writable 06-Jun-2022 01:04:36.847 config: error: /etc/bind/named.conf:6: parsing failed: permission denied 06-Jun-2022 01:04:36.848 general: critical: loading configuration: permission denied # ls /mnt/user/appdata -l drwxr-xr-x 1 nobody users 42 Jun 3 02:43 bind9/ # ls /mnt/user/appdata/bind9/ -l -rw-r--r-- 1 nobody users 170 Jun 3 02:43 local.hosts -rw-r--r-- 1 nobody users 513 Jun 3 02:38 named.conf

I've completely re-installed the docker container, fresh install. It didn't help, restarting the server seemed to work, but it went down again (I think next time docker container was restarted) I have 2 Unraid servers so I even tried to copy the known working config from the other server, but still failing. tried installing it as host'ed network and as br0 with static IP, didn't work either way. only things I can think off is that the working server is running combination of older version unraid and this docker container. server1: UNRAID 6.9.2 with [pwa666/bind9@sha256:b76ee59003e8eb4cd5199f72c87f5c89903fabb9992d30d93126c0f6687fee9a] server2: URAID 6.10.1 with [pwa666/bind9@sha256:6e315ba61f7d29b2d1cdf0012109753c461666db1fceba687ff3fb209231d8b9] (one version behind) Also I am scared to update server2 to current 6.10.2 as there's an warning message "WARNING: combination of NIC using tg3 driver and Intel VT-d enabled may cause DATA CORRUPTION on some platforms." I am running PowerEdge R730 8xLFF currently running the internal Ethernet card, but will be adding an Mellanox MCX311A-XCAT EDIT---- I've also found that server1 has 2 files inside appdata that the server2 does not: managed-keys.bind managed-keys.bind.jnl

After update I get this, reinstalled cleared configs, still happening. 2022-05-31 04:09:23,794 INFO Set uid to user 0 succeeded 2022-05-31 04:09:23,798 INFO supervisord started with pid 1 2022-05-31 04:09:24,802 INFO spawned: 'bind' with pid 38 2022-05-31 04:09:25,282 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:09:26,287 INFO spawned: 'bind' with pid 152 2022-05-31 04:09:26,702 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:09:28,708 INFO spawned: 'bind' with pid 266 2022-05-31 04:09:29,156 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:09:32,163 INFO spawned: 'bind' with pid 380 2022-05-31 04:09:32,540 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:09:33,541 INFO gave up: bind entered FATAL state, too many start retries too quickly If i go into the docker console and run "supervisord -n -c /etc/supervisord.conf" i get a similar result: 2022-05-31 04:18:20,996 INFO Set uid to user 0 succeeded 2022-05-31 04:18:21,000 INFO supervisord started with pid 536 2022-05-31 04:18:22,004 INFO spawned: 'bind' with pid 537 2022-05-31 04:18:22,389 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:18:23,393 INFO spawned: 'bind' with pid 651 2022-05-31 04:18:23,827 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:18:25,833 INFO spawned: 'bind' with pid 765 2022-05-31 04:18:26,197 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:18:29,204 INFO spawned: 'bind' with pid 879 2022-05-31 04:18:29,671 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:18:30,672 INFO gave up: bind entered FATAL state, too many start retries too quickly and if i run it without the config file: /usr/lib/python3.9/site-packages/supervisor/options.py:474: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. self.warnings.warn( 2022-05-31 04:20:30,808 INFO Set uid to user 0 succeeded 2022-05-31 04:20:30,810 INFO supervisord started with pid 996 2022-05-31 04:20:31,815 INFO spawned: 'bind' with pid 997 2022-05-31 04:20:32,276 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:20:33,281 INFO spawned: 'bind' with pid 1111 2022-05-31 04:20:33,673 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:20:35,679 INFO spawned: 'bind' with pid 1225 2022-05-31 04:20:36,068 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:20:39,075 INFO spawned: 'bind' with pid 1339 2022-05-31 04:20:39,490 INFO exited: bind (exit status 1; not expected) 2022-05-31 04:20:40,491 INFO gave up: bind entered FATAL state, too many start retries too quickly Seems that its not my config, its the image fault. Edit---- I've attempted to run an older image pwa666/bind9:v1.3.40 but issue still persists, might be something glitched on the server and needs to be restarted, will do so tonight as I cant restart it now.