Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aPZaq-0006xY-Sp for pgsql-general@arkaria.postgresql.org; Sat, 30 Jan 2016 17:45:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aPZaq-00081I-Fk for pgsql-general@arkaria.postgresql.org; Sat, 30 Jan 2016 17:45:52 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aPZao-00080d-TR for pgsql-general@postgresql.org; Sat, 30 Jan 2016 17:45:51 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aPZam-0003TI-0h for pgsql-general@postgresql.org; Sat, 30 Jan 2016 17:45:49 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4D6D82A9B3 for ; Sat, 30 Jan 2016 12:45:46 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Sat, 30 Jan 2016 12:45:46 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=war98YDfy5zvI+xYdgDbl7cxRPE=; b=jrmSHn njB70Wb2Ub7iBIHmhz1wiLwDsiK3SbJKPVcgjgyq0uQ6N8ZwgyJg3ytmIQhkNRkz y9D5VDR2UoH5AvOg1HhCiRY5W667vtvHclIfMTPPPtmWNRfuoDemRxND2s7UGtZz HqngfKF2Bhxou8ftqiI8Rr5m+63wSxUf84TPc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=war98YDfy5zvI+x YdgDbl7cxRPE=; b=oXwRKah2PGbkDEx9adDbCB1EwT8VwOGh7jlCl27V2BJde1c balYQTbKTJvmRBEdp4taVBiImJrCGMD32Lmw2U230DcuPs3DrsHx8Js44VRanFZ2 zA2aRCrW7e76M7I4TxLcoo9LtlRUD21stJ2W/7QIObD3OsuLWVM6tUYjF76s= X-Sasl-enc: dm5RGE6I8PhD0a2U0lDoAhUy7dh7jAKP/Dxlr+8Cb+os 1454175945 Received: from [192.168.1.2] (65-102-182-223.tukw.qwest.net [65.102.182.223]) by mail.messagingengine.com (Postfix) with ESMTPA id 295FF680118; Sat, 30 Jan 2016 12:45:45 -0500 (EST) Subject: Re: Cannot start the PostgreSQL service To: David Unsworth , "pgsql-admin-owner@postgresql.org" , "pgsql-in-general@postgresql.org" , "pgsql-in-general-owner@postgresql.org" , "pgsql-general@postgresql.org" , "pgsql-general-owner@postgresql.org" , "pgsql-admin@postgresql.org" References: From: Adrian Klaver Message-ID: <56ACF68D.7060709@aklaver.com> Date: Sat, 30 Jan 2016 09:44:45 -0800 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.2 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 01/30/2016 08:24 AM, David Unsworth wrote: > Hello. Sorry if I have sent this to too may mail boxes. I hope one of > them is correct. Please forward this on if not. For future reference, sending to --general would be sufficient. > > This was working until recently. In Services I right clicked on > properties and I think I changed the METHOD in pg_hba.conf from md5 to > trust. > I think after making this change the problems started. > > In Services I cannot start the PostgreSQL Server 8.4 due to Error:1069 > The service did not start due to a logon failure. Assuming this is a Windows machine, what version of the OS? How did you install Postgres on this machine? What user are you starting the service as? What if anything happened/changed between the time it was working and the time it stopped working? What is in the Postgres log prior to it shutting down? What is in the system(Windows) logs when you try to start the service? > > I have tried to set up pg_hba.conf correctly. Currently it is set to > the following - > > # TYPE DATABASE USER CIDR-ADDRESS METHOD > # IPv4 local connections: > host all all 127.0.0.1/32 trust > host all all 192.168.1.1/5432 trust > # IPv6 local connections: > host all all ::1/128 trust > > I have tried to set up pgpass.conf correctly as this was empty. > Currently set to the following - > > 127.0.0.1:5432:*:postgres:dbpass > > The errors remain. Also I have been getting the error "could not > connect to Server: Connection refused" detailed below - > > http://www.pgadmin.org/docs/1.14/connect-error.html > > I wanted to reload the configuration (before attempting to start the > Service again ) and I got the error "Reload command returned an error (1)". > > I am not sure what to try next. I have some databases I do not want to > lose if I can avoid it. I doubt you have lost the databases or will lose the databases. You are just not able to start the server. > > Any ideas? > > Thanks, Dave. > > > > > > > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general