Обсуждение: pgagent-pg16 could not start: Error 1053
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
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
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
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 RegardsBin
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.
GreetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base Administrator998596691El 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 RegardsBin
Ok, well what you are telling me... now I need to know some things regarding the installation of your Windows Server 2019
Is it a clone Virtual Machine, Docker, Kubernete or some pre-installed image or is it a complete new installation from scratch?
Reason: It is simple, when cloning the VMs, Docker Images, Kubernetes or machine in the cloud. The REGEDIT level records in Windows are copied exactly the same as the original but that has consequences since if my computer needs to modify the registry when installing pgagent, the account may not have permissions to modify the registry or it may be corrupted by cloning. To avoid this point, it is the query...
Greetings
Is it a clone Virtual Machine, Docker, Kubernete or some pre-installed image or is it a complete new installation from scratch?
Reason: It is simple, when cloning the VMs, Docker Images, Kubernetes or machine in the cloud. The REGEDIT level records in Windows are copied exactly the same as the original but that has consequences since if my computer needs to modify the registry when installing pgagent, the account may not have permissions to modify the registry or it may be corrupted by cloning. To avoid this point, it is the query...
Greetings
Erik R. Serrano Saavedra
Ingeniero de Sistemas Informáticos
Data Base Administrator
El jue, 9 nov 2023 a las 11:14, B Liu (<binliucam@gmail.com>) escribió:
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 RegardsBinOn 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.
GreetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base Administrator998596691El 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 RegardsBin
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 RegardsBinOn 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.
GreetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base Administrator998596691El 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 RegardsBin
Dear B. Liu
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 RegardsBinOn 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 RegardsBinOn 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.
GreetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base Administrator998596691El 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 RegardsBin
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. LiuWhat 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 greetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base AdministratorEl 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 RegardsBinOn 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 RegardsBinOn 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.
GreetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base Administrator998596691El 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 RegardsBin
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 RegardsBinOn Fri, Nov 10, 2023 at 12:54 PM Erik Serrano <eserranos@gmail.com> wrote:Dear B. LiuWhat 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 greetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base AdministratorEl 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 RegardsBinOn 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 RegardsBinOn 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.
GreetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base Administrator998596691El 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 RegardsBin
--
Born in Arizona, moved to Babylonia.
Born in Arizona, moved to Babylonia.
Thanks, I reported it as a bug issue ....
All the best
Bin
On Mon, Nov 13, 2023 at 2:22 PM Ron <ronljohnsonjr@gmail.com> wrote:
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 RegardsBinOn Fri, Nov 10, 2023 at 12:54 PM Erik Serrano <eserranos@gmail.com> wrote:Dear B. LiuWhat 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 greetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base AdministratorEl 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 RegardsBinOn 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 RegardsBinOn 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.
GreetingsErik R. Serrano SaavedraIngeniero de Sistemas InformáticosData Base Administrator998596691El 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 RegardsBin--
Born in Arizona, moved to Babylonia.