Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 692266 Details for
Bug 907133
[abrt] bind-dyndb-ldap-2.4-1.fc18.i686: zr_flush_all_caches: Process /usr/sbin/named was killed by signal 11 (SIGSEGV)
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
File: var_log_messages
var_log_messages (text/plain), 9.87 KB, created by
Niki Guldbrand
on 2013-02-03 11:15:10 UTC
(
hide
)
Description:
File: var_log_messages
Filename:
MIME Type:
Creator:
Niki Guldbrand
Created:
2013-02-03 11:15:10 UTC
Size:
9.87 KB
patch
obsolete
>Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 254.169.IN-ADDR.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 2.0.192.IN-ADDR.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 100.51.198.IN-ADDR.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 113.0.203.IN-ADDR.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: D.F.IP6.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 8.E.F.IP6.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 9.E.F.IP6.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: A.E.F.IP6.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: B.E.F.IP6.ARPA >Feb 3 09:32:35 ipa named[2221]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA >Feb 3 09:32:35 ipa named[2221]: command channel listening on 127.0.0.1#953 >Feb 3 09:32:35 ipa named[2221]: command channel listening on ::1#953 >Feb 3 09:32:35 ipa named[2221]: managed-keys.bind.jnl: create: permission denied >Feb 3 09:32:35 ipa named[2221]: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error >Feb 3 09:32:35 ipa named[2221]: zone 0.in-addr.arpa/IN: loaded serial 0 >Feb 3 09:32:35 ipa named[2221]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0 >Feb 3 09:32:35 ipa named[2221]: zone localhost/IN: loaded serial 0 >Feb 3 09:32:35 ipa named[2221]: zone localhost.localdomain/IN: loaded serial 0 >Feb 3 09:32:35 ipa named[2221]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0 >Feb 3 09:32:35 ipa named[2221]: all zones loaded >Feb 3 09:32:35 ipa named[2221]: running >Feb 3 09:33:45 ipa ipactl[2154]: Starting named Service >Feb 3 09:34:01 ipa named[2221]: error (network unreachable) resolving '0.fedora.pool.ntp.org/A/IN': 2001:500:1::803f:235#53 >Feb 3 09:34:01 ipa named[2221]: error (network unreachable) resolving '0.fedora.pool.ntp.org/AAAA/IN': 2001:500:1::803f:235#53 >Feb 3 09:36:57 ipa named[2221]: error (network unreachable) resolving 'bugzilla.redhat.com/AAAA/IN': 2001:503:ba3e::2:30#53 >Feb 3 09:43:56 ipa named[2221]: error (network unreachable) resolving 'clients2.google.com/A/IN': 2001:503:a83e::2:30#53 >Feb 3 09:43:56 ipa named[2221]: error (network unreachable) resolving 'clients2.google.com/AAAA/IN': 2001:503:a83e::2:30#53 >Feb 3 09:44:00 ipa named[2221]: error (network unreachable) resolving 'static-redirect.zlb.phx.mozilla.net/A/IN': 2001:503:231d::2:30#53 >Feb 3 09:44:00 ipa named[2221]: error (network unreachable) resolving 'static-redirect.zlb.phx.mozilla.net/AAAA/IN': 2001:503:231d::2:30#53 >Feb 3 09:44:01 ipa named[2221]: error (network unreachable) resolving 'www-gm-opensocial.googleusercontent.com/A/IN': 2001:503:231d::2:30#53 >Feb 3 09:44:01 ipa named[2221]: error (network unreachable) resolving 'www-gm-opensocial.googleusercontent.com/AAAA/IN': 2001:503:231d::2:30#53 >Feb 3 09:44:02 ipa named[2221]: error (network unreachable) resolving 'mozorg.dynect.mozilla.net.dlv.isc.org/DLV/IN': 2001:4f8:0:2::20#53 >Feb 3 09:44:02 ipa named[2221]: error (network unreachable) resolving 'mozorg.dynect.mozilla.net.dlv.isc.org/DLV/IN': 2001:500:2c::254#53 >Feb 3 09:44:02 ipa named[2221]: error (network unreachable) resolving 'mozorg.dynect.mozilla.net.dlv.isc.org/DLV/IN': 2001:500:60::29#53 >Feb 3 09:44:02 ipa named[2221]: error (network unreachable) resolving 'mozorg.dynect.mozilla.net.dlv.isc.org/DLV/IN': 2001:500:71::29#53 >Feb 3 10:00:51 ipa named[2221]: error (network unreachable) resolving 'planet.classpath.org/A/IN': 2001:500:e::1#53 >Feb 3 10:00:51 ipa named[2221]: error (network unreachable) resolving 'planet.classpath.org/AAAA/IN': 2001:500:e::1#53 >Feb 3 10:02:30 ipa named[2221]: error (network unreachable) resolving 'twitter-blog.s3.amazonaws.com/A/IN': 2001:503:a83e::2:30#53 >Feb 3 10:02:30 ipa named[2221]: error (network unreachable) resolving 'twitter-blog.s3.amazonaws.com/AAAA/IN': 2001:503:a83e::2:30#53 >Feb 3 10:02:30 ipa named[2221]: error (network unreachable) resolving 'www.blogger.com/A/IN': 2001:503:a83e::2:30#53 >Feb 3 10:02:30 ipa named[2221]: error (network unreachable) resolving 'www.blogger.com/AAAA/IN': 2001:503:a83e::2:30#53 >Feb 3 10:02:30 ipa named[2221]: error (network unreachable) resolving 'img1.blogblog.com/A/IN': 2001:503:a83e::2:30#53 >Feb 3 10:02:30 ipa named[2221]: error (network unreachable) resolving 'img1.blogblog.com/AAAA/IN': 2001:503:a83e::2:30#53 >Feb 3 10:02:34 ipa named[2221]: error (network unreachable) resolving 'pagead2.googlesyndication.com/A/IN': 2001:503:231d::2:30#53 >Feb 3 10:02:34 ipa named[2221]: error (network unreachable) resolving 'pagead2.googlesyndication.com/AAAA/IN': 2001:503:231d::2:30#53 >Feb 3 10:02:34 ipa named[2221]: error (network unreachable) resolving 'googleads.g.doubleclick.net/A/IN': 2001:503:231d::2:30#53 >Feb 3 10:02:39 ipa named[2221]: error (network unreachable) resolving 'en.wikipedia.org/A/IN': 2001:500:40::1#53 >Feb 3 10:02:39 ipa named[2221]: error (network unreachable) resolving 'en.wikipedia.org/AAAA/IN': 2001:500:40::1#53 >Feb 3 10:02:44 ipa named[2221]: RSA_verify failed >Feb 3 10:02:44 ipa named[2221]: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature:rsa_sign.c:293: >Feb 3 10:02:44 ipa named[2221]: sucessfully validated after lower casing signer 'CO' >Feb 3 10:02:44 ipa named[2221]: RSA_verify failed >Feb 3 10:02:44 ipa named[2221]: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature:rsa_sign.c:293: >Feb 3 10:02:44 ipa named[2221]: sucessfully validated after lower casing signer 'CO' >Feb 3 10:02:44 ipa named[2221]: RSA_verify failed >Feb 3 10:02:44 ipa named[2221]: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature:rsa_sign.c:293: >Feb 3 10:02:44 ipa named[2221]: sucessfully validated after lower casing signer 'CO' >Feb 3 10:02:44 ipa named[2221]: RSA_verify failed >Feb 3 10:02:44 ipa named[2221]: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature:rsa_sign.c:293: >Feb 3 10:02:44 ipa named[2221]: sucessfully validated after lower casing signer 'CO' >Feb 3 10:02:44 ipa named[2221]: RSA_verify failed >Feb 3 10:02:44 ipa named[2221]: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature:rsa_sign.c:293: >Feb 3 10:02:44 ipa named[2221]: sucessfully validated after lower casing signer 'CO' >Feb 3 10:19:52 ipa named[2221]: error (network unreachable) resolving 'fedora.uni-oldenburg.de/A/IN': 2001:503:ba3e::2:30#53 >Feb 3 10:19:52 ipa named[2221]: error (network unreachable) resolving 'ftp.uni-erlangen.de/A/IN': 2001:503:ba3e::2:30#53 >Feb 3 10:19:52 ipa named[2221]: error (network unreachable) resolving 'ftp.wsisiz.edu.pl/A/IN': 2001:503:ba3e::2:30#53 >Feb 3 10:19:52 ipa named[2221]: error (network unreachable) resolving 'ftp.uni-siegen.de/A/IN': 2001:503:ba3e::2:30#53 >Feb 3 10:19:54 ipa named[2221]: error (network unreachable) resolving 'uni-erlangen.de/DS/IN': 2a02:568:0:2::53#53 >Feb 3 10:19:54 ipa named[2221]: error (network unreachable) resolving 'ftp.uni-siegen.de/A/IN': 2a02:568:0:2::53#53 >Feb 3 10:38:14 ipa named[2221]: error (network unreachable) resolving '86.116.55.65.in-addr.arpa/PTR/IN': 2001:470:1a::2#53 >Feb 3 10:51:09 ipa named[2221]: error (network unreachable) resolving 'b.barracudacentral.org.dlv.isc.org/DLV/IN': 2001:500:2c::254#53 >Feb 3 10:51:09 ipa named[2221]: error (network unreachable) resolving 'zen.spamhaus.org.dlv.isc.org/DLV/IN': 2001:500:2c::254#53 >Feb 3 11:47:17 ipa named[2221]: error (network unreachable) resolving 'ftp.crc.dk/A/IN': 2001:500:2f::f#53 >Feb 3 11:47:17 ipa named[2221]: error (network unreachable) resolving 'ftp.crc.dk/AAAA/IN': 2001:500:2f::f#53 >Feb 3 11:47:17 ipa named[2221]: error (network unreachable) resolving 'mirror.yandex.ru/A/IN': 2001:500:2f::f#53 >Feb 3 11:47:17 ipa named[2221]: error (network unreachable) resolving 'mirror.yandex.ru/AAAA/IN': 2001:500:2f::f#53 >Feb 3 11:47:19 ipa named[2221]: error (network unreachable) resolving 'mirror.yandex.ru/A/IN': 2001:678:17:0:193:232:128:6#53 >Feb 3 11:47:19 ipa named[2221]: error (network unreachable) resolving 'mirror.yandex.ru/A/IN': 2001:678:18:0:194:190:124:17#53 >Feb 3 11:47:19 ipa named[2221]: error (network unreachable) resolving 'mirror.yandex.ru/A/IN': 2001:678:14:0:193:232:156:17#53 >Feb 3 11:47:19 ipa named[2221]: error (network unreachable) resolving 'yandex.ru/DS/IN': 2001:678:17:0:193:232:128:6#53 >Feb 3 11:47:19 ipa named[2221]: error (network unreachable) resolving 'yandex.ru/DS/IN': 2001:678:18:0:194:190:124:17#53 >Feb 3 11:47:19 ipa named[2221]: error (network unreachable) resolving 'yandex.ru/DS/IN': 2001:678:14:0:193:232:156:17#53 >Feb 3 11:48:49 ipa named[2221]: LDAP error: Can't contact LDAP server >Feb 3 11:48:49 ipa named[2221]: connection to the LDAP server was lost >Feb 3 11:48:49 ipa named[2221]: bind to LDAP server failed: Can't contact LDAP server >Feb 3 11:48:49 ipa named[2221]: ldap_psearch_watcher failed to handle LDAP connection error. Reconnection in 60s >Feb 3 11:49:39 ipa named[2221]: LDAP error: Can't contact LDAP server >Feb 3 11:49:39 ipa named[2221]: connection to the LDAP server was lost >Feb 3 11:49:39 ipa named[2221]: successfully reconnected to LDAP server >Feb 3 11:49:49 ipa named[2221]: connection to the LDAP server was lost >Feb 3 11:49:50 ipa named[2221]: successfully reconnected to LDAP server >Feb 3 11:49:50 ipa kernel: [ 9040.106530] named[2225]: segfault at 1c ip b4f22667 sp b47fec80 error 4 in ldap.so[b4f06000+24000] >Feb 3 11:49:50 ipa abrt[3211]: /var/named/core.2221 fd(-1) is not a regular file with link count 1: Permission denied >Feb 3 11:49:52 ipa abrt[3211]: Saved core dump of pid 2221 (/usr/sbin/named) to /var/spool/abrt/ccpp-2013-02-03-11:49:50-2221 (99164160 bytes) >Feb 3 11:49:52 ipa systemd[1]: named.service: main process exited, code=dumped, status=11/SEGV >Feb 3 11:49:52 ipa systemd[1]: named.service: control process exited, code=exited status=1 >Feb 3 11:49:52 ipa systemd[1]: Unit named.service entered failed state
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 907133
:
692256
|
692257
|
692258
|
692259
|
692260
|
692261
|
692262
|
692263
|
692264
|
692265
| 692266