PSCS Wiki

User Tools

Site Tools

Trace:
how_to:database_issues

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
how_to:database_issues [2013/06/24 08:35] – [PostgreSQL service not starting] paulhow_to:database_issues [2013/08/30 12:34] – [Database Issues] paul
Line 2: Line 2:
  
 VPOP3 version 3 and later use the [[http://www.postgresql.org|PostgreSQL]]] database server. This is an open source enterprise level database server. Several VPOP3 problems are due to problems with the database service. VPOP3 version 3 and later use the [[http://www.postgresql.org|PostgreSQL]]] database server. This is an open source enterprise level database server. Several VPOP3 problems are due to problems with the database service.
 +
 +  * [[Database & Disk Caching]]
  
 =====Disk Caching===== =====Disk Caching=====
Line 56: Line 58:
  
 ====Event Viewer Entries==== ====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==== ====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 "::1", user "postgres", database "postgres"=== ===no pg_hba.conf entry for host "::1", user "postgres", database "postgres"===
how_to/database_issues.txt · Last modified: 2018/11/14 10:45 by 127.0.0.1

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki