[opensuse] Cannot start named on 12.1
After configuring Bind name service via YaST, I cannot start named. # rcnamed start redirecting to systemctl Job failed. See system logs and 'systemctl status' for details. # rcnamed status redirecting to systemctl named.service - LSB: Domain Name System (DNS) server, named Loaded: loaded (/etc/init.d/named) Active: failed since Sun, 27 Nov 2011 18:49:52 +0900; 17s ago Process: 9743 ExecStart=/etc/init.d/named start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/named.service I can see the logs below: Nov 27 18:49:52 hyperion named[9791]: starting BIND 9.8.1-P1 -t /var/lib/named -u named Nov 27 18:49:52 hyperion named[9791]: built with '--prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sys confdir=/etc' '--localstatedir=/var' '--libdir=/usr/lib64' '--includedir=/usr/include/bind' '--mandir=/usr/share/ man' '--infodir=/usr/share/info' '--with-openssl' '--enable-threads' '--with-libtool' '--enable-runidn' '--with-l ibxml2' '--with-dlz-mysql' '--with-dlz-ldap' 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-pro tector -funwind-tables -fasynchronous-unwind-tables -g -DNO_VERSION_DATE -fno-strict-aliasing' 'LDFLAGS=-L/usr/li b64' Nov 27 18:49:52 hyperion named[9791]: adjusted limit on open files from 4096 to 1048576 Nov 27 18:49:52 hyperion named[9791]: found 4 CPUs, using 4 worker threads Nov 27 18:49:52 hyperion named[9791]: using up to 4096 sockets Nov 27 18:49:52 hyperion named[9791]: initializing DST: openssl failure Nov 27 18:49:52 hyperion named[9791]: exiting (due to fatal error) Nov 27 18:49:52 hyperion named[9743]: Starting name server BIND ..failed Nov 27 18:49:52 hyperion systemd[1]: named.service: control process exited, code=exited status=1 Nov 27 18:49:52 hyperion systemd[1]: Unit named.service entered failed state. Any suggestions to solve this problem? Best, -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.zaq.ne.jp/opensuse/ _/_/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Satoru Matsumoto wrote:
After configuring Bind name service via YaST, I cannot start named.
[snip]
Nov 27 18:49:52 hyperion named[9791]: initializing DST: openssl failure
The above is the key issue I think.
Any suggestions to solve this problem?
Perhaps disable DNSSEC? Google has quite a few hits: http://www.google.com/search?q=named+initializing+DST+openssl+failure -- Per Jessen, Zürich (6.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/11/11 11:00, Satoru Matsumoto wrote:
After configuring Bind name service via YaST, I cannot start named.
# rcnamed start redirecting to systemctl Job failed. See system logs and 'systemctl status' for details.
Does it start OK if you boot using system V init? I have lots of services which don't start with systemd. named may be another to add to the list. Just a thought. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/27/2011 12:55 PM, lynn wrote:
On 27/11/11 11:00, Satoru Matsumoto wrote:
After configuring Bind name service via YaST, I cannot start named.
# rcnamed start redirecting to systemctl Job failed. See system logs and 'systemctl status' for details.
Does it start OK if you boot using system V init?
I have lots of services which don't start with systemd. named may be another to add to the list.
Please file a separate bug for each one that fails so that this gets fixed. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/11/11 10:15, Andreas Jaeger wrote:
On 11/27/2011 12:55 PM, lynn wrote:
On 27/11/11 11:00, Satoru Matsumoto wrote:
After configuring Bind name service via YaST, I cannot start named.
# rcnamed start redirecting to systemctl Job failed. See system logs and 'systemctl status' for details.
Does it start OK if you boot using system V init?
I have lots of services which don't start with systemd. named may be another to add to the list.
Please file a separate bug for each one that fails so that this gets fixed.
Andreas
Hi I reported the services that fail for me here: https://bugzilla.novell.com/show_bug.cgi?id=732395 Maybe if the op did one for named it would duplicate this. Thanks. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 27 Nov 2011 19:00:29 Satoru Matsumoto wrote:
Nov 27 18:49:52 hyperion named[9791]: adjusted limit on open files from 4096 to 1048576 Nov 27 18:49:52 hyperion named[9791]: found 4 CPUs, using 4 worker threads Nov 27 18:49:52 hyperion named[9791]: using up to 4096 sockets Nov 27 18:49:52 hyperion named[9791]: initializing DST: openssl failure Nov 27 18:49:52 hyperion named[9791]: exiting (due to fatal error) Nov 27 18:49:52 hyperion named[9743]: Starting name server BIND ..failed Nov 27 18:49:52 hyperion systemd[1]: named.service: control process exited, code=exited status=1 Nov 27 18:49:52 hyperion systemd[1]: Unit named.service entered failed state.
Any suggestions to solve this problem?
https://bugzilla.novell.com/show_bug.cgi?id=716745 Adjust AppArmor policy, disable AppArmor or check for updated bind and AppArmor packages. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andreas Jaeger -
Graham Anderson -
lynn -
Per Jessen -
Satoru Matsumoto