This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
how_to:vpop3db_postgresql_service_not_starting [2014/11/17 09:54] – [VPOP3DB Service not starting] paul | how_to:vpop3db_postgresql_service_not_starting [2018/11/14 10:45] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======VPOP3DB Service not starting====== | + | [[https://helpdesk.pscs.co.uk/865133-VPOP3DB-Service-not-starting]] |
- | VPOP3DB is the current name of the VPOP3 instance of PostgreSQL. Earlier versions of VPOP3 used the name ' | + | |
- | + | ||
- | * [[1069 - Login Failure - error when starting VPOP3DB service]] | + | |
- | + | ||
- | If the PostgreSQL service doesn' | + | |
- | + | ||
- | * Look in the Windows | + | |
- | * Look in the VPOP3\pgsql\data\pg_log folder for a log file created at the time when you started VPOP3. If that is there, you can read that (using Notepad) and see if it reports any problems with files or ' | + | |
- | + | ||
- | ===Start service manually=== | + | |
- | You can also try starting the PostgreSQL service manually: | + | |
- | + | ||
- | * For VPOP3 v3 and v4, from a command prompt, run " | + | |
- | * For VPOP3 v5 and later, from a command prompt, run "runas / | + | |
- | + | ||
- | Then | + | |
- | c: | + | |
- | cd \vpop3\pgsql\bin | + | |
- | pg_ctl | + | |
- | + | ||
- | (If your VPOP3 is installed in a different directory, change the above paths as appropriate) | + | |
- | + | ||
- | See what response you get to the pg_ctl command | + | |
- | + | ||
- | ===Change Service user to ' | + | |
- | Occasionally it won't start anyway. In this case, changing the VPOP3DB | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | It is not installed this way by default because the ' | + | |
- | =====Event Viewer Entries===== | + | |
- | In the Windows Event Viewer, view the // | + | |
- | + | ||
- | Depending on your installation, | + | |
- | The description for Event ID xxxx from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer.... | + | |
- | + | ||
- | If that's the case, don't worry, just look lower down in the event message. It will say something like | + | |
- | The following information was included with the event | + | |
- | + | ||
- | It is that information you need to see. Some possible event messages we have seen are: | + | |
- | + | ||
- | ====Timed out waiting for server startup==== | + | |
- | This can happen if the PC previously crashed, or there was a power failure. When the PC restarts, it can take some time for the database server to run its recovery process. This may take longer than the time allowed by the database service controller, especially if the PC is busy doing other recovery tasks. | + | |
- | + | ||
- | To solve this, go to Windows TaskManager (Ctrl-Alt-Del - choose TaskManager), | + | |
- | + | ||
- | ====pg_ctl: this data directory appears to be running a pre-existing postmaster==== | + | |
- | If this is the case, then usually it means that a previous attempt to start PostgreSQL was made, but it timed out or something, and is now in a ' | + | |
- | + | ||
- | To solve this, go to Windows TaskManager (Ctrl-Alt-Del - choose TaskManager), | + | |
- | + | ||
- | ====Postmaster.pid exists==== | + | |
- | If there is an event saying '' | + | |
- | + | ||
- | First check that the database software is not running in a partial state. Go to Windows TaskManager (Ctrl-Alt-Del - choose TaskManager), | + | |
- | + | ||
- | If the database software is not running, you can manually delete the VPOP3\pgsql\data\postmaster.pid file before restarting the VPOP3 service. | + | |
- | + | ||
- | ====pg_ctl: could not find postgres program executable==== | + | |
- | We have seen this happen if a virus scanner decides to delete part of the PostgreSQL installation, | + | |
- | + | ||
- | If you are using VPOP3 v5 or v6, the easiest thing to do is to manually reinstall the PostgreSQL part of the installation. To do this, open a command prompt and go to the VPOP3 installation directory. Then run:\\ | + | |
- | bsdtar -xvf pgsql.tbz | + | |
- | + | ||
- | If you are using VPOP3 v3 or v4, it is more difficult. Possibly the best thing to do is to install a temporary copy of the same version of VPOP3 on another PC, then copy the VPOP3\pgsql\bin, | + | |
- | ====PostgreSQL Log Entries==== | + | |
- | If you get **FATAL** or **PANIC** entries in the PostgreSQL log files (in **VPOP3\pgsql\data\pg_log**) then they may give more information about why PostgreSQL could not start. Some log entries we have come across are below. | + | |
- | + | ||
- | ====no pg_hba.conf entry for host ":: | + | |
- | This usually happens if the PC where VPOP3 is installed used to only have IPv4 installed, and has now had IPv6 added. The PostgreSQL configuration needs altering to support IPv6. | + | |
- | + | ||
- | Usually this only happens on Windows XP - earlier versions of Windows do not support IPv6, and later versions support IPv6 by default. Windows XP needs to have [[http:// | + | |
- | + | ||
- | To fix this problem, go to the **VPOP3\pgsql\data** folder on the server and edit the **pg_hba.conf** file using a plain text editor such as Notepad. | + | |
- | + | ||
- | Near the bottom of that file you should see a section saying | + | |
- | < | + | |
- | # TYPE DATABASE | + | |
- | + | ||
- | # IPv4 local connections: | + | |
- | host all | + | |
- | # IPv6 local connections: | + | |
- | #host all | + | |
- | </ | + | |
- | + | ||
- | Edit the last line to remove the # from the start, so it now says | + | |
- | + | ||
- | < | + | |
- | + | ||
- | # IPv4 local connections: | + | |
- | host all | + | |
- | # IPv6 local connections: | + | |
- | host all | + | |
- | </ | + | |
- | + | ||
- | In some cases the last two lines may not exist, in which case you can simply copy those lines from the example above and paste them into your pg_hba.conf file | + | |
- | + | ||
- | You will then need to restart the PostgreSQL service in Windows. Note that sometimes PostgreSQL cannot close down properly, and there will be unwanted ' | + | |
- | + | ||
- | ====Shared memory problems==== | + | |
- | The VPOP3 installer attempts to configure the database server to sensible defaults for the computer on which VPOP3 is running. Sometimes this may be wrong because of changes to the server configuration or other things. Most of the settings the installer could get wrong will not usually cause serious problems, but if the installer has overestimated the amount of memory available, then this could cause the VPOP3DB service to fail to start. | + | |
- | + | ||
- | To check, this look in the '' | + | |
- | + | ||
- | shared_buffers=1024MB | + | |
- | + | ||
- | This tells the database service how much memory it can use for its built-in cache. If this number is too high, so that Windows cannot give this amount of memory to the database server, then the VPOP3DB service will not start. | + | |
- | + | ||
- | You can decrease the value, eg to '' | + | |
- | + | ||
- | Since the VPOP3 installation of the PostgreSQL database server is a 32 bit version, you should not increase the value of this over 1024MB, even if the computer has much more memory available. PostgreSQL takes advantage of Windows' | + | |
- | + | ||
- | Do not set this value below about 32MB. The bigger it is, the faster the database server will be able to run, up to a maximum of about 1024MB. For computers with sufficient RAM (memory), then about 1/4 of the available RAM is a good starting point (within the above limits) - eg if the PC has 2GB of RAM, then 512MB is a sensible starting point. | + | |
- | + | ||
- | Increasing this so much that other programs start paging to disk will be counter-productive, | + |