PSCS Wiki

User Tools

Site Tools

Trace:
how_to:postgresql_server_won_t_start_due_to_damaged_log_files

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:postgresql_server_won_t_start_due_to_damaged_log_files [2011/10/21 11:42] – paulhow_to:postgresql_server_won_t_start_due_to_damaged_log_files [2018/11/14 10:45] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 If the PostgreSQL server won't start at all, because its transaction logs are damaged, you will probably need to recreate the database store totally. If the PostgreSQL server won't start at all, because its transaction logs are damaged, you will probably need to recreate the database store totally.
- 
-You **may** be able to use the **[[http://www.postgresql.org/docs/8.3/static/app-pgresetxlog.html|pg_resetxlog.exe]]** program to create new transaction logs and control files which are 'just good enough' to get PostgreSQL started again, then you can [[http://wiki.pscs.co.uk/how_to%3Bbackup_vpop3#manual_database_backup|backup the database]] before doing the following steps. (Do //not// use pg_resetxlog.exe, then continue using the database without doing a full backup/rebuild/restore, corruption may be hidden, and cause bigger problems in the future). See the [[http://www.postgresql.org/docs/8.3/static/app-pgresetxlog.html|pg_resetxlog instructions]] for details on how to use that utility. 
  
 To rebuild the database: To rebuild the database:
Line 10: Line 8:
   - Run <code>bin\initdb -D <VPOP3folder>\pgsql\data -U postgres -W -A md5</code>   - Run <code>bin\initdb -D <VPOP3folder>\pgsql\data -U postgres -W -A md5</code>
   - When it prompts for a password, type in the password you want for the PostgreSQL superuser - we use **pgsqlpass**. If you choose to use something different, make sure you remember what it is!   - When it prompts for a password, type in the password you want for the PostgreSQL superuser - we use **pgsqlpass**. If you choose to use something different, make sure you remember what it is!
-  - Type <code>copy data_old\postgresql.conf data</code> to copy the database server configuration to the new location. You may be prompted if you want to overwrite the existing file. If so, confirm the overwrite. +  - Type <code>copy data_old\postgresql.conf data</code><code>copy data_old\vpop3db.conf data</code><code>copy data_old\vpop3dbuser.conf data</code> to copy the database server configuration to the new location. You may be prompted if you want to overwrite the existing file. If so, confirm the overwrite. 
-  - Set the permissions on the new Data folder. In Windows Explorer, right-click the VPOP3\pgsql\DATA folder and choose 'Properties' -> 'Security'. Check that the 'postgres' user has 'Full control' of the folder.+  - Set the permissions on the new Data folder. In Windows Explorer, right-click the VPOP3\pgsql\DATA folder and choose 'Properties' -> 'Security'. Check that the 'vpop3postgres' user ('postgres' user in VPOP3 versions 3 and 4) has 'Full control' of the folder.
   - Start the PostgreSQL service in Windows   - Start the PostgreSQL service in Windows
   - From the command prompt in vpop3\pgsql\bin run <code>createuser -S -D -R -U postgres -P vpop3</code>At the 'Enter Password for new role' and 'Enter it again' prompts type **vpop3pass**. At the 'Password:' prompt type **pgsqlpass** (or whatever password you defined in the step 4 above)   - From the command prompt in vpop3\pgsql\bin run <code>createuser -S -D -R -U postgres -P vpop3</code>At the 'Enter Password for new role' and 'Enter it again' prompts type **vpop3pass**. At the 'Password:' prompt type **pgsqlpass** (or whatever password you defined in the step 4 above)
Line 18: Line 16:
 Once you're happy everything is working OK, you can delete the **data_old** folder. Once you're happy everything is working OK, you can delete the **data_old** folder.
  
-If you wish, we can remote into your server and try to recover the data for you, but there will be a [[http://www.pscs.co.uk/buynow/buy.php?item=MISCSUP|£20 charge]] for this. You can [[support@pscs.co.uk|email us]] or phone on +44 1484 855800 to arrange this.+If you wish, we can remote into your server and try to recover the data for you, but there will be a [[http://www.pscs.co.uk/buynow/buy.php?item=MISCSUP3|£75 charge]] for this. You can [[support@pscs.co.uk|email us]] or phone on +44 1484 855800 to arrange this.
  
 =====Possible Causes===== =====Possible Causes=====
Line 26: Line 24:
  
 The only files in the pgsql\data folder which should ever be accessed by anything other than PostgreSQL itself are the contents of the ''pg_log'' folder (NOT the pg_xlog/pg_clog folders!) or the ''*.conf'' files. The only files in the pgsql\data folder which should ever be accessed by anything other than PostgreSQL itself are the contents of the ''pg_log'' folder (NOT the pg_xlog/pg_clog folders!) or the ''*.conf'' files.
 +
 +
 +====Possible alternative solution====
 +You **may** be able to use the **[[http://www.postgresql.org/docs/8.3/static/app-pgresetxlog.html|pg_resetxlog.exe]]** program to create new transaction logs and control files which are 'just good enough' to get PostgreSQL started again, then you can [[http://wiki.pscs.co.uk/how_to%3Bbackup_vpop3#manual_database_backup|backup the database]] before doing the following steps. (Do //not// use pg_resetxlog.exe, then continue using the database without doing a full backup/rebuild/restore, corruption may be hidden, and cause bigger problems in the future). See the [[http://www.postgresql.org/docs/8.3/static/app-pgresetxlog.html|pg_resetxlog instructions]] for details on how to use that utility.
  
  
how_to/postgresql_server_won_t_start_due_to_damaged_log_files.1319193747.txt.gz · Last modified: 2018/11/14 10:44 (external edit)

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki