Bug 2960
| Summary: | linuxconf segfaults on /etc/named.conf | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | eric_seppanen |
| Component: | linuxconf | Assignee: | Michael K. Johnson <johnsonm> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | jn, rapid_clicker |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 1999-08-28 20:17:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I ran in to this bug, too. It happens when etc/named.conf is using the old (BIND v4) syntax. It stopped when I changed etc/named.conf to use the new (BIND v8) syntax. Perhaps dnsconf should complain about old-style syntax, rather than seg faulting.... ? - hh I should note that "statistics-interval" and "cleaning-interval" are valid bind 8 syntax, and the example I give is a legal bind 8 named.conf. The directives that choke linuxconf aren't necessary but I like them because it reduces logfile clutter. Segfaulting on legal directives is dumb. I don't think this is Red Hat's problem, but I posted the bug in the hope the workaround would prove useful to others. I just ran into something that may be related. My named.conf doesnt' have any references to statistics-interval or cleaning-interval, but I got segfaults until I renamed named.conf to foo, then they went away. When I renamed foo back to named.conf, linuxconf continued to work. I'd been using the same named.conf for several days without problems (I installed BIND just recently, actually). *** Bug 4297 has been marked as a duplicate of this bug. *** After manualy configuring bind, and changing other /etc files, such as resolve.conf, when linuxconf is run it core dumps. When the line module.list 1 dnsconf was removed from /etc/conf.linuxconf, it stopped (until a the next reboot when the line was added. That shits me:( ) This bug is fixed, for me anyway, by the new Linuxconf RPM listed in the errata page: linuxconf-1.16r1.3-1.i386.rpm Thanks, guys. Thanks for the verification that it is fixed! |
Linuxconf was segfaulting every time I ran it- at first right away, then only when I tried to run the server-tasks:domain-name-server menu item. Removing /usr/lib/linuxconf/modules/dnsconf.so.1.14.4 fixed the problem temporarily. Removing "statistics-interval" and "cleaning-interval" lines from named.conf fixed it permanently. Example named.conf that shows this problem: options { directory "/var/named"; statistics-interval 0; cleaning-interval 1440; }; zone "." { type hint; file "named.ca"; }; zone "0.0.127.in-addr.arpa" { type master; file "named.local"; };