Не удалось запустить службу postgresql ошибка 1053

I installed postgres on windows7 and tried to start the service through control panel. It produces error 1053.

When I try to run postgres.exe from command line, I get this message:

C:\Program Files (x86)\PostgreSQL\9.0\bin>postgres.exe
2011-07-24 14:02:29 IST LOG:  could not create file "postmaster.opts": Permission denied

The default data directory is

C:\Program Files (x86)\PostgreSQL\9.0\data

I have set the PGDATA env variable to the above directory.

Also, I have edited the pg_hba.conf file in that directory to add a new line as below:

local   all postgres    ident  sameuser

I tried to start the service with postgresql server allowed (both private and public networks ticked) in Windows Firewall, and when that didn’t solve the problem, turned off the firewall for both public and private networks..

Still the service cannot be started. I tried disabling the AVG resident shield. None of these worked.

Any idea what to do?

update:

I tried this:

C:\Program Files (x86)\PostgreSQL\9.0\bin>pg_ctl restart
pg_ctl: PID file "C:/Program Files (x86)/PostgreSQL/9.0/data/postmaster.pid" does not exist
Is server running?
starting server anyway
server starting

C:\Program Files (x86)\PostgreSQL\9.0\bin>2011-07-24 16:12:57 IST LOG:  could not create file "postmaster.opts":

Still no luck.

As for the logs, I found 2 txt files in folder data/pg_log. They contain logs of events immediately after installation, not my later attempts at starting postgres. I have put it here.

In windows event viewer, I get a series of error event entries like http://pastebin.com/K6jUPPAy. All of them contain messages similar to:

2011-07-24 12:46:44 IST FATAL:  could not access status of transaction
0 2011-07-24 12:46:44 IST DETAIL:  Could not open file
"pg_notify/0000": Permission denied.

If there are any other logs, please tell me where I can find them.

Error 1053 is a common error code triggered while working with the PostgreSQL database.

It displays the message “the service did not respond to the start or control request in a timely fashion” due to incorrect file permissions, missing files etc.

As a part of our PostgreSQL Management Services, we help customers to fix PostgreSQL errors routinely.

Let us today discuss the possible reasons and solutions for Error code1053.

What causes Postgresql error 1053

The error message 1053 states ‘The service did not respond to the start or control request in a timely fashion’. If a request to start a service does not respond in a specific time window, it triggers 1053 error message.

The common reasons for this error include:

• Low timeout value
• Firewall restrictions
• Corrupted files
• Permission of file

Let us now look at each of these reasons in detail and the tips to fix them.

Low timeout value

The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all Windows services. By default, it will wait 30 seconds for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and respond to the Control Manager. This, in turn, triggers the 1053 error.

It can be fixed easily by setting a ServicesPipeTimeout DWORD value. This value overrides the default timeout value. However, incorrect usage of the use of the Microsoft Windows Registry Editor can cause serious damages like operating systems corruption and inability to boot.

To override the timeout value:

1. First, open the Registry editor from Start > Run > and type regedit.
2. Then,generate a backup of the registry files using the export option.
3. Next, navigate to location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
4. With the control folder selected, right click in the pane on the right and select new DWORD Value
Name the new DWORD: ServicesPipeTimeout

5. then, right-click ServicesPipeTimeout, and then click Modify
Click Decimal, type '180000'.
6. Finally, restart the system.

Firewall restrictions

If you see the error 1053 on a new PostgreSQL installation, it is most probably related to some firewall rules. Some firewalls prevent Postgres from starting. This could be a restriction on the port or any similar setting. Disabling the firewall temporarily will help to eliminate the firewall factor.

Permission of file

Another common reason that can trigger 1053 is the permission of the files. More details on the error can be obtained from the Windows Event viewer or PostgreSQL’s error logs.

For instance, this error will be triggered if the Postgres working directory was set to be read-only mode. This could happen as a result of any changes made by anti-virus programs installed in the server. Setting read permission to everyone can fix the issue here.

Corrupted files

Another common instance that triggers this error message is where the installation of the application is somewhat corrupt. Reinstallation can help to fix the issue here.

This error message may not be limited to corrupt PostgreSQL installation files at times. For instance, if any of the Windows core files are missing or somehow corrupt, it may cause some important modules not to work. As a result, it may trigger the same 1053  error.

We can use any of the file system checking tools to check the system file structure with that of a fresh copy present online. These tools then replace those files accordingly in case of a discrepancy.

[Need more assistance to solve PostgreSQL errors? We’ll help you.]

Conclusion

In short, the Postgresql error 1053 is triggered due to permission issues, timeout settings, firewall restrictions etc. Today we discussed some tips that our Support Engineers followed to fix the error 1053.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

I installed postgres on windows7 and tried to start the service through control panel. It produces error 1053.

When I try to run postgres.exe from command line, I get this message:

C:\Program Files (x86)\PostgreSQL\9.0\bin>postgres.exe
2011-07-24 14:02:29 IST LOG:  could not create file "postmaster.opts": Permission denied

The default data directory is

C:\Program Files (x86)\PostgreSQL\9.0\data

I have set the PGDATA env variable to the above directory.

Also, I have edited the pg_hba.conf file in that directory to add a new line as below:

local   all postgres    ident  sameuser

I tried to start the service with postgresql server allowed (both private and public networks ticked) in Windows Firewall, and when that didn’t solve the problem, turned off the firewall for both public and private networks..

Still the service cannot be started. I tried disabling the AVG resident shield. None of these worked.

Any idea what to do?

update:

I tried this:

C:\Program Files (x86)\PostgreSQL\9.0\bin>pg_ctl restart
pg_ctl: PID file "C:/Program Files (x86)/PostgreSQL/9.0/data/postmaster.pid" does not exist
Is server running?
starting server anyway
server starting

C:\Program Files (x86)\PostgreSQL\9.0\bin>2011-07-24 16:12:57 IST LOG:  could not create file "postmaster.opts":

Still no luck.

As for the logs, I found 2 txt files in folder data/pg_log. They contain logs of events immediately after installation, not my later attempts at starting postgres. I have put it here.

In windows event viewer, I get a series of error event entries like http://pastebin.com/K6jUPPAy. All of them contain messages similar to:

2011-07-24 12:46:44 IST FATAL:  could not access status of transaction
0 2011-07-24 12:46:44 IST DETAIL:  Could not open file
"pg_notify/0000": Permission denied.

If there are any other logs, please tell me where I can find them.

Fix Postgresql error 1053

Tutorials

Postgresql 1053 error is very common when you work with a databases based on PostgresSQL.

When this error occurs, you will usually see an error message which says «the service did not respond to the start or control request in a timely fashion«. This is as a result of incorrect file permission or missing files.

Our Server Experts has helped a lot of people to fix PostgreSQL errors as such on a daily basis.

Why does the Postgresql error 1053 occurs?

This Postgresql 1053 error which states that «The service did not respond to the start or control request in a timely fashion» takes place once a request to start a service is not responding within the specified time it is suppose to.

It is caused by the following factors;

• Corrupted files
• Restrictions in Firewall
• Incorrect file permission
• Low timeout rate

We will look into these factors in details:

Corrupted files

When the installation of an application or software is somehow corrupted, the Postgresql error message 1053 will be triggered. I most cases, doing the installation again will help resolve this issue.

In other cases, some important window core files might be missing thereby causing some dependencies to malfunction. If this is the case, it is better to get a fresh copy via the official online source.

Need professional support in solving PostgreSQL errors? We can help you.

Restrictions in Firewall

Firewall rules can cause PostgreSQL 1053 error during installation. To get Postgres started successfully, you can disable such firewall rule temporarily.

Incorrect file permission

When there is an incorrect permission of the files, the 1053 PostgreSQL error could come up. The windows Event viewer will display more information about the error anyway.

For example, this error will come up if the Postgres working directory was set to read-only. Most Anti-virus application in the server could make such changes in the permission. In this case, the read permission to everyone on the system will help to resolve this issue.

Low timeout rate

All the Windows services are controlled by the Microsoft Windows Service Control Manager. The normal time a service would take to respond to an event is 30 seconds. In cases where some technical restrictions or issues with performances makes the service to take a longer time to respond, the 1053 error will be immediately triggered.

This error can be easily fixed if a ServicesPipeTimeout DWORD value is set. What this value does is to override the default timeout value.

To get through this issue, Do the following;

1. Locate the Registry editor from the Windows Search tool( Start —  Run ) and type regedit.

2. Use the export option to generate a backup of the registry files.

3. Next, go to the location;

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

4. When you get to the control folder, do a right click action and select new DWORD Value

Name the new DWORD: ServicesPipeTimeout

5. Then, do a right click action on the «ServicesPipeTimeout» and click on Modify;

you will see «Decimal» then type value  ‘180000‘.

6. Lastly, do a restart of the system.

Conclusion

Basically, the 1053 Postgresql error is prompted when there are permission issues, limit placed by firewall, timeout problems and so on. Our Support Experts can fix the 1053 error for you.