我完全被绑定吓到了! 将大量欣赏任何提示。
当我尝试开始绑定时,我看到:
root@WIG001-001 ~]# /etc/init.d/named start ls: cannot access /var/named/run-root/etc/pki/dnssec-keys: No such file or directory mount: mount point /var/named/run-root/etc/pki/dnssec-keys does not exist ls: cannot access /var/named/run-root/var/named: No such file or directory mount: mount point /var/named/run-root/var/named does not exist ls: cannot access /var/named/run-root/usr/lib64/bind: No such file or directory mount: mount point /var/named/run-root/usr/lib64/bind does not exist Starting named: [FAILED]
…所以它看起来像named从/ var / named / run-root运行。 如果我检查日志,看起来conf文件位于/etc/named.conf(我正在复制其他相关的消息,以防其他人知道发生了什么):
[root@WIG001-001 ~]# tail -n30 /var/log/messages Jul 27 21:16:44 WIG001-001 named[9200]: loading configuration from '/etc/named.conf' Jul 27 21:16:44 WIG001-001 named[9200]: using default UDP/IPv4 port range: [1024, 65535] Jul 27 21:16:44 WIG001-001 named[9200]: using default UDP/IPv6 port range: [1024, 65535] Jul 27 21:16:44 WIG001-001 named[9200]: listening on IPv4 interface lo, 127.0.0.1#53 ...blah.... Jul 27 21:16:44 WIG001-001 named[9200]: command channel listening on 127.0.0.1#953 Jul 27 21:16:44 WIG001-001 named[9200]: could not open entropy source /dev/random: permission denied Jul 27 21:16:44 WIG001-001 named[9200]: using pre-chroot entropy source /dev/random Jul 27 21:16:44 WIG001-001 named[9200]: the working directory is not writable Jul 27 21:16:44 WIG001-001 named[9200]: couldn't open pid file '/var/run/named/named.pid': Permission denied Jul 27 21:16:44 WIG001-001 named[9200]: exiting (due to early fatal error)
..所以假设我的configuration文件是从上面的日志/etc/named.conf中,
[root@WIG001-001 ~]# cat /etc/named.conf ...blah... options { allow-recursion { localnets; }; directory "/var"; auth-nxdomain no; pid-file "/var/run/named/named.pid"; .....
从这个文件看来,named应该在/ var – not / var / named / run-root下运行,就像我试图启动named时从命令行中看到的那样。
任何人都可以给我任何想法从哪里去? 任何和所有的帮助将大力赞赏!
你使用的初始化脚本是否假设了一个用于绑定的chroot? 找一个
-t /var/named/run-root
在那里。 我不清楚chroot设置是否是您的意图,但环境和init脚本必须以某种方式匹配。
非常感谢这个指针,我现在被告知它是通过禁用SELinux来解决的,只是把答案放在这里,以防别人遇到同样的问题!
干杯,
麦克风