This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_to:vpop3db_postgresql_service_not_starting [2014/06/10 11:30] – external edit 127.0.0.1 | how_to:vpop3db_postgresql_service_not_starting [2018/01/02 10:42] – [Other things to try] paul | ||
---|---|---|---|
Line 1: | Line 1: | ||
======VPOP3DB Service not starting====== | ======VPOP3DB Service not starting====== | ||
VPOP3DB is the current name of the VPOP3 instance of PostgreSQL. Earlier versions of VPOP3 used the name ' | 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]] | ||
+ | * [[Timeout while VPOP3DB is starting]] | ||
If the PostgreSQL service doesn' | If the PostgreSQL service doesn' | ||
* Look in the Windows // | * 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 ' | + | * 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 ' |
- | + | * Check the Processes list (for all users) in Windows' | |
- | You can also try starting the PostgreSQL service manually: | + | |
- | + | ||
- | * For VPOP3 v3 and v4, from a command prompt, run "runas / | + | |
- | * For VPOP3 v5 and later, from a command prompt, run "runas /user:vpop3postgres | + | |
- | + | ||
- | Then | + | |
- | c: | + | |
- | cd \vpop3\pgsql\bin | + | |
- | pg_ctl -D " | + | |
- | + | ||
- | (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 | + | |
=====Event Viewer Entries===== | =====Event Viewer Entries===== | ||
Line 60: | Line 50: | ||
====no pg_hba.conf entry for host ":: | ====no pg_hba.conf entry for host ":: | ||
+ | ====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. | 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. | ||
Line 88: | Line 79: | ||
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 | 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 ' | + | You will then need to restart the VPOP3DB/PostgreSQL service in Windows. Note that sometimes PostgreSQL cannot close down properly, and there will be unwanted ' |
====Shared memory problems==== | ====Shared memory problems==== | ||
Line 106: | Line 97: | ||
Increasing this so much that other programs start paging to disk will be counter-productive, | Increasing this so much that other programs start paging to disk will be counter-productive, | ||
+ | |||
+ | =====Other things to try===== | ||
+ | |||
+ | ===Start service manually=== | ||
+ | You can also try starting the PostgreSQL service manually: | ||
+ | |||
+ | * For VPOP3 v3 and v4, from a command prompt, run "runas / | ||
+ | * For VPOP3 v5 and later, from a command prompt, run "runas / | ||
+ | |||
+ | Then | ||
+ | c: | ||
+ | cd \vpop3\pgsql\bin | ||
+ | pg_ctl -D " | ||
+ | | ||
+ | (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 service Logon user to //Local System Account// will solve the problem (make sure that //Allow service to interact with desktop// is not checked). | ||
+ | |||
+ | {{: | ||
+ | |||
+ | It is not installed this way by default because the ' | ||
+ | |||
+ | ===Reinstall PostgreSQL program files=== | ||
+ | It isn't unknown for a virus scanner or Internet security program (or a ' | ||
+ | |||
+ | In this case, in v6 or later you can manually replace all the PostgreSQL program files without having to reinstall or lose data. To do this, go to a command prompt in the VPOP3 installation directory and run: | ||
+ | |||
+ | ==VPOP3 v6.x== | ||
+ | bsdtar -xvf pgsql.tbz | ||
+ | | ||
+ | ==VPOP3 v7.x== | ||
+ | 7z x -aoa -r pgsql95.7z | ||
+ | |||
+ | That should overwrite all the PostgreSQL program files/ |