| Summary: | 3_a2: missing local and named files in master/reverse directories | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | davidwhodgins, jdines, thomas |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | bind-9.9.2-2.mga3.src.rpm, bind-9.9.3.P2-1.mga3 | CVE: | |
| Status comment: | |||
|
Manuel Hiebel
2012-11-11 00:16:50 CET
Assignee:
bugsquad =>
guillomovitch There is no reference to those files in the current configuration file. You're probably having an upgrade issue here. Summary:
3_a2: missing local and named files in master/reverse directories. =>
missing local and named files in master/reverse directories (In reply to comment #1) > There is no reference to those files in the current configuration file. Guessing that is why they disappeared. :( > You're probably having an upgrade issue here. Upgrade from where. I did a clean install and named worked. bind-9.9.1.P4 fails on openssl, and did not fail in named-checkconf like bind-9.9.2-1.mga3.src.rpm does. My bad, I forgot to push some fixes I made during my tests into the package, notably the /usr/lib{64}/openssl directory into the chroot. The incoming 9.9.2-2.mga3 release should fix it.
(In reply to comment #3) > My bad, I forgot to push some fixes I made during my tests into the package, > notably the /usr/lib{64}/openssl directory into the chroot. The incoming > 9.9.2-2.mga3 release should fix it. Not so you would notice. Good news, less errors from named-checkconf. Bad news still fails with I did a urpme bind ; urpmi bind and systemctl start named.service : _default/1.0.0.127.in-addr.arpa/IN: file not found : zone 0.in-addr.arpa/IN: loading from master file named.empty failed: file not found : zone 0.in-addr.arpa/IN: not loaded due to errors. : _default/0.in-addr.arpa/IN: file not found # get_src_rpm named Install rpm: bind-9.9.2-2.mga3 Source rpm: bind-9.9.2-2.mga3.src.rpm Summary:
missing local and named files in master/reverse directories =>
3_a2: missing local and named files in master/reverse directories ok, appears several directories and whatnot were not cleaned up on a urpme/urpmi activity. Deleted several files/directories, rebooted, urpmi bind and was able to bring up named.service. Executed my named_changes script and it failed trying to create my home and tuners zones. Guessing a clean alpha3 install will let me make those changes. Resolution:
(none) =>
FIXED The problem is still there on a brand new install of mga3 and using the drakwizard to set it up. CC:
(none) =>
thomas I am using a fresh install of Mageia 3 with bind-9.9.3.P2-1.mga3 installed and have a similar issue: [root@server var]# ls named zone/ The drakwizard fails and asks to please relaunch drakwizard and try to change some parameters. ... is it possible to attach the needed files to get bind working so we have a workaround until you can get the rpm straightened out? CC:
(none) =>
jdines (In reply to Jim Dines from comment #7) > I am using a fresh install of Mageia 3 with bind-9.9.3.P2-1.mga3 installed > and have a similar issue: > > [root@server var]# ls named > zone/ > > The drakwizard fails and asks to please relaunch drakwizard and try to > change some parameters. > > ... is it possible to attach the needed files to get bind working so we have > a workaround until you can get the rpm straightened out? As far as I know, there is no problem with the files in the rpm package. The configuration procedures have changed, and upgrading does not fix custom configurations. Simplest way I know of to fix the config problems... systemctl disable named.service reboot #to ensure the bind mounts are closed The file named.conf should be in /etc mv all custom config files to /var/named Make sure all include or file references in named.conf, or the included files use relative names, not absolute names. systemctl enable named.service systemctl start named.service The named service runs in a chroot, with the various config files and directories mounted as bind mounts, so they are read-only for named. CC:
(none) =>
davidwhodgins Also note, /etc/named.conf will need changes if you want it to be accessible from other then localhost, change listen-on and allow-query, to any. This is a fresh install of Mageia 3 with no custom changes made. I merely used drakwizard and it failed. It is possible that I installed named then updates were made before I ran drakwizard. I want a fresh install of the latest rpm. Should things get sorted out if I remove bind and bind-utils then re-install them? I need a working install so I can make changes, as I am not familiar with bind and would prefer not to become an expert just to get DNS working for this (very small) LAN. I haven't tried using drakwizard recently, for configuring bind. Probably best to avoid using it for now. (I'd forgotten it had that feature.) I'd uninstall bind, reboot (to ensure the bind mounts are closed), then re-install bind. Should be working out of the box (test that, before trying to customize). I'll look into drakwizard configuration of bind, and file bug reports for it, if appropriate. Bug 10981 filed for drakwizard. No more problem in bind package anymore, I'm closing this bug. Resolution:
(none) =>
FIXED |
Description of problem: Missing /var/lib/named/var/named/reverse/ named.broadcast named.ip6.local named.local named.zero Missing /var/lib/named/var/named/master/ localdomain.zone localhost.zone Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. systemctl start named.service 2. systemctl status named.service snippet follows: named-checkconf: zone 1.0... ip6.arpa/IN: not loaded... errors. named-checkconf: _default/1.0....ip6.arpa/IN: file not found named-checkconf: zone 1.0.0.127.in-addr.arpa/IN: loading from master file named.loopback failed: file not found named-checkconf: zone 1.0.0.127.in-addr.arpa/IN: not loaded due to errors. named-checkconf: _default/1.0.0.127.in-addr.arpa/IN: file not found named-checkconf: zone 0.in-addr.arpa/IN: loading from master file named.empty failed: file not found named-checkconf: zone 0.in-addr.arpa/IN: not loaded due to errors. named-checkconf: _default/0.in-addr.arpa/IN: file not found systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).