PSCS Wiki

User Tools

Site Tools

Trace:
how_to:vpop3db_postgresql_service_not_starting

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:vpop3db_postgresql_service_not_starting [2015/03/02 09:38] – paulhow_to:vpop3db_postgresql_service_not_starting [2018/01/02 10:42] – [Other things to try] paul
Line 3: Line 3:
  
   * [[1069 - Login Failure - error when starting VPOP3DB service]]   * [[1069 - Login Failure - error when starting VPOP3DB service]]
 +  * [[Timeout while VPOP3DB is starting]]
  
 If the PostgreSQL service doesn't start, or starts and immediately stops, there are a couple of things you can do: If the PostgreSQL service doesn't start, or starts and immediately stops, there are a couple of things you can do:
  
   * Look in the Windows //Application//event log for entries relating to PostgreSQL. See below for possible errors in the event log   * Look in the Windows //Application//event log for entries relating to PostgreSQL. See below for possible errors in the event log
-  * 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 'relations'. If so, it might be a problem with a damaged database. See below for other possible error messages in the PostgreSQL log files+  * 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 'relations'. If so, it might be a problem with a damaged database. See below for other possible error messages in the PostgreSQL log files. 
 +  * Check the Processes list (for all users) in Windows' Task Manager and end any 'postgres.exe' processes which are owned by 'vpop3postgres' and try again.
  
 +=====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:
 +  
 ====Timed out waiting for server startup==== ====Timed out waiting for server startup====
 This can happen if the PC previously crashed, or there was a power failure. When the PC restarts, it can take some time for the database server to run its recovery process. This may take longer than the time allowed by the database service controller, especially if the PC is busy doing other recovery tasks. This can happen if the PC previously crashed, or there was a power failure. When the PC restarts, it can take some time for the database server to run its recovery process. This may take longer than the time allowed by the database service controller, especially if the PC is busy doing other recovery tasks.
Line 37: Line 50:
  
 ====no pg_hba.conf entry for host "::1", user "postgres", database "postgres"==== ====no pg_hba.conf entry for host "::1", user "postgres", database "postgres"====
 +====no pg_hba.conf entry for host "::1", user "vpop3", database "vpop3"====
 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 65: 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 'postgres.exe' processes visible in Windows TaskManager on the Processes tab. If so, then end those processes manually, before restarting the service.+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 'postgres.exe' processes visible in Windows TaskManager on the Processes tab. If so, then end those processes manually, before restarting the service.
  
 ====Shared memory problems==== ====Shared memory problems====
Line 107: Line 121:
  
 It is not installed this way by default because the 'LocalSystem' user has full permissions to the PC's files, whereas the //vpop3postgres// user only has access to the database files, but it should not be a big security risk as long as other basic security steps are taken. The default installation of the VPOP3DB service does not allow access to the database over the network, so it is low risk. It is not installed this way by default because the 'LocalSystem' user has full permissions to the PC's files, whereas the //vpop3postgres// user only has access to the database files, but it should not be a big security risk as long as other basic security steps are taken. The default installation of the VPOP3DB service does not allow access to the database over the network, so it is low risk.
-=====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: +===Reinstall PostgreSQL program files=== 
-  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.... +It isn't unknown for a virus scanner or Internet security program (or a 'system restore', etc) to randomly delete the PostgreSQL program files/DLLs, which will cause the service to fail to start. 
-   + 
-If that's the case, don't worry, just look lower down in the event message. It will say something like  +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: 
-  The following information was included with the event + 
-   +==VPOP3 v6.x== 
-It is that information you need to see. Some possible event messages we have seen are:+  bsdtar -xvf pgsql.tbz
      
 +==VPOP3 v7.x==
 +  7z x -aoa -r pgsql95.7z
 +
 +That should overwrite all the PostgreSQL program files/DLLs/etc without affecting the database.
how_to/vpop3db_postgresql_service_not_starting.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