Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aPcDC-0006lk-9N for pgsql-general@arkaria.postgresql.org; Sat, 30 Jan 2016 20:33:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aPcDB-0004O0-Nt for pgsql-general@arkaria.postgresql.org; Sat, 30 Jan 2016 20:33:37 +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 1aPcD9-0004K5-Rz for pgsql-general@postgresql.org; Sat, 30 Jan 2016 20:33:36 +0000 Received: from mail-pf0-x22e.google.com ([2607:f8b0:400e:c00::22e]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aPcD3-0006oG-5f for pgsql-general@postgresql.org; Sat, 30 Jan 2016 20:33:34 +0000 Received: by mail-pf0-x22e.google.com with SMTP id n128so60381448pfn.3 for ; Sat, 30 Jan 2016 12:33:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucee-org.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=FxzGc62lecfWsP8W8zpn2E+YmmctJ11gBPBfRgqL/fs=; b=QUzjp76YiHhLMv4jSG5LaBVGnCPrmKnLZK12pBjNWMT2F/3gEmgU7yv30tTavqc3x9 Opc0F+edr0hShPuIam9W5mWgKZ5JA50ncYdlD8dCIiODEf2Vqpfqo04cc4GJAkt7Lw4M SNRJmkaF3G8NSsZY94myYxM7xHVXN0NdzjwxwWqAlIj4TqWVN3srmdlnBXXLEVNPubSV 71OhE/EErIvr18kjW2UTGZX+xB6YFFI16hT8Au25Ls7DMU7B97EBDc4+ItCG3UeqHTCM MyyNwEiPof9ttl+hhNlCOfZ2U5bQpyDgZ2OcezQHqeBiirw4hiGoQUVIR3QN3vUMmQ97 Vn5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type; bh=FxzGc62lecfWsP8W8zpn2E+YmmctJ11gBPBfRgqL/fs=; b=V7lECprebeqkEfF7IhVmGFkSvFvHu109YraNo2bJzAlWDhFCAMrhcRp9/sPZ2jNuOO 6H7qeOal7cdJgIaMKsH4cEpXC5dHLrj4tODpqcYSJwMhkMPNr4lPwM8ZT/WmWpHSjJgN 7tg6VSV8R2bRVqpj4FUT7rAZap14RRQyZJ1DO9B4g0+0oP0Ws5Cg23v5rZE/TiyzchrQ jtUqzAlfhvpRM4+Ulg4rm95IIDY3JoqPB5em1v6GAV9NCEonzFbKplKOPsbktUXzHwbS gZ+8nLJidCmfsCsbqKtsUQeweLv8POp8RaBKxnDw8nNZsYziK0fEuRP7kixvpokijGjz zAwQ== X-Gm-Message-State: AG10YOTvu9jKPAEGlKbc4NrJ9HZJi1oMuiLMh/WA5VAeEHQwNzobb9oXVqA4KrS3ubNHCw== X-Received: by 10.98.73.149 with SMTP id r21mr25037022pfi.140.1454186008108; Sat, 30 Jan 2016 12:33:28 -0800 (PST) Received: from [192.168.1.11] (cpe-108-185-131-196.socal.res.rr.com. [108.185.131.196]) by smtp.googlemail.com with ESMTPSA id 89sm32369978pfi.2.2016.01.30.12.33.27 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Jan 2016 12:33:27 -0800 (PST) Subject: Re: Cannot start the PostgreSQL service To: Adrian Klaver , David Unsworth References: <56ACF68D.7060709@aklaver.com> <56AD17B4.80105@aklaver.com> <56AD18C3.9040605@lucee.org> Cc: pgsql-general From: "Igal @ Lucee.org" Message-ID: <56AD1E04.9080306@lucee.org> Date: Sat, 30 Jan 2016 12:33:08 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56AD18C3.9040605@lucee.org> Content-Type: multipart/alternative; boundary="------------070905010203060406070300" X-Pg-Spam-Score: -2.6 (--) 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 This is a multi-part message in MIME format. --------------070905010203060406070300 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 1/30/2016 12:10 PM, Igal @ Lucee.org wrote: > > Did you check the Windows Event Viewer? When a service fails to start > you should see the details there in the Application log errors. Sorry, I just realized that you had this: > 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 you are using PostgreSQL 8.4? Not sure why you would do that on a development machine (assuming that you're not running production servers on Windows 7 Home) Looks to me like the issue is that the service is running under the Local System account, which is not recognized by PostgreSQL, and that's why the log shows [role "SYSTEM" does not exist]. If you have installed using the installer then you should probably have a "postgres" account on the machine? If so, set the service to Log On as that account. --------------070905010203060406070300 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit On 1/30/2016 12:10 PM, Igal @ Lucee.org wrote:

Did you check the Windows Event Viewer?  When a service fails to start you should see the details there in the Application log errors.
Sorry, I just realized that you had this:

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 you are using PostgreSQL 8.4?  Not sure why you would do that on a development machine (assuming that you're not running production servers on Windows 7 Home)

Looks to me like the issue is that the service is running under the Local System account, which is not recognized by PostgreSQL, and that's why the log shows [role "SYSTEM" does not exist].  If you have installed using the installer then you should probably have a "postgres" account on the machine?  If so, set the service to Log On as that account.

--------------070905010203060406070300--