Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r2Xpr-00HLPI-GA for pgsql-admin@arkaria.postgresql.org; Mon, 13 Nov 2023 14:22:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r2Xpp-00Fnk9-UP for pgsql-admin@arkaria.postgresql.org; Mon, 13 Nov 2023 14:22:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r2Xpp-00Fnjc-GZ for pgsql-admin@lists.postgresql.org; Mon, 13 Nov 2023 14:22:41 +0000 Received: from mail-yw1-x112f.google.com ([2607:f8b0:4864:20::112f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r2Xpm-006E5A-HQ for pgsql-admin@lists.postgresql.org; Mon, 13 Nov 2023 14:22:40 +0000 Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-5bf812041a6so48072027b3.3 for ; Mon, 13 Nov 2023 06:22:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699885356; x=1700490156; darn=lists.postgresql.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=K6F4ZX48oWUjU3r2C52MvTFKMlJqc7GDukmUfsr0HCU=; b=FO7NUnGG5Ju9T8Xv5Y/0JUviLYe99mH+9qTP3sNRvJrs24skFzZmBZF/JG0fqMGXYq ROsjtFvd5nBqIMuPLsNv4Fn6bxDBjbvYfmv5QsofmPH4+5K5arhtku5gaCF9IHRtTWzr IvAsR4BJI3oZ6br0s+NVgd5tgr2EZi9IofXwyyQPnm1m6BCy81uXt6VMcsZa2p0KvxTQ 069ilCuuJWhDZmzeN5yMwfgsPP/YU6mBLyhfRuUkGxABXryorhRW/zEWRy4MXFkfRibP SBux6mNPKoFDSqFB1FbOFgQgK6Zb8eVuhrPFroPf2hosYdvwAkH2QEQHq7OU7NE78s5W Eqmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699885356; x=1700490156; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=K6F4ZX48oWUjU3r2C52MvTFKMlJqc7GDukmUfsr0HCU=; b=wWGYbpMuiQ6LdHYmLOPSzweoOsqAl1gGeca3SHsxfVzfTqQfb9NgRMCL02Vo3TdIH6 seBMxdYZlDkuQ4S6EaiGpdPmxxtphe7KD4BUZKoYndCGnGFuSffYJVnm/2sw0zWg1XR4 UGUXQNo+Sx6g/r5V0wDL6k9qohvWq41UOk0W/x+EMEbBcMq833Adk0Qmi9tbI/3SpjS+ pMbklPO7YTwnAuGzsAg/EDqViCqDoW2Sw1gGMvDfMDJlSVLGm0LYxqrgn3fAH2yROyiH S+PeWBZeZcSd4UzBUxQEsoEwPL701KsnDYtDd4c2CqYs/1R+5SW0UX0g2wg9dxhOw4FV 3Ycw== X-Gm-Message-State: AOJu0YywFNr6ZHvXZwyb79ZbIULXRKgvhlm7kqP7tuorAAL320xJNEay I8d53sSRafXFNeFGWM4X3T/aTenU8uw= X-Google-Smtp-Source: AGHT+IHpwTS76PtjYdknsDcG8PDk//eHiAl8byPG9Wy09yR1ZQKWZk1giBWZqEayvgTF2QFXktpJ/Q== X-Received: by 2002:a81:6d12:0:b0:5a8:9b88:745c with SMTP id i18-20020a816d12000000b005a89b88745cmr7110476ywc.13.1699885356372; Mon, 13 Nov 2023 06:22:36 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::44? ([2600:1700:bd2c:b810::44]) by smtp.googlemail.com with ESMTPSA id k184-20020a0dfac1000000b00594fb0e2db3sm1795995ywf.138.2023.11.13.06.22.35 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 13 Nov 2023 06:22:35 -0800 (PST) Content-Type: multipart/alternative; boundary="------------HBD0tTwVC3sOAC1sgaVUSz7P" Message-ID: Date: Mon, 13 Nov 2023 08:22:35 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pgagent-pg16 could not start: Error 1053 Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------HBD0tTwVC3sOAC1sgaVUSz7P Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit They might not know.  Especially since pgsql-admin is not the pgadmin mailing list. https://github.com/pgadmin-org/pgadmin4/issues https://www.pgadmin.org/support/list/ On 11/13/23 03:46, B Liu wrote: > Hi Erik, > > I installed postgresql 12 and its pgagent on my laptop, which works for > windows server 2012, unfortunately the pgagent is not working, like the > pgagent 16 version, it is in the starting stage forever. So it looks like > the pgagent doesn't work for windows 10 and windows server 2019 then. Is > there any plan that the admin team will provide a working version for the > latest windows server? > > Kind Regards > > Bin > > On Fri, Nov 10, 2023 at 12:54 PM Erik Serrano wrote: > > Dear B. Liu > > What you say makes sense to me that the file you are installing is > defective or incompatible. I suggest you look for another distribution > and reinstall it. > I hope it helps you and greetings > > /* > */ > /* > */ > /*Erik R. Serrano Saavedra*/ > /*Ingeniero de Sistemas Informáticos*/ > /*      Data Base Administrator*/ > > /**/ > > > El vie, 10 nov 2023 a las 5:43, B Liu () escribió: > > Dear Erik, > Many thanks for your help. > Regarding the windows server 2019, it probably is a > virtual machine. After I increased the low time value, there is no > error code 1053 any more, but the pgagent service is on starting > status forever. To test if the pgagent works, I installed the same > pgagent on my laptop, it gave the same service starting status > forever, but not into any running stage. > I am pretty sure that the latest pgagent is not working > for windows 10 or windows server 2019! I have one postgres-pg12 > working on windows server 2012 though. > Kind Regards > Bin > > On Thu, Nov 9, 2023 at 2:14 PM B Liu wrote: > > Dear Erik, > > Many thanks for your email. > > The pgagent was installed on a brand new windows server 2019, > it shouldn't have any file corrupted files, and it was > installed via the pgagent installer, which I don't think there > is any permission issue,  the local firewall has opened the > postgresql port 5432 unless there is another port need to be > opened, when I installed the pgagent, I chose the port 5432 > anyway. > > It narrows down to the low time value, I followed some advice > and increased it. When I started pgagent service, it states it > is starting, but doesn't go to the running stage, this time no > error message, nothing in the postgresql log file. > > I wonder if there is a working version of pgagent exist? This > could explain why there is no official pgagent downloadable > file on the official web site anymore! > > Could anybody from the admin team kindly give some update? > > Kind Regards > > Bin > > On Thu, Nov 9, 2023 at 1:06 PM Erik Serrano > wrote: > > Dear, > > The postgresql error indicates that common reasons for > this error include: > > * Low timeout value > * Firewall restrictions > * Corrupt files > * file permissions > > Check that out in the meantime, I hope it helps you. > Greetings > > /* > */ > /*Erik R. Serrano Saavedra*/ > /*Ingeniero de Sistemas Informáticos*/ > /*    Data Base Administrator*/ > /*eserranos@gmail.com > */ > /* 998596691*/ > /**/ > > > El jue, 9 nov 2023 a las 9:51, B Liu > () escribió: > > Hi there, > > I finally downloaded pgagent from EDB installer, when > I tried to start pgagent-pg16 service for the first > time, it couldn't start, the error message saying: > Windows could not start postgres-pg16 service on local > computer, error code 1053. > > Local server is windows server 2019. Could anybody > from the admin team advise on this? > > Kind Regards > > Bin > -- Born in Arizona, moved to Babylonia. --------------HBD0tTwVC3sOAC1sgaVUSz7P Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
They might not know.  Especially since pgsql-admin is not the pgadmin mailing list.

https://github.com/pgadmin-org/pgadmin4/issues
https://www.pgadmin.org/support/list/


On 11/13/23 03:46, B Liu wrote:
Hi Erik,

I installed postgresql 12 and its pgagent on my laptop, which works for windows server 2012, unfortunately the pgagent is not working, like the pgagent 16 version, it is in the starting stage forever. So it looks like the pgagent doesn't work for windows 10 and windows server 2019 then. Is there any plan that the admin team will provide a working version for the latest windows server?

Kind Regards

Bin

On Fri, Nov 10, 2023 at 12:54 PM Erik Serrano <eserranos@gmail.com> wrote:
Dear B. Liu

What you say makes sense to me that the file you are installing is defective or incompatible. I suggest you look for another distribution and reinstall it.
I hope it helps you and greetings



Erik R. Serrano Saavedra
Ingeniero de Sistemas Informáticos
      Data Base Administrator



El vie, 10 nov 2023 a las 5:43, B Liu (<binliucam@gmail.com>) escribió:
Dear Erik,
Many thanks for your help.
Regarding the windows server 2019, it probably is a virtual machine. After I increased the low time value, there is no error code 1053 any more, but the pgagent service is on starting status forever. To test if the pgagent works, I installed the same pgagent on my laptop, it gave the same service starting status forever, but not into any running stage. 
I am pretty sure that the latest pgagent is not working for windows 10 or windows server 2019! I have one postgres-pg12 working on windows server 2012 though.
Kind Regards
Bin

On Thu, Nov 9, 2023 at 2:14 PM B Liu <binliucam@gmail.com> wrote:
Dear Erik,

Many thanks for your email.

The pgagent was installed on a brand new windows server 2019, it shouldn't have any file corrupted files, and it was installed via the pgagent installer, which I don't think there is any permission issue,  the local firewall has opened the postgresql port 5432 unless there is another port need to be opened, when I installed the pgagent, I chose the port 5432 anyway. 

It narrows down to the low time value, I followed some advice and increased it. When I started pgagent service, it states it is starting, but doesn't go to the running stage, this time no error message, nothing in the postgresql log file. 

I wonder if there is a working version of pgagent exist? This could explain why there is no official pgagent downloadable file on the official web site anymore!

Could anybody from the admin team kindly give some update?

Kind Regards

Bin

On Thu, Nov 9, 2023 at 1:06 PM Erik Serrano <eserranos@gmail.com> wrote:
Dear,

The postgresql error indicates that common reasons for this error include:

* Low timeout value
* Firewall restrictions
* Corrupt files
* file permissions

Check that out in the meantime, I hope it helps you.
Greetings


Erik R. Serrano Saavedra
Ingeniero de Sistemas Informáticos
      Data Base Administrator
        eserranos@gmail.com
                 998596691


El jue, 9 nov 2023 a las 9:51, B Liu (<binliucam@gmail.com>) escribió:
Hi there,

I finally downloaded pgagent from EDB installer, when I tried to start pgagent-pg16 service for the first time, it couldn't start, the error message saying: Windows could not start postgres-pg16 service on local computer, error code 1053.

Local server is windows server 2019. Could anybody from the admin team advise on this?

Kind Regards

Bin

--
Born in Arizona, moved to Babylonia.
--------------HBD0tTwVC3sOAC1sgaVUSz7P--