Differences

This shows you the differences between two versions of the page.

--- how_to:database_issues [2013/06/24 08:36] – [PostgreSQL Log Entries] paul
+++ how_to:database_issues [2013/06/24 08:41] – [Event Viewer Entries] paul
@@ Line 56: / Line 56: @@
 ====Event Viewer Entries====
+In the Windows Event Viewer, view the //Application// event log, then look for **Error** entries for the **PostgreSQL** source.
+Depending on your installation, the events may all be displayed as something like:
+  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 'partially' running state.
+To solve this, go to Windows TaskManager (Ctrl-Alt-Del - choose TaskManager), then go to the **Processes** tab and click **Show processes for all users**. Sort by **Image Name**, and **End Process** on all the **postgres.exe** processes. Once those are all ended, then you should be able to start the **VPOP3DB** service manually.
 ====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.

PSCS Wiki

User Tools

Site Tools

Differences

Page Tools