how_to:database_issues
Differences
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 [2013/03/15 08:26] – [Database Issues] paul | how_to:database_issues [2013/06/24 08:41] – [Event Viewer Entries] paul | ||
|---|---|---|---|
| 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 38: | 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 54: | 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==== | ||
| + | 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: | ||
| + | | ||
| + | ===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), | ||
| ====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 ":: | ||
how_to/database_issues.txt · Last modified: 2018/11/14 10:45 by 127.0.0.1
Page Tools
