X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B0C4753C8A for ; Tue, 10 May 2005 21:41:57 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98598-08 for ; Wed, 11 May 2005 00:41:55 +0000 (GMT) Received: from voyager.interspeed.co.nz (ip210-55-105-81.valentine.co.nz [210.55.105.81]) by svr1.postgresql.org (Postfix) with ESMTP id C589353C99 for ; Tue, 10 May 2005 21:41:53 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by voyager.interspeed.co.nz (Postfix) with ESMTP id 320A12FA891 for ; Wed, 11 May 2005 12:41:23 +1200 (NZST) Received: from voyager.interspeed.co.nz ([127.0.0.1]) by localhost (voyager [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27994-02 for ; Wed, 11 May 2005 12:41:19 +1200 (NZST) Received: from ajsnotebook (port-222-152-52-106.fastadsl.net.nz [222.152.52.106]) by voyager.interspeed.co.nz (Postfix) with ESMTP id D85752FA895 for ; Wed, 11 May 2005 12:41:15 +1200 (NZST) From: "Alex Shepherd" To: Subject: Problem with SSL - Server went 100% Busy Date: Wed, 11 May 2005 12:41:34 +1200 Message-ID: <000601c555c2$32ce3b80$d217900a@ajsnotebook> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at interspeed.co.nz X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200505/110 X-Sequence-Number: 17539 Hi, This is my first PostgreSQL post so hopefully I've chosen the right list = for my problem. I've relatively new to PostgreSQL but have had quite a bit = of admin experience with Informix 7/9 over the years. I have PostgreSQL 8.0 installed on a Windows2003 server (SP1) and = configured to use SSL on the server and Client Certificates. The clients are = written in Delphi5 using the PostgresDAC component. All this seems to usually work fine. However, last night the server = started to run at 100% CPU as or just after I restarted an app and went home. = Later I checked the server from home and was unable to connect properly as it would just sit there without a timeout, but not connect properly either. I then connect to the server using Remote Desktop and found 2 = postmaster.exe processes consuming 100% of the CPU. I tried to shutdown the service but = not all the postmaster.exe processes went away. Finally I tried to restart = the system but it took about 1-2 hours before that completed. During this time about 1000 10M log files were created, and they all contained the following line, over and over: 2005-05-10 18:13:31 LOG: SSL SYSCALL error: A blocking operation was interrupted by a call to WSACancelBlockingCall. The line before the first occurrence was: 2005-05-10 17:57:27 ERROR: value too long for type character = varying(20) 2005-05-10 17:59:55 ERROR: value too long for type character = varying(20)=20 Which seems unrelated.=20 After the server rebooted, it all started to work as normal. I have downloaded the 8.0.2 release. Should I upgrade the server to = 8.0.2 first and see if the problem reoccurs or wait for wait in case one of = the developers wants to know more about the system as is? Given that this is an SSL related issue, should I upgrade the OpenSSL installation on this system or must I only use known PostgreSQL Server versions with particular OpenSSL versions? Cheers Alex Shepherd Phone: (Mobile) +64 (21) 777764 Phone: (Home) +64 (7) 854 0819 Email: alex@ajsystems.co.nz=20