Richard Hesse wrote:
Yeah, we¹re using SSL and TLS so ethereal/tcpdump isn¹t going to yield much
info. The process hung again and strace didn¹t provide too much information
other than this:
futex(0x20b9260, FUTEX_WAIT, 2, NULL)
Would that give you a place to start looking?
Try logconv.pl -V
Richard Hesse wrote:
Yeah, we¹re using SSL and TLS so ethereal/tcpdump isn¹t going to yield much
info.
It would give us the TCP/IP protocol data, so we could see what clients
and servers are sending the FIN and RST. It's not so much the LDAP data
I care about, although ssltap might be useful f
Yeah, we¹re using SSL and TLS so ethereal/tcpdump isn¹t going to yield much
info. The process hung again and strace didn¹t provide too much information
other than this:
futex(0x20b9260, FUTEX_WAIT, 2, NULL)
Would that give you a place to start looking?
-richard
On 2/19/08 4:04 PM, "Rich Meggin
Richard Hesse wrote:
Not much new to report. The server hung again and the only thing in the
error log with connection tracing is this:
[18/Feb/2008:13:14:03 +] - PR_Write(41818752) Netscape Portable Runtime
error -5961 (TCP connection reset by peer.)
[18/Feb/2008:13:14:03 +] - ber_flush
Not much new to report. The server hung again and the only thing in the
error log with connection tracing is this:
[18/Feb/2008:13:14:03 +] - PR_Write(41818752) Netscape Portable Runtime
error -5961 (TCP connection reset by peer.)
[18/Feb/2008:13:14:03 +] - ber_flush failed, error 104 (Con
Richard Hesse wrote:
Yes, every host (except the ldap hosts) runs nscd. The ldap servers are not
configured to use directory data for anything.
I just don't know. I've not seen this before. I suppose you could try
checking your kernel TCP/IP settings, and increasing the number of file
desc
Yes, every host (except the ldap hosts) runs nscd. The ldap servers are not
configured to use directory data for anything.
-richard
On 2/15/08 2:11 PM, "Rich Megginson" <[EMAIL PROTECTED]> wrote:
> Richard Hesse wrote:
>> nsswitch posix users/groups,
> Are you using nscd?
>> ssh, sudo, puppet (
Richard Hesse wrote:
nsswitch posix users/groups,
Are you using nscd?
ssh, sudo, puppet (config management), and
internally written applications.
-richard
On 2/15/08 12:53 PM, "Rich Megginson" <[EMAIL PROTECTED]> wrote:
What is the application which is generating this load?
--
Fe
nsswitch posix users/groups, ssh, sudo, puppet (config management), and
internally written applications.
-richard
On 2/15/08 12:53 PM, "Rich Megginson" <[EMAIL PROTECTED]> wrote:
> What is the application which is generating this load?
--
Fedora-directory-users mailing list
Fedora-directory-us
Richard Hesse wrote:
Thanks Richard, I¹ll give connection management a whirl.
What is the application which is generating this load?
Here¹s the log parser output (nice util btw):
--- Access Log Output
Restarts: 0
Total Connections:4820
Thanks Richard, I¹ll give connection management a whirl.
Here¹s the log parser output (nice util btw):
--- Access Log Output
Restarts: 0
Total Connections:4820
Peak Concurrent Connections: 19
Total Operations: 18017
Total Results
Richard Hesse wrote:
Eh sorry about this but it appears that my original hunch was correct.
The 1.1 DS instance did indeed hang again recently. I was able to
check a localhost query and that failed, too. So the problem
definitely appears to be a hang in the FDS code somewhere. The
question is,
em with the
connection to the client.
> Thanks.
>
> -richard
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard
> Megginson
> Sent: Monday, February 11, 2008 7:43 PM
> To: General discussion list for the Fedora Directory s
, February 11, 2008 7:43 PM
> To: General discussion list for the Fedora Directory server project.
> Subject: Re: [Fedora-directory-users] FDS 1.1 Transport endpoint is not
> connected
>
> Richard Hesse wrote:
>
>> Started to play with FDS 1.1 for some dogfood testing. After
l discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] FDS 1.1 Transport endpoint is not
connected
Richard Hesse wrote:
Started to play with FDS 1.1 for some dogfood testing. After running for 10-15
minutes, the server stopped responding to network
discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] FDS 1.1 Transport endpoint is not
connected
Richard Hesse wrote:
> Started to play with FDS 1.1 for some dogfood testing. After running for
> 10-15 minutes, the server stopped responding to netw
Richard Hesse wrote:
Started to play with FDS 1.1 for some dogfood testing. After running for 10-15
minutes, the server stopped responding to network requests and went silent. The
process was running, the error log was updating with the ldbm event loop, but
no socket requests were fulfilled. C
Started to play with FDS 1.1 for some dogfood testing. After running for 10-15
minutes, the server stopped responding to network requests and went silent. The
process was running, the error log was updating with the ldbm event loop, but
no socket requests were fulfilled. Checking the access log,
18 matches
Mail list logo
