Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8Nk8-0005Om-P1 for pgsql-admin@arkaria.postgresql.org; Wed, 19 Aug 2020 13:03:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k8Nk7-00050A-Nz for pgsql-admin@arkaria.postgresql.org; Wed, 19 Aug 2020 13:03:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8Nk7-000503-Ey for pgsql-admin@lists.postgresql.org; Wed, 19 Aug 2020 13:03:03 +0000 Received: from jakobs.com ([85.214.83.89] helo=rs.plausibolo.de) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8Nk5-0008SA-GK for pgsql-admin@lists.postgresql.org; Wed, 19 Aug 2020 13:03:03 +0000 Received: from localhost (localhost [127.0.0.1]) by rs.plausibolo.de (Postfix) with ESMTP id 5F6E0380627; Wed, 19 Aug 2020 15:03:00 +0200 (CEST) Received: from rs.plausibolo.de ([127.0.0.1]) by localhost (h2367442.stratoserver.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lfGhQUXc9c0d; Wed, 19 Aug 2020 15:03:00 +0200 (CEST) Received: from [192.168.178.97] (ip-37-201-154-65.hsi13.unitymediagroup.de [37.201.154.65]) by rs.plausibolo.de (Postfix) with ESMTPSA id 0B5AE380624; Wed, 19 Aug 2020 15:02:59 +0200 (CEST) Subject: Re: pg96 not running as service To: Peter Watt Cc: pgsql-admin@lists.postgresql.org References: From: Holger Jakobs Message-ID: <4e8f2fd4-1bbd-635b-0a88-5d82556f8099@jakobs.com> Date: Wed, 19 Aug 2020 15:02:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------C23E7193E48A2B989320E8EC" Content-Language: de-DE List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------C23E7193E48A2B989320E8EC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit There should be more detail records in the event viewer. What you show is only the first line. Am 19.08.20 um 14:50 schrieb Peter Watt: > Thanks Holger.  > > The Windows Event Viewer only states: > > pg_ctl: could not start server > Examine the log output.  > > which was not so useful :-) > > On Wed, 19 Aug 2020 at 22:13, Holger Jakobs > wrote: > > Don't check the log file, but Windows event viewer. > > Only after successful start postgresql starts to write into the > log file. > > Am 19. August 2020 14:35:19 MESZ schrieb Peter Watt > >: > > Hi All, > System:Win server 2016 > Version:pg9.6  > > I have had an odd problem happen today. My server that has > been running fine for 2 years has decided that it will not > start any more. Investigating a little i have found that it > works fine when running from command line, using either of the > below commands: > > C:\POSTGR~1\pg96\..\pg96\bin\pg_ctl start -c -w --log > "C:\tmp\logs.txt" -D "C:\PostgreSQL\data\pg96" > > C:\PostgreSQL\pg96\pgservice.exe "//TS//PostgreSQL 9.6 Server" > > but when trying to run as a service (using  > C:\PostgreSQL\pg96\pgservice.exe "//RS//PostgreSQL 9.6 > Server") as system user i get this in the windows event viewer > pg_ctl: could not start server > Examine the log output. > > I have looked at the logs, both in C:\tmp\logs.txt (empty > file)  and C:\PostgreSQL\data\logs\pg96 (no new lines) no no > avail. Can anyone help me out?? > > This seems to happen soon after I created a new DB > using pgadmin4 and had a new instance of bitbucket populate > it, but not immediately after. > > Thanks for your help! > > Peter > > > -- > Holger Jakobs, Bergisch Gladbach > +49 178 9759012 > - sent from mobile, therefore short - > -- Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012 --------------C23E7193E48A2B989320E8EC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

There should be more detail records in the event viewer. What you show is only the first line.

Am 19.08.20 um 14:50 schrieb Peter Watt:
Thanks Holger. 

The Windows Event Viewer only states:

pg_ctl: could not start server
Examine the log output. 

which was not so useful :-)

On Wed, 19 Aug 2020 at 22:13, Holger Jakobs <holger@jakobs.com> wrote:
Don't check the log file, but Windows event viewer.

Only after successful start postgresql starts to write into the log file.

Am 19. August 2020 14:35:19 MESZ schrieb Peter Watt <pwatt01@gmail.com>:
Hi All,
System:Win server 2016
Version:pg9.6 

I have had an odd problem happen today. My server that has been running fine for 2 years has decided that it will not start any more. Investigating a little i have found that it works fine when running from command line, using either of the below commands:

C:\POSTGR~1\pg96\..\pg96\bin\pg_ctl start -c -w --log "C:\tmp\logs.txt" -D "C:\PostgreSQL\data\pg96"

C:\PostgreSQL\pg96\pgservice.exe "//TS//PostgreSQL 9.6 Server"

but when trying to run as a service (using  C:\PostgreSQL\pg96\pgservice.exe "//RS//PostgreSQL 9.6 Server") as system user i get this in the windows event viewer
pg_ctl: could not start server
Examine the log output.

I have looked at the logs, both in C:\tmp\logs.txt (empty file)  and C:\PostgreSQL\data\logs\pg96 (no new lines) no no avail. Can anyone help me out??

This seems to happen soon after I created a new DB using pgadmin4 and had a new instance of bitbucket populate it, but not immediately after.

Thanks for your help!

Peter

--
Holger Jakobs, Bergisch Gladbach
+49 178 9759012
- sent from mobile, therefore short -
-- 
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
--------------C23E7193E48A2B989320E8EC--