Backtrack 5 postgresql Error Fix

Hello Friends, In This post, I will Discuss About the postgresql error in Backtrack 5r2 when the service attempts to starts.





The Error:

FATAL:  bogus data in lock file "postmaster.pid": ""
/opt/framework3/postgresql/scripts/ctl.sh : postgresql  could not be started

Fix:

root@bt:~# rm /opt/framework3/postgresql/data/postmaster.pid
root@bt:~# rm /opt/framework3/postgresql/.s.PGSQL.7175
root@bt:~# rm /opt/framework3/postgresql/.s.PGSQL.7175.lock
root@bt:~# /etc/init.d/framework-postgres start
LOG:  database system was interrupted; last known up at 2012-07-02 14:11:35 IST
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  record with zero length at 0/6A7D80
LOG:  redo is not required
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
/opt/framework3/postgresql/scripts/ctl.sh : postgresql  started at port 7175
root@bt:~#

Steps:

rm /opt/framework3/postgresql/data/postmaster.pid
rm /opt/framework3/postgresql/.s.PGSQL.7175
rm /opt/framework3/postgresql/.s.PGSQL.7175.lock
/etc/init.d/framework-postgres start

And thats it, you are done.


Feel Free To Leave A Comment If Our Article has Helped You, Support Us By Making A Small Contribution, Thank You!