Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with configuration after upgrade #333

Closed
karlism opened this issue Aug 1, 2016 · 4 comments
Closed

Problems with configuration after upgrade #333

karlism opened this issue Aug 1, 2016 · 4 comments

Comments

@karlism
Copy link

@karlism karlism commented Aug 1, 2016

Hello,

After seemingly successful upgrade of facileManager to 2.3 and fmDNS module to 2.2.4, I now experience two issues with server configuration building:
facilemanager
facilemanager2

As you can see, there are two errors, about 13th line of /etc/named.conf.key, even though this line is actually empty, and about nonexistent /var/named directory. BIND is running chrooted in my case and both /var/named and /var/named/chroot/var/named directories exist.

Any ideas what could be wrong?
Thanks!

@WillyXJ
Copy link
Owner

@WillyXJ WillyXJ commented Aug 1, 2016

Hi,

That is indeed odd behavior. The syntax checks are performed by the BIND named-checkconf utility. Did you upgrade BIND recently, too? What version of BIND are you using?

@karlism
Copy link
Author

@karlism karlism commented Aug 1, 2016

Thank you for prompt reply!

I'm using bind-chroot package 9.9.4-29.el7_2.3 on CentOS 7.2. Judging by yum logs, BIND package hasn't been upgraded since May 27th, so I suspect that's not an issue.

@WillyXJ
Copy link
Owner

@WillyXJ WillyXJ commented Aug 1, 2016

I've found the issue with $fm_module_buildconf->namedSyntaxChecks() which only impacts the syntax check routine. If you disable the checks, config builds and zone reloads are successful. A fix will be coming in the next bug fix release.

@karlism
Copy link
Author

@karlism karlism commented Aug 2, 2016

Thanks!

@karlism karlism closed this Aug 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants