Re: [389-users] slapd not responding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/23/2010 10:21 AM, Reinhard Nappert wrote:
Rich,
 
the slapd process was again in a state, where it did not respond. I did disable access logging. See the attached thread information.
 
Could you have a look at it and tell me, what you see.
I don't see anything - most of the interesting symbols are not being printed.
 
Thanks,
-Reinhard


From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Reinhard Nappert
Sent: Monday, November 22, 2010 5:11 PM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] slapd not responding

ok. I need to do a bit more testing, but disabling access logging may not solve the issue. I keep you updated


From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Rich Megginson
Sent: Monday, November 22, 2010 5:08 PM
To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [389-users] slapd not responding

On 11/22/2010 03:00 PM, Reinhard Nappert wrote:
Should I open a bug for it?
Sure, but unless you can reproduce it with the latest code (1.2.6 or 1.2.7), it's going to be very difficult for us to fix it.
 
-Reinhard


From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Rich Megginson
Sent: Monday, November 22, 2010 4:49 PM
To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [389-users] slapd not responding

On 11/22/2010 09:38 AM, Reinhard Nappert wrote:
Hi,
 
I have a 389 DS 1.1.2 server in Multi-Master mode. It happens that the server stops responding in some circumstances. When the server was in that state, I did a kill -11 on the pid in order to generate a coredump.
 
I got the following out of the core, by using gdb.
 
Any idea, what is going on on the server side. BTW, the server does not log anything during this time in either access nor errors.
Looks like the server is deadlocked in the access logging code.  I suppose you could try disabling access logging.
 
Thanks,
-Reinhard
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users

-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users

-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux