Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B41BF6501DA; Wed, 3 Sep 2008 12:39:29 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 26987-01-9; Wed, 3 Sep 2008 12:39:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 273C96501B4; Wed, 3 Sep 2008 12:38:49 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m83FcVdC021519; Wed, 3 Sep 2008 11:38:31 -0400 (EDT) To: Andriy Bakay cc: pgsql-admin@postgresql.org, pgsql-ru-general@postgresql.org Subject: Re: SSL problems In-reply-to: <48BE8671.8060200@irbisnet.com> References: <48BE8671.8060200@irbisnet.com> Comments: In-reply-to Andriy Bakay message dated "Wed, 03 Sep 2008 08:43:29 -0400" Date: Wed, 03 Sep 2008 11:38:31 -0400 Message-ID: <21518.1220456311@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/11 X-Sequence-Number: 30104 Andriy Bakay writes: > I have problems to setup SSL for PostgreSQL server. I did all the steps > which described in the documentation (17.8. Secure TCP/IP Connections > with SSL), but when I try to start the PostgreSQL server the pg_ctl gave > me: "could not start server". And nothing in the logs (I enabled all of > them). I googled around but did not find much. There is *no* exit path from the PG server that does not spit out an error message someplace. Re-examine the logging setup. I don't know how FreeBSD's package sets it up exactly, but there have been packages in the past that just sent the postmaster's stderr to /dev/null :-(. See here for some documentation about the settings that determine where messages go: http://www.postgresql.org/docs/8.3/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHERE regards, tom lane