|
Bugzilla – Full Text Bug Listing |
| Summary: | named does not start | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | First Name Last Name <sinderbox+novell> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | locilka, suse-beta |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | requested y2log | ||
Could you, please, attach YaST logs? This problem is known but should be solved by the DNS Server itself, on the other hand DNS Server itself writes forwarders correctly, so I assume that the HTTP server configuration somehow corrupts the data. http://en.opensuse.org/Bug_Reporting_FAQ#YaST Thanks Y2log attached. Following commets added: Inserted in named.conf when finishing "yast http-server": ==================BEGIN================== include "/etc/named.d/forwarders.conf"; ===================END==================== /etc/named.d/forwarders.conf is created when finishing "yast http-server" with the following broken format file: ==================BEGIN================== # Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany. # All rights reserved. # Forwarders file for PPPD updates (only) # # /etc/named.d/forwarders.conf forwarders ; ===================END==================== "forwarders ;" it is ilegal and therefore named fails to restart. In any case named.conf should not have been touched at all nor /etc/named.d/forwarders.conf created since I use no forwarders. Not using forwardersis what probably fooled the script into creating the incomplete "forwarders ;" line Created attachment 66622 [details]
requested y2log
the problem was that that http-server read/write named configuration also in case that dns server wasn't configured fixed Well, in my case named WAS CONFIGURED, but it used no forwarders, if that's what you mean. I will check the upcoming version when available and let you know if the problem persists. |
yast http-server module (at least under ncurses) adds the following line at /etc/named.conf include "/etc/named.d/forwarders.conf" even when named is using no forwarders at all. It also created a /etc/named.d/forwarders.conf with the following line: forwarders ; with no IP, which is an illegal named.conf configuration line. Therefore named fails to reload, and after stoping it will never start again. yast http-server will overwrite this two files with corrupted format after every run. As far as I can see the problem starts here: /usr/share/YaST2/modules/DnsServer.pm line 540 foreach my $key (sort (keys (%opt_map))) { if ($key ne "forwarders") { my @values = @{$opt_map{$key} || []}; SCR->Write (".dns.named.value.options.\"\Q$key\E\"", \@values); } else { $forwarders_found = 1; # writing forwarders into single file SCR->Write (".dns.named-forwarders", [$forwarders_include, @{$opt_map{$key}}[0]]); } }