Skip site navigation (1) Skip section navigation (2)

Problem with SSL - Server went 100% Busy - Part II

From: "Daniel M" <daniel(dot)alemao(at)hotmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Problem with SSL - Server went 100% Busy - Part II
Date: 2006-01-25 17:07:16
Message-ID: BAY113-F13F5776B7EBB7BC4D42292E1120@phx.gbl (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Hi there,

I experienced the same problem as Alex eight months ago (reference below), 
but as there was no answer to his question. So I hope I have more luck:

I got the error "SSL SYSCALL error: A blocking operation was interrupted by 
a call to WSACancelBlockingCall." which appears to end in a loop, as, when I 
discovered it, there have been written already several Gigabytes of 
Log-Files with just that entry.

The error occured already two times, unfortunately I just got the log of the 
2nd time. It occured right after some autovacuum calls, but I guess they 
don't have anything to do with it, as autovacuum runs everyday.

The effect is simply a busy server with having all postgres.exe processes 
sharing the 100% of CPU time. The server is a v8.1.1 running on XP Pro.

Part I of this problem you find under
From: "Alex Shepherd" <maillists ( at ) ajsystems ( dot ) co ( dot ) nz>
To: <pgsql-admin ( at ) postgresql ( dot ) org>
Subject: Problem with SSL - Server went 100% Busy
Date: Wed, 11 May 2005 12:41:34 +1200

Thank in advance

Daniel Michulke

Você sabia que com o seu MSN Messenger você faz ligações de PC-papa- PC, 
grátis e para qualquer lugar do mundo? É só acessar

pgsql-admin by date

Next:From: Dario BrignardelloDate: 2006-01-25 18:03:47
Subject: Re: Where is my bottleneck?
Previous:From: ArnauDate: 2006-01-25 16:57:07
Subject: Re: Where is my bottleneck?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group