Hi all,
After applying the patches and restarting the service, everything was fine for
about couple of hours. But again it crashed and gave core dump. I have updated
the latest /var/log/messages and core dump with the bugzilla report.
Please help.
Regards,
Nidal
--- On Tue, 7/26/11, Adam Tka
Hi,
the new named just died again:
[root@zerberus ~]# nslookup www.google.de
;; connection timed out; no servers could be reached
[root@zerberus ~]# rpm --query --all | grep bind
bind-debuginfo-9.8.0-7.P4.fc15.x86_64
bind-libs-9.8.0-7.P4.fc15.x86_64
bind-libs-lite-9.8.0-7.P4.fc15.x86_64
bind-dy
On 07/26/2011 04:51 PM, nasir nasir wrote:
> Hi All,
>
> Thanks a ton for every one who helped to have such a quick fix for this
> issue. I truly appreciate it. I have applied the patch (generated from the
> source rpm and applied with rpm -Uvh ***) and restarted IPA service. Had a
> preliminary
Hi All,
Thanks a ton for every one who helped to have such a quick fix for this issue.
I truly appreciate it. I have applied the patch (generated from the source rpm
and applied with rpm -Uvh ***) and restarted IPA service. Had a preliminary
test of the services and everything seems to be fine.
On 07/26/2011 03:56 PM, nasir nasir wrote:
> Hi,
>
>>> In my case things are getting worse after the
>> configuration change. Earlier the issue used to pops up once
>> in a day or so. But now it is recurring in every hour
>> or so. So I have reverted that parameter.
>> May I ask you if you send r
Robert M. Albrecht wrote:
Hi,
I tried to join my first client (another fully patched F15, like the
ipa-server).
Joining realm failed because of failing XML-RPC request.
This error may be caused by incompatible server/client major versions.
I think this is the problem caused by a recent libcur
Hi,
> >
> > In my case things are getting worse after the
> configuration change. Earlier the issue used to pops up once
> in a day or so. But now it is recurring in every hour
> or so. So I have reverted that parameter.
> >
> May I ask you if you send reload (rndc reload or kill -HUP)
> or stop
On 07/26/2011 03:22 PM, nasir nasir wrote:
> Hi,
>
>
>> Hi,
>>
>> I already included it, it's running for 15 minutes now. It
>> never
>> survived longer than a minute before.
>>
>> Keep fingers crossed :-)
>
> In my case things are getting worse after the configuration change. Earlier
> the issue
Hi,
it just died.
Limiting the connections seems to help, but does not solve the problem.
cu romal
Am 26.07.11 15:22, schrieb nasir nasir:
Hi,
Hi,
I already included it, it's running for 15 minutes now. It
never
survived longer than a minute before.
Keep fingers crossed :-)
In my ca
Hi,
I tried to join my first client (another fully patched F15, like the
ipa-server).
Joining realm failed because of failing XML-RPC request.
This error may be caused by incompatible server/client major versions.
[root@chessur ~]# ipa-client-install --debug --enable-dns-updates
root
Hi,
>
> Hi,
>
> I already included it, it's running for 15 minutes now. It
> never
> survived longer than a minute before.
>
> Keep fingers crossed :-)
In my case things are getting worse after the configuration change. Earlier the
issue used to pops up once in a day or so. But now it is r
Am 26.07.11 14:52, schrieb Rob Crittenden:
Robert M. Albrecht wrote:
Hi,
I think I have a similar problem on a fully patched F15.
After booting name resolution is working for about a minute, after that
it suddenly stops.
The logged error sure looks similar. Can you try the configuration
opti
Hi,
abrt-upload at: https://bugzilla.redhat.com/show_bug.cgi?id=725741
cu romal
Am 26.07.11 14:02, schrieb Robert M. Albrecht:
Hi,
I think I have a similar problem on a fully patched F15.
After booting name resolution is working for about a minute, after that
it suddenly stops.
/var/log/me
Robert M. Albrecht wrote:
Hi,
I think I have a similar problem on a fully patched F15.
After booting name resolution is working for about a minute, after that
it suddenly stops.
The logged error sure looks similar. Can you try the configuration
option as well to see if it helps?
thanks
ro
Hi,
sorry, that was my own mistake:
from the docs at
http://directory.fedoraproject.org/wiki/Install_Guide#Removing_Packages
Extra cleanup
After removing all of the packages, you can do something like this to
make sure your system is back to a clean state:
rm -rf /etc/dirsrv /usr/lib*/dirs
Hi,
I think I have a similar problem on a fully patched F15.
After booting name resolution is working for about a minute, after that
it suddenly stops.
/var/log/messages
Jul 26 13:51:50 zerberus named[2948]: starting BIND
9.8.0-P4-RedHat-9.8.0-7.P4.fc15 -u named
Jul 26 13:51:50 zerberus nam
Hi Adam/Rob,
Many many thanks indeed for the lightning fast action on this and the
workaround! As per your suggestion, I have modified the named.conf file and
attached the log file to the bugzilla entry.
Please let me know if there is anything else that I can do to help you to help
me.
Thanks
Hello,
I saw this problem from 02/2011 (Fedora 14/freeipa 2.0.0RC1). Many
times, as a MacOS computer started on network, he made deja vu request,
(4 dns request in the same time), and freezed bind. I made a script to
request bind every 3 seconds, and restart when nedded.
Regards,
Sylvain PA
Note this issue is also tracked in RH bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=725577
Regards, Adam
On 07/26/2011 10:06 AM, Adam Tkac wrote:
> Hello Nasir,
>
> I checked the backtrace and this is a bug in the bind-dyndb-ldap plugin.
>
> I wasn't able to reproduce your crash but I th
Hello Nasir,
I checked the backtrace and this is a bug in the bind-dyndb-ldap plugin.
I wasn't able to reproduce your crash but I think the workaround is to
limit "connections" argument to 1 (note this is number of connections
from bind-dyndb-ldap to LDAP server, not number of clients that named
20 matches
Mail list logo
