PSCS Wiki

User Tools

Site Tools

Trace:
how_to:vpop3_not_starting_properly

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
how_to:vpop3_not_starting_properly [2014/01/03 09:55] – [VPOP3 Not Starting Properly] paulhow_to:vpop3_not_starting_properly [2018/11/14 10:45] (current) – external edit 127.0.0.1
Line 7: Line 7:
 If the database service does not exist, see the [[VPOP3DB service doesn't exist]] article. If the database service does not exist, see the [[VPOP3DB service doesn't exist]] article.
  
-If the database service doesn't start, or starts and stops immediately, see the [[VPOP3DB service not starting]] article.+If the database service doesn't start, or starts and stops immediately, see the [[VPOP3DB_PostgreSQL service not starting|VPOP3DB service not starting]] article.
  
-If the database service is started, but VPOP3 won't start, then there are a few possibilities:+If the database service is started, but VPOP3 won't start, then there are a few possibilities below. Also, check the Windows Application Event log for errors from VPOP3, and check the 'EXCEPTIONS.LOG' file in the VPOP3 directory. These may indicate what the problem is.
  
 ====VPOP3 User and/or Database doesn't exist==== ====VPOP3 User and/or Database doesn't exist====
Line 38: Line 38:
  
 If VPOP3 appears to hang at the **Check OutQueue DB** step, then the probable reason is that the VPOP3 OutQueue contains an excessive number of messages, so it is taking a while to validate them. See the [[delete Outqueue messages directly from the database]] article for some things to do next. If VPOP3 appears to hang at the **Check OutQueue DB** step, then the probable reason is that the VPOP3 OutQueue contains an excessive number of messages, so it is taking a while to validate them. See the [[delete Outqueue messages directly from the database]] article for some things to do next.
 +
 +====Backup running====
 +If a database backup (eg using ''pg_dump.exe'') is currently running, then VPOP3 will not be able to complete its startup database checks until the backup is complete (due to database locks). You can tell if this is the case by looking for **pg_dump.exe** in the Windows Task Manager //Processes// list. If it is, then stopping and restart the **VPOP3DB** service should cancel the current backup.
  
 ====Bad database==== ====Bad database====
Line 48: Line 51:
  
 Some users have problems with VPOP3 not automatically starting for various reasons, when starting it manually later will work. This can be solved by using the [[alternative method of automatically starting VPOP3]]. Some users have problems with VPOP3 not automatically starting for various reasons, when starting it manually later will work. This can be solved by using the [[alternative method of automatically starting VPOP3]].
 +
 +====Corrupt Bayesian database====
 +The spam filter's Bayesian statistical database is stored outside the main database for performance reasons. This database lets the spam filter analyse message content based on how previous messages were categorised. Occasionally this database may get corrupted (eg after a power failure or disk failure), which can cause VPOP3 to crash on startup. This database is stored in the VPOP3\_database\bayes.ldb directory on the disk. If you suspect this is the problem, you can delete/move/rename this directory and see if this makes any difference. VPOP3 periodically backs this database up, so it will automatically recover from a previous backup if you do this.
 +
 +
how_to/vpop3_not_starting_properly.1388742933.txt.gz · Last modified: 2018/11/14 10:44 (external edit)

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki