Quantcast
Viewing all articles
Browse latest Browse all 3189

(DP) Support Tip: PANIC: could not open control file "Global/pg_control" Permission Denied.

in instances where the IDB service fails to start for example after an upgrade and a manual atempt to start the service

ex;

D:\Omniback\idb\bin>pg_ctl.exe start –D “d:\Omniback\server\db80\pg

reports the following:

PANIC: could not open control file "Global/pg_control" Permission Denied.

check the PG_logs (ProgramData/omniback/Server/DB80/PG/PG_log) (/Var/opt/omni/server/db80/pg/pg_log)

should you see the following entry or similiar.


2016-01-26 14:35:37 CET LOG: database system was interrupted; last known up at 2015-11-09 18:55:13 CET
2016-01-26 14:35:37 CET LOG: could not open file "pg_xlog/000000010000000400000041" (log file 4, segment 65): No such file or directory
2016-01-26 14:35:37 CET LOG: invalid checkpoint record
2016-01-26 14:35:37 CET FATAL: could not locate required checkpoint record
2016-01-26 14:35:37 CET HINT: If you are not restoring from a backup, try removing the file "D:/Omniback/server/db80/pg/backup_label".
2016-01-26 14:35:37 CET LOG: startup process (PID 7996) exited with exit code 1
2016-01-26 14:35:37 CET LOG: aborting startup due to startup process failure

rin this scenario emoving the file "backup_label" resolved the issue and the IDB service was able to start. 

Technical Notes:

By default, DataProtector has continous archiving enabled in postgres.conf file:
 
archive_command = 'copy "%p" "D:/ProgramData/Omniback/server/db80/pg/pg_xlog_archive/%f"'
archive_mode = on
 
Which means that write ahead log (WAL) in the pg_xlog folder is stored to that previously mentioned folder.
 
WAL files contain every change made to the database and should the Server crash then postgres uses the WAL logs to perform a recovery.
 
As seen above in the postgres logs:
 
database system was interrupted; last known up at 2015-11-09 18:55:13 CET
 
An unexpected event did occur and postgres was trying to replay the WAL logs. However it could not find the referenced xlog files:
 
 could not open file "pg_xlog/000000010000000400000041" (log file 4, segment 65): No such file or directory
 
and also the backup history file was still present (pg_label file).
 
The reasons why the pg_label file remained on the system could be:that the server was stopped manually with pg_ctl stop, while idb backup is running but in this instance is unknown.
 
 
 

 

 

 


Viewing all articles
Browse latest Browse all 3189

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>