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:database_issues [2011/12/22 09:21] – [Database corruption] paul | how_to:database_issues [2013/06/24 08:36] – [PostgreSQL Log Entries] paul | ||
---|---|---|---|
Line 1: | Line 1: | ||
======Database Issues====== | ======Database Issues====== | ||
- | VPOP3 version 3 and later use the [[http:// | + | VPOP3 version 3 and later use the [[http:// |
=====Disk Caching===== | =====Disk Caching===== | ||
Line 11: | Line 11: | ||
It is slightly less safe, but still usually OK, to have a UPS with automated shutdown of the PC. You still have to ensure that the PC is not just turned off without shutting down properly. | It is slightly less safe, but still usually OK, to have a UPS with automated shutdown of the PC. You still have to ensure that the PC is not just turned off without shutting down properly. | ||
- | If you don't have either of these facilities, then make sure you turn off write-back caching in Windows. | + | If you don't have either of these facilities, then make sure you turn off write-back caching in Windows. (Note that ' |
Exactly how you turn off write-back caching depends on your version of Windows, and the disk controller. | Exactly how you turn off write-back caching depends on your version of Windows, and the disk controller. | ||
Line 32: | Line 32: | ||
* [[PostgreSQL server won't start due to damaged log files]] or missing pg_control file | * [[PostgreSQL server won't start due to damaged log files]] or missing pg_control file | ||
* [[Total Rebuild of Database]] | * [[Total Rebuild of Database]] | ||
+ | * [[Repairing corrupted database]] | ||
Our chargeable support service will be able to help with this if necessary. Note that we cannot guarantee recovering data, as that will depend on how badly the database has been damaged, and when the latest good backup was. | Our chargeable support service will be able to help with this if necessary. Note that we cannot guarantee recovering data, as that will depend on how badly the database has been damaged, and when the latest good backup was. | ||
Line 37: | Line 38: | ||
If the PostgreSQL service doesn' | 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 ' | * 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 Windows event log for entries relating to PostgreSQL | ||
You can also try starting the PostgreSQL service manually: | You can also try starting the PostgreSQL service manually: | ||
- | From a command prompt, run "runas / | + | * For VPOP3 v3 and v4, from a command prompt, run "runas / |
+ | * For VPOP3 v5 and later, from a command prompt, run "runas / | ||
Then | Then | ||
Line 53: | Line 55: | ||
See what response you get to the pg_ctl command | See what response you get to the pg_ctl command | ||
+ | ====Event Viewer Entries==== | ||
====PostgreSQL Log Entries==== | ====PostgreSQL Log Entries==== | ||
- | If you get **FATAL** 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. | + | 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 ":: | ===no pg_hba.conf entry for host ":: |