Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aPbnp-0005V4-Ks for pgsql-general@arkaria.postgresql.org; Sat, 30 Jan 2016 20:07:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aPbno-0003sa-1f for pgsql-general@arkaria.postgresql.org; Sat, 30 Jan 2016 20:07:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aPbnl-0003s0-Pl for pgsql-general@postgresql.org; Sat, 30 Jan 2016 20:07:21 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aPbnf-0008Ah-Bk for pgsql-general@postgresql.org; Sat, 30 Jan 2016 20:07:19 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 799902C2FE for ; Sat, 30 Jan 2016 15:07:12 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Sat, 30 Jan 2016 15:07:12 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h=cc :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=6aqmX9oOGVi8SQK3aiNZ43B10/k=; b=USjaWg p6mxg5fxnMnE6vF6F/NW2Of5xHvl5fnmpLVyWQ7YmJ/UYAMuDxlmqI7l/bOJHS3p iTVeJv3Km9slYdbujjvQVJngqclzIpiTmKBSokBYJ9YD/vtpJ0kpsvUx1EeiMc4H 4/cQvDgrZ6FsDLx9yEME0xCIYJ79fW5L8EgcI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=6aqmX9oOGVi8SQK 3aiNZ43B10/k=; b=cQs/cpmh/4JsvC9rqv7ZeijwMDStDklJbdPAWBzhu+TXabE LxFyTOwWCu+vRh/A+OlSdby1P5TSvE/vSgqMZLLIjw6jw3QypBEOJENoOggTPjl/ gCnxfxDQ4xB+wjUV3FbStqwiPCc8NoDBglIf+eoJDfUl9C/dHZlSqMQPO2tg= X-Sasl-enc: 94mrHVTeFdr2KwzAxNc6b4/ogZw36BH5QkH6stF1GpPa 1454184432 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 E3902C00014; Sat, 30 Jan 2016 15:07:11 -0500 (EST) Subject: Re: Cannot start the PostgreSQL service To: David Unsworth References: <56ACF68D.7060709@aklaver.com> Cc: pgsql-general From: Adrian Klaver Message-ID: <56AD17B4.80105@aklaver.com> Date: Sat, 30 Jan 2016 12:06:12 -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: -2.7 (--) 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 11:01 AM, David Unsworth wrote: Ccing list, so more eyes can see. > Hello. Thanks for the reply. Here is some more info. > > Assuming this is a Windows machine, what version of the OS? > Windows 7 Home Premium > > How did you install Postgres on this machine? > With Hold'em Manager software many years ago. > > What user are you starting the service as? > Administrator > > What if anything happened/changed between the time it was working and > the time it stopped working? > Editing pg_hba.conf, right clicking in Services, Properties editing log > on details. Service would not start when logging on the next day but > was okay at the time. So the was the machine rebooted between the time it worked and the time it did not or did you just log out and back in? > > What is in the Postgres log prior to it shutting down? > Checked pg_log folder. Log file from 2012. Nothing since the problem. I got to believe there is a newer log file then that. Is there more then one instance of Postgres on this machine? > > What is in the system(Windows) logs when you try to start the service? > 2016-01-25 18:45:19 GMTFATAL: the database system is starting up > 2016-01-27 01:09:47 GMTFATAL: role "SYSTEM" does not exist > pg_ctl: PID file "C:/Program Files > (x86)/PostgreSQL/8.4/data/postmaster.pid" does not exist So there is an almost two day gap between FATAL errors. There is nothing else between those messages or immediately prior to the first one? > > Previously reported errors - > > In Services I cannot start the PostgreSQL Server 8.4 due to Error:1069 > The service did not start due to a logon failure. > > 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 > > When trying to reload the configuration (before attempting to start the > Service again ) and I got the error "Reload command returned an error (1)". > > -- 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